Merge branch 'main' of github.com:codelitdev/courselit into small-fixes-march-2026

Author: Rajat

.github/workflows/code-quality.yaml

@@ -1,5 +1,10 @@
 name: Code Quality
-on: [push]
+on:
+  push:
+    branches:
+      - '**'
+    tags-ignore:
+      - '*'
 
 jobs:
   lint:

.github/workflows/publish-docker-images.yaml

@@ -1,4 +1,4 @@
-name: Publish NPM Packages
+name: Publish Docker images
 
 on:
   push:

.github/workflows/test.yaml

@@ -1,5 +1,10 @@
 name: Testing
-on: [push]
+on:
+  push:
+    branches:
+      - '**'
+    tags-ignore:
+      - '*'
 
 jobs:
   test:

AGENTS.md

@@ -16,6 +16,7 @@
     - Use **Cursors** (`.cursor()`) to stream data from MongoDB, ensuring the script remains memory-efficient regardless of dataset size.
     - Use **Batching** with `bulkWrite` (e.g., batches of 500) to maximize performance and minimize network roundtrips.
     - Ensure **Idempotency** (safe to re-run) by using upserts or `$setOnInsert` where applicable.
+- When making changes to the structure of the Course, consider how it affects its representation on its public page (`apps/web/app/(with-contexts)/(with-layout)/p/[id]/page.tsx`) and the course viewer (`apps/web/app/(with-contexts)/course/[slug]/[id]/page.tsx`).
 
 ### Workspace map (core modules):
 
@@ -48,6 +49,7 @@
 - Always add or update test when introducing changes to `apps/web/graphql` folder, even if nobody asked.
 - Run `pnpm test` to run the tests.
 - Fix any test or type errors until the whole suite is green.
+- Refrain from creating new files when adding tests in `apps/web/graphql` subdirectories. Re-use `logic.test.ts` files for adding new test suites i.e. describe blocks.
 
 ## PR instructions
 

apps/docs/public/assets/products/lesson-reordering.png

@@ -6,7 +6,7 @@ layout: ../../../layouts/MainLayout.astro
 
 CourseLit uses the concept of a `Lesson`. It is very similar to what we generally see in books, i.e., a large piece of information is divided into smaller chunks called lessons.
 
-Similarly, you can break down your course into `Lessons` and group the lessons into [Sections](/en/products/section).
+Similarly, you can break down your course into `Lessons` and group the lessons into [Sections](/en/courses/section).
 
 ## Sections
 

apps/docs/public/assets/products/section-reordering.png

@@ -46,6 +46,18 @@ Here’s how sections look in various parts of the platform.
 
 ![Edit Section Settings](/assets/products/edit-section-settings.png)
 
+## Rearranging Sections
+
+You can move sections up or down as you like. Click the chevron up or down buttons to move a section.
+
+![Move a section](/assets/products/section-reordering.png)
+
+## Moving a Lesson Between Sections
+
+Use the drag-and-drop handles on the left side of a lesson's listing to move it to any section.
+
+![Move a lesson](/assets/products/lesson-reordering.png)
+
 ## Drip a Section
 
 You can release a section on a **specific date** or **after a certain number of days have elapsed since the time a student enrolls**.
@@ -55,22 +67,28 @@ If drip configuration is enabled for a section, a student won't be able to acces
 ### Drip by Date
 
 1. If you want a section to be available to users on a specific date, this is the option you should opt for.
+2. Exact-date sections unlock only when their chosen date and time arrives.
+3. Unlocking an exact-date section does not change the timing of other relative drip sections.
 
 ![Drip by Date](/assets/products/drip-by-date.png)
 
-2. Select the date on which this section will be dripped.
-3. Click `Continue` to save it.
+4. Select the date on which this section will be dripped.
+5. Click `Continue` to save it.
 
 ### Drip After a Certain Number of Days From Last Dripped Content
 
 1. If you want a section to be available to users after a certain number of days have elapsed since the last dripped content, this is the option you should opt for.
+2. Relative-date sections are released in section order. A later relative section waits for the earlier relative section before its own delay begins.
+3. The first relative section counts from the student's enrollment date. After that, each newly released relative section becomes the anchor for the next relative section.
 
 > For the first dripped section, the date of enrollment will be considered the last dripped content date.
 
 ![Drip After a Certain Number of Days Have Elapsed](/assets/products/drip-by-specific-days.png)
 
-2. Select the number of days.
-3. Click `Continue` to save it.
+4. Select the number of days.
+5. Click `Continue` to save it.
+
+> Rearranging a section with drip enabled may affect its drip schedule; use caution.
 
 ### Notify Users When a Section Has Dripped
 
@@ -94,7 +112,7 @@ On the course viewer, the customer will see the clock icon against the section n
 
 2. Click `Delete` on the confirmation dialog.
 
-> A section must be empty (i.e., have no lessons attached to it) in order to be deleted.
+> A section must be empty (i.e., have no lessons attached) before it can be deleted. Move any lessons to another section to make it empty.
 
 ## Next Step
 

apps/docs/src/pages/en/courses/add-content.md

@@ -1,10 +1,36 @@
+# Port for the queue service to listen on
 PORT=4000
+
+# email configuration for sending notifications (e.g., course updates, reminders)
 EMAIL_USER=email_user
 EMAIL_PASS=email_pass
 EMAIL_HOST=email_host
+EMAIL_FROM=[email protected]
+
+# MongoDB connection string for storing queue data and job information
 DB_CONNECTION_STRING=mongodb://db.string
+
+# Redis configuration for caching and job queue management
 REDIS_HOST=localhost
 REDIS_PORT=6379
+
+# Maximum number of times to retry a failed job before marking it as failed
 SEQUENCE_BOUNCE_LIMIT=3
+
+# Domain for constructing URLs in notifications and links
 DOMAIN=courselit.app
-PIXEL_SIGNING_SECRET=super_secret_string
+
+# Secret key for signing tracking pixels (used in email notifications)
+PIXEL_SIGNING_SECRET=super_secret_string
+
+# Optional: enables PostHog exception tracking when set.
+POSTHOG_API_KEY=
+
+# Optional: PostHog host URL (default shown here).
+POSTHOG_HOST=https://us.i.posthog.com
+
+# Optional: per-source exception cap per minute (default: 100).
+POSTHOG_ERROR_CAP_PER_SOURCE_PER_MINUTE=100
+
+# Optional: deployment environment label sent in telemetry (default: unknown).
+DEPLOY_ENV=local

apps/docs/src/pages/en/courses/section.md

@@ -21,6 +21,10 @@ The following environment variables are used by the queue service:
 - `EMAIL_PORT` - SMTP server port (default: `587`)
 - `PORT` - HTTP server port (default: `80`)
 - `NODE_ENV` - Environment mode. When set to `production`, emails are actually sent; otherwise they are only logged
+- `POSTHOG_API_KEY` - Enables PostHog error tracking when set
+- `POSTHOG_HOST` - PostHog host URL (default: `https://us.i.posthog.com`)
+- `POSTHOG_ERROR_CAP_PER_SOURCE_PER_MINUTE` - Per-source exception cap (default: `100`)
+- `DEPLOY_ENV` - Deployment environment label used in telemetry (default: `unknown`)
 - `SEQUENCE_BOUNCE_LIMIT` - Maximum number of bounces allowed for email sequences (default: `3`)
 - `PROTOCOL` - Protocol used for generating site URLs (default: `https`)
 - `DOMAIN` - Base domain name for generating site URLs