Help & How It Works

Quick start

  1. Log in with your Draftline account.
  2. Make sure you’re on the correct tenant (workspace).
  3. Create a client – the company you are writing a newsletter for.
  4. Open that client’s newsletter list.
  5. Click Create from notes to start a new issue.
  6. Enter a subject, pick a template, and add notes / bullets / links.
  7. Submit to queue an AI draft.
  8. The worker generates HTML and saves it to the newsletter.
  9. Open the newsletter Preview page to review the draft.
  10. Use Regenerate if you want another version.

Key concepts

  • Tenant – your workspace or account. All data is scoped by tenant.
  • Client – the customer or brand you send newsletters for.
  • Newsletter – a single issue (subject + body HTML).
  • Inputs – notes, bullets, and links you feed the AI.
  • Template – a structural guide for the AI, not a visual theme.
  • Job – a queued AI generation task the worker picks up.

AI generation behavior

  • Draftline builds a prompt from your subject, template structure, and the inputs you provide.
  • If no AI API key is configured, the system returns a mock HTML draft so you can still demo the full flow.
  • With a real AI key and provider integration, the worker calls the API and stores the returned HTML into the newsletter.

Tenant switching

If your user account belongs to multiple tenants, you can:

  • Click Switch tenant in the top navigation.
  • Select the tenant you want to work in.
  • All dashboards, clients, and newsletters will then be scoped to that tenant.

For demo use

During a live demo, a simple narrative could be:

  1. “Here is our Draftline dashboard for this agency tenant.”
  2. “We manage multiple clients. Let’s open ACME Corp.”
  3. “We’ll collect quick notes and links, then ask Draftline to draft this issue.”
  4. “The worker picks up the job and generates HTML in the background.”
  5. “Now we preview the draft, and if we want a different angle, we hit Regenerate.”

If something doesn’t behave as expected, check:

  • The worker process is running (php cli/ai_worker.php).
  • The database seed created users, tenants, and templates.
  • Environment variables in .env are pointing to the right database.