Use Steps for procedures whose order matters. The component keeps the article reading flow intact: a quiet numbered rail provides orientation while headings, paragraphs, links, lists, and code retain their native Markdown roles.
Ordered list syntax
Wrap one Markdown ordered list in a :::steps container. Each top-level list item becomes one step.
:::steps[Production deployment]1. **Clone and prepare the workspace**
Clone the repository and enter the project directory.
```powershell git clone https://github.com/LyraVoid/Shirone.git Set-Location Shirone ```
2. **Install dependencies**
Use the repository's pinned package manager.
```powershell pnpm.cmd install ```
3. **Run project checks**
Confirm Astro diagnostics and TypeScript checks pass.
```powershell npx.cmd astro check pnpm.cmd type-check ```
4. **Build the production site**
Generate the static site and search index.
```powershell pnpm.cmd build ```:::Production deployment
Clone and prepare the workspace
Clone the repository and enter the project directory.
Terminal window git clone https://github.com/LyraVoid/Shirone.gitSet-Location ShironeInstall dependencies
Use the repository’s pinned package manager.
Terminal window pnpm.cmd installRun project checks
Confirm Astro diagnostics and TypeScript checks pass.
Terminal window npx.cmd astro checkpnpm.cmd type-checkBuild the production site
Generate the static site and search index.
Terminal window pnpm.cmd build
Options
:::steps[Title]ortitle="Title"adds a visible label and accessible name.start=4changes the first displayed step number.- The container must contain exactly one ordered list. Invalid or mixed input remains ordinary readable Markdown instead of being interpreted heuristically.
- Rendering is completed during the site build and adds no client JavaScript or network requests.
Share Article
Generate a share poster or copy the link to share this article.
Continue reading
Take another route
A consistent pick from other articles
Last updated on , 1 days ago
Some content may be outdated