To improve documentation navigability and clearly communicate the state of our guides, we need to implement Starlight's built-in badge system. **Tasks:** - [ ] Define standard badge usage in our `CONTRIBUTING.md` guidelines so all developers use the same terminology: - `New` (`variant: success`) - `Updated` (`variant: note`) - `WIP` (`variant: caution`) - `Deprecated` (`variant: danger`) - `Advanced` (`variant: default`) - [x] Apply the `New` badge via frontmatter (`sidebar.badge`) to recently added pages (e.g., Database Schema, System Overview). - [x] Utilize the inline `<Badge />` component for specific advanced sections within articles (e.g., Redis Seat Locking). **Technical Example (Frontmatter):** ```yaml sidebar: badge: text: New variant: success ```
To improve documentation navigability and clearly communicate the state of our guides, we need to implement Starlight's built-in badge system.
Tasks:
CONTRIBUTING.mdguidelines so all developers use the same terminology:New(variant: success)Updated(variant: note)WIP(variant: caution)Deprecated(variant: danger)Advanced(variant: default)Newbadge via frontmatter (sidebar.badge) to recently added pages (e.g., Database Schema, System Overview).<Badge />component for specific advanced sections within articles (e.g., Redis Seat Locking).Technical Example (Frontmatter):