mirror of
https://github.com/hanzo-docs/docs.git
synced 2026-10-25 04:20:02 +00:00
zeekayandzooqueen
13abc4145f
packages/shadcn (@hanzo/docs-shadcn) existed to emit "npx shadcn@latest add <component>" snippets into rendered docs, and examples/next-shadcn existed to demo it. A docs page that emits an install command for a DOM-only component library puts that library in the reader's app, which is the same defect as depending on it here. Nothing else in the workspace imported either one, so both are deleted rather than repointed. The commerce recipes and storefront pages taught the same thing more quietly: every code block a reader copies was styled with tailwind utility classes. Tailwind classes and raw <div>/<button>/<select> are DOM-only, so a storefront built from these pages could never run on iOS or Android. They now use @hanzo/gui components with style props — XStack/YStack instead of flex and grid classes, Card/Button/Input/Select/Form instead of bare elements, theme tokens ($color2, $borderColor, $red10) instead of gray-500 and red-500. The product grid becomes a wrapping XStack because Tamagui targets flexbox on native, where CSS grid does not exist. zen5.mdx hand-rolled a highlighted box out of tailwind on fumadocs CSS vars; it uses the framework's own <Callout>, which is what that box already was. Authored-docs tailwind goes 17 files / 467 class tokens -> 0. What the counter still reports is not tailwind: Bootstrap classes in a Thymeleaf template in the Java/Spring IAM guide, custom CSS class names paired with <style> blocks in the IAM login-customization guide, one CHANGELOG entry, and content/docs/projects/**, which is gitignored and regenerated by sync-project-docs.ts from upstream repos.
Examples
The apps here are used to generate code examples for our docs.
Please be careful.