Notes from AI builds
Menu

Writing schedule

This is an editorial planning snapshot, not current product documentation or a publication promise. Dates can become stale; the published archive is canonical.

Editorial backlog

The queue records working targets, draft stages, audiences, and questions. It is deliberately excluded from search indexing and machine-readable core-page lists.

  1. Due

    draft / note

    A11y tests catch product regressions, not just accessibility issues

    Use the RSS link regression as the simple example: an accessibility smoke test protected a real reader path, not just a technical checklist.

    For: builders who treat accessibility as product quality

    • accessibility
    • testing
    • product-quality
    Drafting prompts
    • What user path disappeared?
    • Why did the accessibility test catch it?
    • What should a small site test before shipping?
  2. Due

    draft / practical walkthrough

    The small backend pattern for newsletter capture

    Show how one form can get a real backend without turning the whole site into an app: validate, store, verify, then sync later.

    For: developers adding one dynamic workflow to a static site

    • cloudflare
    • d1
    • forms
    Drafting prompts
    • What is the smallest runtime surface the form needs?
    • Which data should be stored first-party?
    • How do we prove the live form actually wrote the row?
  3. Due

    draft / decision note

    Keystatic vs PocketBase vs D1: different tools, different jobs

    Compare content editing, app backends, and small edge data stores without pretending they solve the same problem.

    For: technical operators choosing backend primitives for content sites

    • cms
    • databases
    • cloudflare
    Drafting prompts
    • What should live in Git?
    • What needs runtime storage?
    • When does a full backend become worth the operational cost?
  4. Queued

    draft / field note

    A static site can have a backend without becoming an app

    Use the AppHeat newsletter path as the broader lesson: a content site can add one focused runtime workflow without changing its whole architecture.

    For: builders deciding how much backend a content site actually needs

    • architecture
    • cloudflare
    • d1
    Drafting prompts
    • What changed when the site needed one dynamic workflow?
    • Where does a static site stop and an app start?
    • Which backend pieces are enough before adding a full app backend?
  5. Queued

    draft / build note

    The rendered HTML check is the AEO test I trust

    Use AppHeat's local AEO audit as the concrete example: answer summaries, FAQ schema, topic links, llms.txt, search text, and built HTML all have to agree.

    For: technical publishers who want answer-engine readiness without vague markup theater

    • aeo
    • seo
    • technical-seo
    • content-strategy
    Drafting prompts
    • Why is source frontmatter not enough?
    • What does the built HTML prove that a draft cannot?
    • Which checks should stay local before analytics data exists?
  6. Queued

    idea / architecture note

    Answer summaries are for readers before they are for schema

    Explain why AppHeat puts short visible answers on posts first, then mirrors the same claims in metadata and structured data.

    For: builders adding AEO structure to technical articles

    • aeo
    • schema
    • content-strategy
    Drafting prompts
    • What job does a visible answer summary do for a human reader?
    • When should FAQ schema exist?
    • How do we avoid hidden claims in structured data?
  7. Queued

    idea / architecture note

    Topic hubs beat tags when AI has to understand a site

    Use AppHeat's AEO hub as the example: tags label posts, but hubs explain the path and make recurring ideas easier to understand.

    For: technical writers and solo builders growing a content site deliberately

    • aeo
    • seo
    • content-architecture
    Drafting prompts
    • What can a topic hub explain that a tag cannot?
    • How should a hub link to old and future posts?
    • What does topical authority look like before there are many posts?
  8. Queued

    idea / technical check

    What AI crawlers can actually see on a static Astro site

    Turn crawler access into a practical checklist: robots.txt, llms.txt, sitemap, RSS, server-rendered HTML, and no hidden JavaScript-only content.

    For: developers shipping static technical sites on Cloudflare

    • aeo
    • technical-seo
    • astro
    • cloudflare
    Drafting prompts
    • Which files do crawlers and answer engines get first?
    • What disappears if JavaScript is disabled?
    • How should Cloudflare crawler settings be checked before publishing?
  9. Queued

    idea / workflow note

    Turning video transcripts into citable site content

    Show the AppHeat workflow for using a transcript as research input without copying it: extract, summarize, map gaps, draft, evidence-check, and publish.

    For: builders using local agents for content research and publishing workflows

    • aeo
    • content-strategy
    • agents
    • workflows
    Drafting prompts
    • How do we use yt-dlp transcripts as research inputs?
    • What should the evidence reviewer block?
    • How can Pi workflows make transcript-to-post work repeatable?