Maintained product history

Changes worth remembering.

  1. 21

    A freshness pipeline for the catalogs

    catalog-freshness reports expired funding deadlines, stale verifications, and — on request — probes every launch destination for death, redirects, and hijacks.

    • Added tooling/scripts/catalog-freshness.mjs: offline staleness report plus an opt-in --probe liveness sweep; findings are a report, never a mutation.
    • First run caught six funding programs still marked "Open now" with passed deadlines — now correctly "Next cohort or waitlist".
    • Added the catalog-freshness skill so the refresh loop is a documented capability, not institutional memory.
  2. 20

    One search box for the whole site

    A unified index spanning all 1,250 public entries — products, ideas, funding programs, launch destinations, tools, learnings, and docs.

    • Added /search: client-side search with per-type filter chips and ?q= / ?type= deep links.
    • Added /search.json: the same index as a machine endpoint — agents fetch once and filter on title+summary+keywords.
    • Search joins the primary nav; /search.md, sitemap, llms.txt, and /api/ai register it for crawlers and agents.
  3. 19

    Public domain-rank board and the drank skill

    The archived drank tracker's DR history became a public board at /ranks, and drank itself joined the capability register as a credential-free skill.

    • Imported the checked-in fleet DR snapshot — 29 owned domains with weekly Ahrefs DR history — into src/data/domain-ranks.json.
    • Added /ranks, /ranks.json, and /ranks.md: ranked table with per-domain deltas, provenance, and an explicit not-reported-vs-zero rule.
    • Added tooling/skills/drank so DR lookup is a cataloged agent skill alongside psi-swarm; the tooling register now lists 100 capabilities.
    • Linked the board from the footer, sitemap, llms.txt, and /api/ai.
  4. 18

    Every catalog entry became a page

    Each launch destination, funding program, idea, and tool now has its own indexable URL in the sitemap.

    • Extended /launchdesk/<domain> from playbooked rows to every active destination — 845 catalog records with verbatim source claims.
    • Added /ideas/<slug> pages for all 48 public scored ideas with full reasoning.
    • Added /tools/<id> pages for all 99 reusable capabilities, linking back to their canonical source.
    • Registered all entity pages in sitemap.xml and cross-linked every index row to its detail page.
  5. 17

    The funding workspace moved onto the site

    The Funding & Accelerators workspace became a native public directory — no more living inside Notion.

    • Imported all 184 programs into a checked-in dataset rendered at /funding, one row per specific program.
    • Reproduced the workspace’s sixteen decision views as public presets with their original filters and ordering.
    • Gave every program a full record page and JSON twin at /funding/<slug> and /funding/<slug>.json.
    • Published the strategy, application materials, methodology, and archive documents alongside the directory.
    • Kept uncertainty visible: evidence quality, website status, and unresolved rows are shown rather than smoothed away.
  6. 16

    The spotlight became a product ledger

    The homepage hero stopped pretending the workshop wall has four panes.

    • Replaced the half-empty featured-pane grid with a ruled ledger of full-width product plaques.
    • Gave each spotlight product a persistent tone marker so the pane-color story works on touch, not only hover.
    • Kept the steel frame, limestone ground, Schibsted type, and the atelier photograph as a masked edge glimpse.
  7. 15

    LaunchDesk research passed four hundred playbooks

    The launch catalog gained another hundred researched destinations in descending authority order.

    • Added over a hundred researched playbooks covering submission routes, requirements, and honest unknowns.
    • Quarantined dead or gated destinations instead of keeping optimistic claims.
    • Re-measured 898 active destinations with the live verification sweep.
  8. 14

    Launch playbooks became an executable toolkit

    LaunchDesk grew into a working kit: a per-product coverage ledger and hundreds of researched destination playbooks.

    • Published the free agent-executable launch toolkit at /launchkit.
    • Added a per-project launch coverage ledger so submissions map back to products.
    • Grew the playbook library past three hundred researched destinations.
  9. 13

    The directory started measuring visits

    Watchtower browser telemetry now records public page usage so the surface can be evaluated on evidence.

    • Added Watchtower browser telemetry to the public pages.
  10. 12

    Learnings became an editorial series

    Eleven first-party articles now document how the launch catalog is researched, verified, and maintained.

    • Published eleven LaunchDesk articles covering catalog research, data quality, quarantine, and submission practice.
    • Wired every article into the markdown and agent-readable surfaces automatically.
  11. 11

    LaunchDesk moved onto the workshop

    The launch-destination catalog left private tooling and became a public page at /launchdesk.

    • Rendered the thousand-destination catalog natively with authority, link-policy, and pricing columns.
    • Kept source claims, quarantine state, and unknown-vs-zero semantics visible instead of smoothed over.
  12. 10

    Product profiles became generated

    The public catalog is now projected from the private source catalog rather than edited by hand.

    • Exposed the shared public catalog and generated the profile project data from it.
    • Revalidated the reviewed portfolio categories and directory rows.
  13. 09

    The site hardened its plumbing

    Every public route now answers HEAD requests correctly, and the display typeface is self-hosted.

    • Added HEAD parity on every public route.
    • Self-hosted the Schibsted Grotesk webfont.
  14. 08

    Profiles gained depth and the workshop an identity

    Project pages expanded into fuller profiles, and the studio identity became its own page.

    • Published expanded project profiles and a dedicated studio identity page.
    • Added repository issue readers so product roadmaps live with the code.
    • Corrected AI provider symbols across the public surface.
  15. 07

    Ideas and tools joined the public workshop

    The separate ideas surface was absorbed into /ideas, and shared tooling became a public catalog at /tools.

    • Moved the scored ideas catalog onto /ideas inside the workshop theme.
    • Published the tools catalog of shared skills, scripts, and workflows.
    • Unified the interior pages under one steel-and-limestone system.
  16. 06

    The directory opened to every project — and to agents

    All Fleet projects became browsable at /projects, and the site started answering machine readers in their own formats.

    • Published the complete Fleet project directory while keeping the homepage curated.
    • Added markdown content negotiation, an OpenAPI surface, and llms endpoints for agent readers.
    • Distilled repeated project anatomy and fixed the shared workshop frame.
  17. 05

    Tokens spent for the world became a public ledger

    SaaS Maker now publishes verified aggregate model usage from its products as a cumulative studio measure.

    • Seeded the ledger with CodeVetter’s authoritative lifetime and latest-day token records.
    • Added a procedural Three.js globe, exact UTC recency, and privacy-safe regional pulse support.
    • Kept the verified metrics readable with reduced motion, no script, or unavailable WebGL.
  18. 04

    Product history moved onto the products

    SaaS Maker now treats each maintained product website as the owner of its public release history.

    • Added this product-owned changelog to SaaS Maker.
    • Changed directory changelog links to open the product website instead of raw commit history.
    • Changed roadmap links to open GitHub Issues for public repositories.
  19. 03

    The directory became a workshop

    The public directory and product detail pages moved into one architectural workshop system.

    • Rebuilt product discovery as a responsive steel-and-glass product wall.
    • Brought internal product detail pages into the same visual language.
    • Expanded the maintained public directory while keeping private Fleet controls out.
  20. 02

    SaaS Maker became a focused public directory

    The separate SaaS Maker runtime was retired in favor of a smaller static public product surface.

    • Removed the abandoned dashboard, API, authentication, and internal control-panel features.
    • Kept the public directory on sassmaker.com and the private Fleet console separate.
    • Removed services and storage SaaS Maker no longer needed without changing product domains.
  21. 01

    Feedback became a backend-free package

    The maintained feedback capability was narrowed to a small React package that products control.

    • Removed SaaS Maker-owned submission, inbox, authentication, and storage services.
    • Let each integrating product decide how feedback is submitted and stored.

Looking for a particular product?

Browse all products