> For the complete documentation index, see [llms.txt](https://docs.trover.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trover.tech/engineering/verify-2026-09-08-design-deslop.md). # Verify 2026-09-08 — site de-slop, fonts, status chips, Trovernomics sync **Migration:** none. **Deploy:** frontend only, Vercel on push to `main`. ## What changed (apps/web) * **Fonts ship now.** `src/app/layout.tsx` loads Bricolage Grotesque (display), Hanken Grotesk (body) and IBM Plex Mono (mono) through `next/font/google` and defines `--font-display/--font-body/--font-mono` on ``. Before this the Tailwind families pointed at variables nobody defined, so every `font-mono` and `font-display` rendered in the OS default. `tailwind.config.ts` maps the families, adds `text-2xs` (11 px) and drops the unused `float`/`blink` animations. `globals.css` drops `.grid-bg/.noise/.scanline`. * **No status dots.** `components/ui/StateChip.tsx` is the one status vocabulary: an outlined pill, colour on text and border only, state written out, evidence after a middle dot ("live · block 56,795,430 · 12s"). It never animates. Replaced: `DataFreshness`, `NftLifecycleChip`, the trending board's minting pulse and "Live" dot, the DEX home's glowing dot, the discover minting strip, the two chart placeholders (now a skeleton bar), `Badge`. * **Cards.** `components/ui/Card.tsx` (16 px radius, hairline, flat fill, `inset` 12 px). `.surface` flattened to the same. Radii `rounded-3xl`/`[2rem]`/ `[1.75rem]`… → `rounded-2xl` sitewide; hairline+wide-shadow pairs lost the shadow; `backdrop-blur-xl/2xl` → `md`; coloured glows removed (DEX home dot, buy buttons, TroverMark halo, meme card). * **Type.** No text under 11 px (`text-[8|9|10px]` → `text-2xs`, 437 sites); interactive elements at 12 px; letter-spacing capped at `.08em` for labels and `-.02em` for display; `.eyebrow` is now a sentence-case muted label, and the kicker above headings was removed on tokenomics, home, mcp, how-to-buy, trust, stabledex, track, bridge, claim, hero, about, blog. * **Motion.** `Button` no longer lifts on hover; hover scales removed; the leaderboard reorder is an ease-out tween, not a spring. * **Copy.** English em-dashes in JSX replaced (16 lines); `tokenomics.upgradesCopy` in en/ru/az. * **Trovernomics page** rebuilt with `Card`, no kickers, a real `` for the levels, inline icons beside headings, 14 px body copy. Mechanics unchanged (two-road plan already live). * **`docs/nftomics-tokenomics.md`** now matches the page: two-road table (10/40/120/300 actions or 100k/300k/700k burn), `max(actions, burn)` rule, fusion discount on the burn road only, token settable after launch. ## Verify ``` cd apps/web && npx tsc --noEmit -p . for p in 'text-\[8px\]' 'text-\[9px\]' 'text-\[10px\]' animate-ping hover:scale 'rounded-\[2rem\]' rounded-3xl 'tracking-\[\.1'; do echo "$p $(grep -rn "$p" src --include='*.tsx' | wc -l)"; done # all 0 ``` On the site: DevTools → Network → Font shows three self-hosted woff2 files; no round coloured dot on the DEX home, the leaderboards or the terminal header; the tokenomics page has no uppercase label above any heading. ## Known residue `" — "` still appears in code comments and in ru/az copy (correct punctuation there). `.eyebrow` remains on table column headers and a few labels by design. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.trover.tech/engineering/verify-2026-09-08-design-deslop.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.