mirror of
https://github.com/django-components/django-components.git
synced 2025-08-31 03:07:19 +00:00
refactor: use .nav.yml to define page order instead of nav weights (#1000)
This commit is contained in:
parent
f36581ed86
commit
d5e45125dc
57 changed files with 95 additions and 231 deletions
5
docs/guides/devguides/.nav.yml
Normal file
5
docs/guides/devguides/.nav.yml
Normal 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
|
|
@ -1,5 +1,3 @@
|
|||
# Slot rendering
|
||||
|
||||
This doc serves as a primer on how component slots and fills are resolved.
|
||||
|
||||
## Flow
|
||||
|
|
|
@ -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"
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue