Home, refreshed
The first page you see when you open Subi now does more to orient you. The admin Home has been rebuilt from the ground up to the latest design frames — a cleaner layout that surfaces the setup steps you care about most and makes the path from install to first live subscription shorter.
What changed
Setup guide on the Home page. A four-step guide now sits at the top of your Home screen, pulling from your store's actual configuration data. Each step reflects your real progress — whether your selling plan is created, your widget is embedded, and your storefront setup is complete. New merchants get a guided start; existing merchants can dismiss the guide once it is no longer useful.
Three-column plan-type overview. Below the metrics bar, a redesigned plan-type grid shows your active plan types in a compact card format — the same three subscription modes (Subscribe & Save, Build-a-Box, Membership) with their current status. Clicking a card opens the updated plan-type creation modal, which now uses the same card design and is easier to scan.
Embed status with popover. An inline app-status row shows whether the Subi widget is embedded in your theme. If it is not, a popover explains the one-step installation — so you can catch a missing embed without digging through the theme editor.
Fixed: Membership plan-type card restored. A previous version of the Home page inadvertently lost the Membership block from the plan-type grid. It is now back and correct.
Why it matters
Most merchants log into Subi daily to check on subscriptions, not to configure anything. But for merchants in the first days after install, the Home page is the most important screen — it tells you whether Subi is working. The new setup guide and embed-status indicator make it obvious what is done and what is not, without requiring you to know where to look.
The plan-type modal redesign uses the same card format as the Home grid, so creating a new plan type and understanding which ones you already have are now one consistent mental model rather than two separate UI patterns.