Your Dashboard
RoadmapOne place that shows your site is working — and lets you keep improving it.
After you publish, the dashboard becomes home base. It's not an analytics graveyard you visit once. It's a living control surface that mirrors everything Yoshi does for you: how your site scores, what it's made of, what changed, and what to do next.
A widget for every part of your site
The dashboard is built from cards, each one a window onto a real part of the pipeline:
| widget | what it tells you | status |
|---|---|---|
| Scores | Performance, Accessibility, Best-Practices, SEO — graded, per page, trending over time | soon |
| Pages | every page Yoshi made, searchable, with its individual health | planned |
| Content | your services, areas, reviews, photos — edit any of them, the site updates | planned |
| SEO | what you rank for, gaps to fill, schema + sitemap health | planned |
| Deploys | what's live, what changed, roll back if needed | planned |
| Blog | drafts + published posts that keep the site fresh | planned |
| Domain | your address, SSL, custom-domain status | planned |
The dashboard grows with the product. Every time Yoshi gains a new capability, a card for it appears here — sometimes before the feature is fully built, so you can see where things are heading (clearly marked Soon / Roadmap). The dashboard is a promise you watch get kept.
status: planned— the per-project dashboard is cycle 36; the Scores widget ships first off the live perf API.
Scores you can trust (not vanity numbers)
The first widget is Scores, and it's honest by design. Yoshi runs real Lighthouse audits against your
live site and grades every page — and it doesn't chase a fake "100" by gaming the measurement. A heavy
page scores lower because it is heavier; that's a signal you can act on, not a number we inflate.
status: soon (live perf API shipped; the per-project widget is wiring up).
Steering continues here
Everything you could do at preview, you can still do from the dashboard — in plain language. "Add a winter-tire service." "Refresh the homepage copy." "My hours changed." The dashboard is just preview & steer, after launch, with the added view of how your live site is performing. Build and manage are the same gesture.
For builders & agencies
If you manage many sites (the Studio), the dashboard scales up: a portfolio view across all your
clients, the same widgets per site, and bulk actions. (See Plans → Studio.) status: planned —
the builder/admin surface is cycle 2 (platform); this per-project view is its tenant-facing sibling.
🌳 Open questions (the inquisitive seam)
- What's the one number on the dashboard? Owners want a single "are we good?" glance. Is it an overall score? A "findability" index? A "this week" delta? Leaning: a plain-language health line — "Your site is fast, fully indexed, and gained 3 ranked pages this week" — over a raw number. Decision; cross-ref cycle 19 (scorecard), 36.
- Push vs pull. Should the dashboard notify ("a page slowed down," "you're now ranking for X") or wait to be visited? Leaning: proactive, sparingly — the dashboard earns trust by telling you good news unprompted. Cross-ref cycle 42 (background cognition).
- How much should Yoshi act on its own? If Yoshi notices a slow page, does it fix it automatically and tell you, or ask first? This is the agent-autonomy dial for the live site. Leaning: auto-fix the safe class (perf/SEO hygiene), ask for anything that changes meaning. Big decision; cross-ref cycle 19 self-improvement loop, 32 living.
- Editing content here vs in the conversation. Is the Content widget a structured editor (forms) or more chat? Probably both — chat for big moves, direct edit for "fix this typo." Cross-ref 03, cycle 32.
- What does a builder need that an owner doesn't? Portfolio health, client handoff, white-label branding, billing per client. Does that live here or in a separate Studio console? Cross-ref cycle 2, 37, 49 tier-2.