Tools, templates, React components, reusable GitHub Actions, and curated lists for building emails — write in Markdown or composable functions, get responsive HTML (or React email trees) out, and ship them through shared CI.

This profile README lives in LLazyEmail/.github at profile/README.md. Deeper pages: architecture · repository catalog · contributing & agents.

📖 Documentation: docs.llazyemail.com · llazyemail.github.io/documentation · Source

LLazyEmail is an open organization around email template tooling: parsing Markdown, composing HTML from small functions or React components, writing files safely, inspecting which part of an email broke, and automating render + docs CI with reusable GitHub Actions.

Mission in one line: make production HTML email generation boring, testable, and shareable — without pretending email clients are modern browsers.

We do not invent marketing stats here. Star counts and package versions below are taken from GitHub / npm at documentation time and will drift.

Pick the path that matches your project.

Requires Node (see each package engines; many packages want Node 20+, some CLIs 22+ / 24+).

# Public npm write helpers
npm install markup-generator

# GitHub Packages (@llazyemail) — need read:packages + .npmrc (see each repo's .npmrc.example)
npm install @llazyemail/generate-template @llazyemail/template-runtime-display

import { createGenerator } from '@llazyemail/generate-template';

const generate = createGenerator({
  catalog: [{ ids: ['welcome'], render: (p) => `<p>Hello ${(p as { name: string }).name}</p>` }],
  samplePayloads: { welcome: { name: 'Alex' } },
  outDir: 'generated',
});

await generate.run({ templateId: 'welcome', payload: { name: 'Alex' }, write: { out: 'generated/welcome.html' } });

CLI (after a project generate-template.config.* that exports createProjectGenerator):

npx generate-template --list
npx generate-template --all --out=generated

git clone https://github.com/LLazyEmail/markdown-to-email.git
cd markdown-to-email
npm install
# Put Markdown in ./source/source.md
npm run dev:parseFull          # → generated HTML
# npm run dev:parseReactFull   # → React tree

Package on npmjs: @lazyemail/markdown-to-email.

npx template-runtime-display inspect ./letter.mjs --out report.html
# or live:
npx template-runtime-display dev ./letter.mjs

permissions:
  contents: read
  pull-requests: write
steps:
  - uses: actions/checkout@v7
  - uses: LLazyEmail/email-template-workflows@v1
    with:
      working-directory: .
      command: npx generate-template --all --out=generated
      artifact-directory: generated

• Product docs: https://docs.llazyemail.com
• Awesome Email Marketing: https://github.com/LLazyEmail/awesome-email-marketing
• Awesome Newsletters: https://llazyemail.github.io/awesome-newsletters/

How the core repositories relate. Full write-up: docs/architecture.md.

flowchart TB
  subgraph Consumers["Template consumers"]
    HN["hn_email_template"]
    NMTG["nomoretogo_email_template"]
    Postmark["postmark-transactional-template-simple"]
    Lit["_playing_with_lit"]
  end

  subgraph Generate["Generation"]
    Gen["generate-template<br/>@llazyemail/generate-template"]
    Markup["markup-generator"]
  end

  subgraph Render["Rendering"]
    RT["render-template<br/>@llazyemail/render-template"]
    TRD["template-runtime-display<br/>@llazyemail/template-runtime-display"]
  end

  subgraph Markdown["Markdown path"]
    MTE["markdown-to-email"]
  end

  subgraph CI["Shared Actions"]
    ETW["email-template-workflows"]
    DocA["documentation-actions"]
  end

  HN --> TRD
  Postmark --> Gen
  Postmark --> TRD
  Lit --> Gen
  NMTG --> Markup
  NMTG -.-> MTE
  Gen --> Markup
  TRD --> RT
  Gen -.-> TRD
  MTE --> Markup
  ETW -->|"render → artifact"| Gen
  DocA -->|"docs sites & awesome lists"| Docs["documentation · awesome-* · v-school · assemblya · fuck-ecoflow"]

Ownership rules (short):

Consumers inject render functions into createGenerator rather than reimplementing validation + write pipelines locally. See generate-template/docs/organization-schema.md.

Sister relationship: documentation ↔ awesome-email-marketing ↔ awesome-newsletters share foundation goals; long-term they lean on documentation-actions instead of duplicated workflow YAML.

markdown-to-email is the classic core engine. It parses Markdown and renders responsive HTML or React email templates.

