fix: ai email prompt and home page padding

skillrecordings · Sep 20, 2024 · 1428706 · 1428706
1 parent d162276
commit 1428706
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 6 deletions.
diff --git a/apps/epic-react/src/components/landing/testimonials.tsx b/apps/epic-react/src/components/landing/testimonials.tsx
@@ -129,7 +129,7 @@ const Testimonials = () => {
   return (
     <section
       id="testimonials"
-      className="not-prose relative mx-auto grid w-full max-w-4xl grid-cols-1 gap-4 pb-10 pt-16 md:grid-cols-2"
+      className="not-prose relative mx-auto mt-16 grid w-full max-w-4xl grid-cols-1 gap-4 pb-10 pt-16 md:grid-cols-2"
     >
       <div
         className="absolute left-0 top-0 h-px w-full bg-gradient-to-r from-transparent via-border to-transparent"

diff --git a/apps/epic-react/src/inngest/functions/ai-email/write-an-email.ts b/apps/epic-react/src/inngest/functions/ai-email/write-an-email.ts
@@ -81,14 +81,15 @@ export const writeAnEmail = inngest.createFunction(
     - if there is any previous commentary from the editor, please use it as a basis to improve the email and subject that you write.
     - prefer full text titles over slugs
     - don't guess at titles, use the provided data only
-    - if you talk about the next lesson make sure it comes after the current lesson
+    - next lessons ONLY come after the current lesson!
     - keep the exposition to a minimum
     - developers hate when ai writes for them, don't sound like an ai, sound human
     - when it makes sense, don't focus on Remix, focus on the broader universal skills of a web developer
     - No additional "meta" text or commentary is necessary. 
     - editor feedback is a priority unless you think it is wrong, then you can ignore it.
     - **do not** link to lessons
     - **do not** guess lesson or workshop titles, use the progress data below only
+    - **only** suggest next lessons, not previous incomplete lessons
     - keep the exposition and flowery language to a minimum
 
     Structured Progress Data:

diff --git a/apps/epic-react/src/pages/index.tsx b/apps/epic-react/src/pages/index.tsx
@@ -208,7 +208,7 @@ const Home: React.FC<{
           </div>
         </section>
         <section
-          className="bg-er-gray-100 pb-16 pt-8"
+          className="bg-er-gray-100 pb-24 pt-8"
           aria-label="Enroll in Epic React"
           id="buy"
         >

diff --git a/apps/epic-web/src/inngest/functions/ai-email/write-an-email.ts b/apps/epic-web/src/inngest/functions/ai-email/write-an-email.ts
@@ -81,14 +81,15 @@ export const writeAnEmail = inngest.createFunction(
     - if there is any previous commentary from the editor, please use it as a basis to improve the email and subject that you write.
     - prefer full text titles over slugs
     - don't guess at titles, use the provided data only
-    - if you talk about the next lesson make sure it comes after the current lesson
+    - next lessons ONLY come after the current lesson!
     - keep the exposition to a minimum
     - developers hate when ai writes for them, don't sound like an ai, sound human
     - when it makes sense, don't focus on Remix, focus on the broader universal skills of a web developer
     - No additional "meta" text or commentary is necessary. 
     - editor feedback is a priority unless you think it is wrong, then you can ignore it.
-    - do not link to lessons
-    - do not guess lesson or workshop titles, use the progress data below only
+    - **do not** link to lessons
+    - **do not** guess lesson or workshop titles, use the progress data below only
+    - **only** suggest next lessons, not previous incomplete lessons
     - keep the exposition and flowery language to a minimum
 
     Structured Progress Data: