Email templating system (#755)

* feat: Implement email templates

This commit introduces the email templates feature, allowing you to create reusable templates for broadcast and sequence emails.

Backend:
- Added `EmailTemplate` model.
- Implemented GraphQL queries (`getEmailTemplate`, `getEmailTemplates`) and mutations (`createEmailTemplate`, `updateEmailTemplate`, `deleteEmailTemplate`) for email templates.
- Added logic for the new GraphQL operations.

Frontend:
- Added a 'Templates' tab to the `/dashboard/mails` page.
- Created a `TemplatesList` component to display email templates.
- Created an email template editor page.
- Created a new page for selecting a template when creating a new broadcast or sequence.
- Updated the `createSequence` mutation to accept `title` and `content` from a template.

* Lint fixes

* Email templating system

* Email templating system

* Added email template docs

* Removed state-management package dist and its other mentions

---------

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Co-authored-by: Rajat <hi@rajatsaxena.dev>

Author: 3 people

.github/workflows/test.yaml

@@ -26,7 +26,6 @@ jobs:
           pnpm --filter @courselit/common-models build
           pnpm --filter @courselit/utils build
           pnpm --filter @courselit/text-editor build
-          pnpm --filter @courselit/state-management build
           pnpm --filter @courselit/components-library build
           pnpm --filter @courselit/page-primitives build
           pnpm --filter @courselit/page-blocks build

.gitignore

@@ -44,4 +44,5 @@ report*.json
 globalConfig.json
 
 # CourseLit files
-domains_to_delete.txt
+domains_to_delete.txt
+.codex

AGENTS.md

@@ -6,6 +6,7 @@
 - Command for running tests: `pnpm test`.
 - The project uses shadcn for building UI so stick to its conventions and design.
 - In `apps/web` workspace, create a string first in `apps/web/config/strings.ts` and then import it in the `.tsx` files, instead of using inline strings.
+- For admin/dashboard empty states in `apps/web`, prefer reusing `apps/web/components/admin/empty-state.tsx` instead of creating one-off placeholder UIs.
 - When working with forms, always use refs to keep the current state of the form's data and use it to enable/disable the form submit button.
 - Check the name field inside each package's package.json to confirm the right name—skip the top-level one.
 - While working with forms, always use zod and react-hook-form to validate the form. Take reference implementation from `apps/web/components/admin/settings/sso/new.tsx`.

apps/docs/package.json

@@ -18,7 +18,7 @@
         "@docsearch/css": "^3.1.0",
         "@docsearch/react": "^3.1.0",
         "@types/node": "^18.0.0",
-        "@types/react": "^17.0.45",
+        "@types/react": "^18.0.0",
         "@types/react-dom": "^18.0.0",
         "astro": "^1.4.2",
         "preact": "^10.7.3",

apps/docs/public/assets/emails/email-editor-via-template.png

@@ -96,6 +96,10 @@ export const SIDEBAR: Sidebar = {
                 text: "Sequences (Campaigns)",
                 link: "en/email-marketing/sequences",
             },
+            {
+                text: "Templates",
+                link: "en/email-marketing/templates",
+            },
             {
                 text: "Analytics",
                 link: "en/email-marketing/analytics",