refactor: use .nav.yml to define page order instead of nav weights (#1000)

This commit is contained in:
Juro Oravec 2025-02-23 22:44:12 +01:00 committed by GitHub
parent f36581ed86
commit d5e45125dc
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
57 changed files with 95 additions and 231 deletions

View file

@ -0,0 +1,5 @@
# `.nav.yml` is provided by https://lukasgeiter.github.io/mkdocs-awesome-nav
nav:
- JS and CSS rendering: dependency_mgmt.md
- Slot rendering: slot_rendering.md
- Using slot and block tags: slots_and_blocks.md

View file

@ -1,5 +1,3 @@
# Slot rendering
This doc serves as a primer on how component slots and fills are resolved.
## Flow

View file

@ -1,5 +1,3 @@
# Using `slot` and `block` tags
1. First let's clarify how `include` and `extends` tags work inside components.
When component template includes `include` or `extends` tags, it's as if the "included"