Roadmap, in the work

Ten prompts that built this site’s next phase

On July 2, 2026 we asked one question — "give me 10 prompts that make this a better and more popular site, and execute them in order of importance" — and ran the answer the same day, on Fable 5, during its own return window. The roadmap is the work; here it is, ranked, with what each shipped.

Published 2026-07-02 · all ten executed · ✓ marks shipped

  1. ✓ shippedAnswer the question everyone is asking

    "Is Fable 5 down?" is the biggest live query of the week. Own it.

    Build /status/ — a live "Is Fable 5 up?" page: unambiguous answer block, availability-by-surface table, window countdown, incident history, /api/status.json twin, FAQ schema, daily freshness check.

    → /status/

  2. ✓ shippedBorrow audiences you already own

    Popularity is distribution. The network's AI & tech sites already have readers.

    Inject a removable, self-updating "Fable is back — window closes July 7" module on 10 network homepages, deep-linking /what-to-run/; module rewrites itself into an evergreen guide link after the window.

    → live on robotnewstoday, bigdummiesguidetoai, aiaustintexas, atxtechnewsnow, austintechnews.live, atxtechtrends, aiwayback, memsist, wholetech, childrensfable

  3. ✓ shippedBe ready for the next wave before it breaks

    On July 8 the window closes and "fable 5 credits" becomes the query.

    Build /credits/ — what usage credits are, what Fable-class compute actually costs, a buy/don't-buy decision framework, and the subscription-first fallback ladder.

    → /credits/

  4. ✓ shippedBecome the page AI assistants quote

    Answer engines lift concise, schema-marked Q&As. That's GEO.

    Expand /faq/ to ~20 real search questions (is it down, why was it banned, is it free, why does it refuse, Fable vs Mythos…) with complete FAQPage JSON-LD.

    → /faq/

  5. ✓ shippedOwn the reference asset

    Every future retrospective needs a dated chronicle to cite.

    Build /timeline/ — the definitive launch → ban → comeback chronology, every entry with a primary source and Event JSON-LD.

    → /timeline/

  6. ✓ shippedTurn the manual into evergreen pages

    "Why is Fable 5 slow" and "what effort level" are durable how-to searches.

    Build /effort/ — the four effort levels in plain English, the two failure modes, and a task→effort picker table, sourced to the official playbook.

    → /effort/

  7. ✓ shippedMake every page a doorway to three more

    Session depth and crawl equity are earned with honest internal links.

    Add contextual "Keep reading" blocks (3-4 hand-mapped links) to every article, recipe, and answer page — marker-based, so they're maintainable.

    → 34 pages linked

  8. ✓ shippedCapture the deadline-driven visitor

    The window brings people once; give them a reason to come back July 7.

    Add an add-to-calendar file for the July 7 close (with a built-in reminder alarm) plus RSS and live-status hooks under the homepage countdown clock.

    → calendar file on the homepage clock

  9. ✓ shippedGet the sister site rowing the same direction

    claudefieldguide.com still told the June story — stale info next door hurts both.

    Sweep claudefieldguide.com to post-return reality (window, Sonnet 5, classifier) and cross-link the two guides where each is strongest.

    → swept + cross-linked

  10. ✓ shippedLook good when shared

    The old share image predated the shutdown — every share told a dead story.

    Regenerate the OG/social card ("~~Fable is gone.~~ Fable is back." with the live-status pill), add full OG/Twitter meta, and publish this roadmap page itself.

    → you're reading it

Moral: "make it popular" decomposes into answer the live question, be where readers already are, and be the citable source when the story moves again.

Live