ui-libraries/material/docs/README.md
The documentation site is built with Astro Starlight and reuses it's project structure.
docs/
βββ public/
βββ src/
β βββ assets/
β βββ content/
β β βββ docs/
β β βββ config.ts
β βββ env.d.ts
βββ tests/
βββ astro.config.mjs
βββ package.json
βββ tsconfig.json
βββ
Starlight looks for .md or .mdx files in the src/content/docs/ directory. Each file is exposed as a route based on its file name.
Images can be added to src/assets/ and embedded in Markdown with a relative link. They will be optimized
for download size and also their width and height will be extracted so the framework can render them without
ugly content shifts.
Static assets, like favicons, can be placed in the public/ directory. Note that images in this folder will
not be processed and optimized by Starlight.
The docs use a lot of autogenerated content. First create all the screenshots which will be placed at src/assets/generated/.
Generate the screenshots:
cargo run -p slint-docsnapper -- -Lmaterial=$PWD/ui-libraries/material/src/material.slint ui-libraries/material/docs
Build the docs:
cd ui-libraries/material/docs
pnpm i
pnpm run build
This will build the site and place it in dist/.
To run the live hot reloading dev server run in the astro directory:
cd docs/
pnpm start
This will start the dev server at localhost:4321/docs/.
All commands are run from the root of the project, from a terminal:
| Command | Action |
|---|---|
pnpm i | Installs dependencies |
pnpm start | Starts local dev server at localhost:4321 |
pnpm build | Build your production site to ./dist/ |
pnpm preview | Preview your build locally, before deploying |
pnpm run astro ... | Run CLI commands like astro add, astro check |
npm run astro -- --help | Get help using the Astro CLI |
Check out Starlightβs docs, read the Astro documentation, or jump into the Astro Discord server.