Content Generation Checklist for Web Development

Specify the role (frontend, backend, full-stack), project context, and the action you want (clone repo, run example, sign up). Tie each piece to a measurable KPI like demo signups or docs-to-trial conversion.

Convert recurring bugs, feature requests, and migration pain points into posts and guides. If 10 issues mention CORS or TypeScript types, that is a topic with clear developer demand.

Index READMEs, ADRs, OpenAPI/GraphQL schemas, and architecture diagrams into a vector store to ground generation. This reduces hallucinations and keeps outputs aligned with your actual stack.

Use temperature 0-0.2, consistent system prompts, and schema-constrained outputs. Deterministic settings ensure repeatable drafts that can be diffed and reviewed like code.

Include target frameworks (React, Next.js, Node), audience level, keywords, sources, success criteria, and required CTAs. Store briefs in the repo to version along with content.

List MDN, TC39 proposals, WHATWG specs, framework docs, and RFCs you will cite. Linking to primary sources builds trust with engineers and improves E-E-A-T.

Specify tone, code fence conventions, snippet policies, and prohibited claims. Include guidance like 'prefer TypeScript, show npm and pnpm, include version constraints.'

Provide package.json, tsconfig, OpenAPI yaml, GraphQL SDL, and environment guidelines. The model should inherit your lint rules and API shapes for precise examples.

Ask for H2/H3 structure, acceptance criteria, and code block inventory before drafting. Approve or edit the outline to prevent rework and keep drafts focused.

Have the model emit structured sections, then render to Markdown or MDX. Schema validation catches missing elements like CTAs, hero summary, or code prerequisites.

Include language version, package versions, and setup steps. For Node examples, pin 'node:18-alpine' in Dockerfile and show exact npm install commands.

Produce H1, subhead, three value props, code-first hero, and a short 'How it works' flow. Keep jargon light, but include concrete claims like bundle size impact or cold start times.

Extract code fences and run them in a container via GitHub Actions. Use Node, Python, or Go images to verify install commands and sample scripts do not error.

Apply ESLint, Prettier, and TypeScript checks to all snippets. Enforce noImplicitAny and consistent module resolution to avoid misleading examples.

Spin up Prism or MSW to ensure request/response bodies match your schema. Fail the build if examples drift from contract.

Reject hardcoded keys, require .env usage, and show token scoping best practices. Add a secret scanner step to block unsafe content.

Where applicable, generate React, Vue, and Svelte variants and verify identical outcomes. Use Playwright to snapshot UI parity across samples.

Demonstrate tree-shaking, code-splitting, and caching headers. Include Lighthouse or Web Vitals notes where relevant to avoid teaching anti-patterns.

Target queries like 'Next.js image optimization', 'Prisma migration error', or 'CORS fix Express'. Map each keyword to a format: tutorial, troubleshooting, or comparison.

Use tokens developers scan for: framework, version, error codes, and outcome. Keep titles under 60 characters and metas under 155 with a concrete benefit.

Emit Article or TechArticle with author, dateModified, codeSampleType, and references. Validate in Rich Results Test to boost SERP clarity.

Link tutorials to API references and related guides, and ensure breadcrumb consistency. Use descriptive anchors like '/docs/api/webhooks#verify-signature'.

Prefer text over screenshots, add alt text, and provide copy buttons for code blocks. If images are necessary, use SVG for diagrams and compress PNGs.

Include an executive summary, prerequisites, time-to-complete, and a table of contents. Busy engineers should grasp the value in under 30 seconds.

Use PR templates with checklists for sources, tests, and SEO. Require code-owner reviews from a developer advocate for technical posts.

Run markdownlint, cspell, linkinator, and frontmatter validation. Break the build on broken links or missing canonical URLs.

Use GrowthBook or VWO to test H1 variants and button copy. Evaluate click-through to code examples and signup conversion, not just time on page.

Publish to Dev.to, Hashnode, Reddit, and LinkedIn with consistent UTM parameters. Track which channels drive repo stars, trial starts, or issue creation.

Instrument copy-to-clipboard, code sandbox runs, and outbound doc clicks. Use GA4 or Plausible with custom events mapped to your funnel.

Subscribe to release feeds and security advisories to open issues when APIs change. Schedule quarterly revamps for high-traffic posts and re-run tests on snippets.