Where to look in the code

• Content source
• Replace Markdown (HTML)
• Replace Markdown (React)
• Write module

"atherdon-callbacks": "^1.10.0",
"atherdon-newsletter-html-replacer": "^0.4.0",
"atherdon-newsletter-js-layouts": "^1.5.1",
"atherdon-newsletter-react": "^1.0.11",
"atherdon-newsletter-react-replacer": "^0.4.0",
"atherdon-old-newsletter-js-outertemplate": "^2.4.0",
"markup-generator": "^0.4.0",

Today’s parallel path: new template repos (for example postmark-transactional-template-simple, hn_email_template’s current scripts/ generator, _playing_with_lit) prefer @llazyemail/generate-template + @llazyemail/template-runtime-display rather than growing the Markdown parser further. Both paths remain first-class in the org.

Active highlights by category. Full table of every public repo (including languages and star counts from the API): docs/repositories.md.

Versions below were read from npmjs / GitHub Packages APIs while writing this doc — always confirm with npm view / the package page before pinning.

Requires a token with read:packages and scope mapping in .npmrc (copy each repo’s .npmrc.example).

markup-generator v4 bundles its internal workspace packages into one public tarball (trusted publishing / OIDC). Older markdown-to-email READMEs may still list pre-v4 dependency ranges.

Pin LLazyEmail/email-template-workflows@v1. Supports npm / yarn / pnpm / bun, monorepos, script mode, command mode, and build-command mode (MJML, pandoc, …). Uploads artifacts and can upsert one PR comment per comment-key. Agent playbook: docs/agent-playbook.md.

Pin LLazyEmail/documentation-actions@v1 after release. Reusable workflows cover Docusaurus test-deploy / Pages deploy, markdownlint, soft-fail lychee, changelog, docs-index, catalog API, auto-rebase, star-request, and awesome-list checks. Prefer copying from examples/ over duplicating YAML. Checklist: skills/docusaurus-docs-site/SKILL.md.

• Pin third-party Actions to a full commit SHA with a # vX.Y.Z comment; Renovate updates them.
• Prefer draft PRs; do not merge unless the owner asks.
• Org Actions access must allow reusable workflows from these repositories.

More detail: docs/contributing.md.

1. Open small, single-purpose draft PRs.
2. Keep existing curated content — extend, annotate, or archive; do not delete wholesale.
3. Include the commit trailer when working for the maintainer:

Co-authored-by: petroved <arthur.tkachenko.netweight@gmail.com>

4. Follow the target repository’s CONTRIBUTING.md / AGENTS.md.
5. Never commit secrets.

Do not hand-edit compiled CHANGELOG.md files when a fragment or Changesets system is in use. Labels like skip-changelog / no-changelog waive CI where configured.

Most active repos ship a root AGENTS.md. Agents should read it first.

Org-wide expectations:

• Treat src/ + tests as ground truth; keep docs in sync without deleting historical guidance.
• Prefer createGenerator + injected render over local BuildPipeline-style duplication.
• Prefer thin callers of documentation-actions / email-template-workflows.
• Parts passed to render-template must return strings (stringify Lit / React output first).
• Open draft PRs; never merge/close unless the human owner asks.
• Always add the Co-authored-by: petroved <…> trailer when working for Arthur.

Indexes: many repos also expose llms.txt / llms-full.txt for LLM tooling.

Suggested consumer README badge examples:

[![email-template-workflows](https://img.shields.io/badge/CI-email--template--workflows-blue)](https://github.com/LLazyEmail/email-template-workflows)
[![documentation-actions](https://img.shields.io/badge/CI-documentation--actions-blue)](https://github.com/LLazyEmail/documentation-actions)

• Build your email templates with React
• Creating email templates with React components
• HTML Email Basics
• How to build emails with React
• Build a Reusable Design System With React
• Create elegant HTML email templates using React
• React-email-editor

• Designing Error Messages and a Logging Strategy in Node.js
• Comparing Node.js logging tools
• npmlog
• How to use levels function in Logger
• How to handle log events with the npmlog library?
• markdownlint
• Mintlify docs

Worth a look for ideas and comparison:

• Bojler
• Maizzle
• Pechkin
• 11ty-email-generator

Facts in these docs come from public repository metadata and READMEs. If something drifts, prefer the source repo and send a draft PR that extends this profile rather than deleting sections.