app/routes/legacy-public.tsx

Functions

Imports

It imports app/components/error-page.tsx. No module of this repo imports it.

Source

1import { Outlet } from "react-router";
2
3import { ErrorPage } from "~/components/error-page";
4
5import type { Route } from "./+types/legacy-public";
6
7/*
8 * TEMPORARY, and the ONE place the old public design's global CSS is loaded. The admin is Capsomer's and
9 * loads none of it (an unlayered reset would override Capsomer's layered rules), so every route outside
10 * /admin and /api nests under this layout. When the public site is rebuilt on Capsomer, delete this file,
11 * its `layout(...)` wrapper in routes.ts, routes/not-found.tsx's reason to exist, and the old sheets it
12 * imports; nothing in the admin reads any of them.
13 */
14import "~/app.css";
15
16// Capsomer's site header (site-header.tsx) and what it is built on, on every public page: its tokens, the
17// shared popover (the panels' placing and the tips) and dialog (the phone's sheet). Layered, so the site's
18// unlayered sheets below win wherever they touch the same thing.
19import "capsomer/tokens.css";
20import "capsomer/site-dustinedwards.css";
21import "capsomer/popover.css";
22import "capsomer/dialog.css";
23import "capsomer/site-header.css";
24
25// Module imports, not @import in app.css, which CSS drops after any rule.
26// The order is the cascade: do not sort.
27import "~/styles/public-chrome.css";
28import "~/styles/page-shell.css";
29import "~/styles/chrome-nav.css";
30import "~/styles/skip-link.css";
31import "~/styles/motion-print.css";
32// Last: shell.css must win where it and page-shell.css touch the same thing.
33import "~/styles/shell.css";
34
35export default function PublicLayout() {
36  return <Outlet />;
37}
38
39/*
40 * The public pages' error page, here and not only in root.tsx: React Router links the stylesheets of the routes
41 * down to the boundary that renders, so a boundary in root.tsx would show a public error page with none of the
42 * old public CSS. root.tsx renders the same ErrorPage for an error above this layout.
43 */
44export function ErrorBoundary({ error }: Route.ErrorBoundaryProps) {
45  return <ErrorPage error={error} />;
46}