Skip to main content

Studio · Roadmap · 9 items

Roadmap.

What we’re actively building, what’s queued, and what we’re researching. The honest version — anything that ships moves to /changelog. Anything that gets dropped just disappears, no theatre.

Last edited by hand · paired with /pulse · /changelog

Now

1

In progress this week.

  1. Real capture set for the Hubenov case study

    The case study shipped with self-labelled placeholder shots rather than fabricated ones. Swapping in real captures — the public hero in Bulgarian locale, the operator console mid shipments list, the driver run-sheet on a phone — then regenerating blur data.

    Started 11d ago

Next

2

Queued — starting in days, not months.

  1. Mobile typography pacing pass on long pages

    A second look at /now, /colophon, /uses on 360px-wide screens. Tightening clamp values, reflowing dense grids, fixing places where editorial labels eat the horizontal budget.

  2. Newsletter widget in the client dashboard

    Subscribers see studio shipping cadence inside their dashboard so the relationship doesn’t live only in their inbox. Same data the public newsletter goes from, scoped to logged-in clients.

Exploring

6

Research. No commitment yet — these get published only if they earn their place.

  1. WebMCP origin trial — expose site actions to agents

    Chrome’s WebMCP origin trial lets a page declare real actions — run the audit, check availability, book a slot — as structured tools an in-browser agent can call, instead of scraping our DOM. Trialling on /audit and /book first, where the actions already exist.

  2. llms.txt as a route handler generated from site data

    Today’s /llms.txt is a hand-written static file. The next step is a route handler that derives it from the same data the pages render from — projects, journal, changelog — so the agent-facing summary can never drift from the human-facing site.

  3. Open-source extraction of BrowserFrame + AnimatedCounter

    Two of the components we keep reusing across client projects. Publishing them as `@gosmartr/ui` would be a marketing artefact and a forcing function for genuinely reusable design. Researching maintenance commitment.

  4. Studio soundtrack — per-project track on case studies

    Every project gets one track that played while we built it. Optional Spotify embed at the bottom of each case study, default off, screenshot-worthy when on. Personality move.

  5. Long-form essay series on /journal

    One properly-written 2,500+ word piece per month with marginalia, pull-quotes, real depth. Replaces the temptation to write five short blog posts that say nothing.

  6. Cursor-aware variable typography on the hero

    The variable-weight hero idea survived two redesigns without getting built. Parked as research: after Brief 07 stripped the home page back, any motion on the hero has to earn its place — this one hasn’t yet.

Want something on this list? Tell us about it