Pages reached from an email link or bookmark have no site chrome #49

New Issue

2026-08-18T11:28:36-05:00

bermudalamb commented

2026-08-18 11:28:36 -05:00

Problem

Three routes are entered from outside the app, and all three render a bare Card with no header:

Route	Entered from	Links out
`/verify-email?token=`	the verification email	`/account` only
`/reset-password?token=`	the reset email	`/forgot-password`, `/login`
`/privacy`	storefront footer, the register form, bookmarks	none at all

A customer clicking a link in their inbox lands on a page with no logo, no cart, and no route into the shop. /privacy is the worst of the three: it is linked from the footer and from the registration consent text, so customers genuinely arrive there, and it offers no way onward whatsoever.

Why these cannot be modals

Unlike the account and auth views, there is no originating page to close back to — the customer arrives from their mail client or a bookmark with no history behind them. A modal needs something underneath it and somewhere to return to; neither exists here.

So these want the opposite treatment: give them the site chrome, so the header provides navigation the same way it does on the storefront.

Scope

Render Layout + Header on these three routes, or extract the storefront chrome into a shared wrapper they can use
/privacy in particular should look like part of the site, since it is a page customers are directed to for a legal purpose and may link to

## Problem Three routes are entered from *outside* the app, and all three render a bare `Card` with no header: | Route | Entered from | Links out | | --- | --- | --- | | `/verify-email?token=` | the verification email | `/account` only | | `/reset-password?token=` | the reset email | `/forgot-password`, `/login` | | `/privacy` | storefront footer, the register form, bookmarks | **none at all** | A customer clicking a link in their inbox lands on a page with no logo, no cart, and no route into the shop. `/privacy` is the worst of the three: it is linked from the footer and from the registration consent text, so customers genuinely arrive there, and it offers no way onward whatsoever. ## Why these cannot be modals Unlike the account and auth views, there is no originating page to close back to — the customer arrives from their mail client or a bookmark with no history behind them. A modal needs something underneath it and somewhere to return to; neither exists here. So these want the opposite treatment: give them the site chrome, so the header provides navigation the same way it does on the storefront. ## Scope - Render `Layout` + `Header` on these three routes, or extract the storefront chrome into a shared wrapper they can use - `/privacy` in particular should look like part of the site, since it is a page customers are directed to for a legal purpose and may link to ## Related Same root cause as the account and auth issues: only `/`, `/admin` and `/cart` currently render `Layout` + `Header`.

bermudalamb added this to the Initial Build project 2026-08-18 11:42:29 -05:00

bermudalamb self-assigned this 2026-08-18 11:42:34 -05:00

bermudalamb referenced this issue

2026-08-18 15:47:21 -05:00

My Account is a navigational dead end #48

bermudalamb closed this issue

2026-08-18 16:18:01 -05:00

bermudalamb removed this from the Initial Build project 2026-08-18 16:51:38 -05:00

Sign in to join this conversation.