docs: migrate content files to TOML frontmatter
Migrate all 17 docs/content/ files from --- YAML to +++ TOML frontmatter delimiters and key = value syntax. Update 8 embedded frontmatter examples in 7 documentation pages to match (configuration, content-organization, getting-started, security, sections, sitemap, feeds, templates). Update configuration.md frontmatter reference table: add draft and aliases fields, correct date type from string to date.
This commit is contained in:
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Content Organization
|
||||
description: How the filesystem maps to your site structure
|
||||
weight: 2
|
||||
---
|
||||
+++
|
||||
title = "Content Organization"
|
||||
description = "How the filesystem maps to your site structure"
|
||||
weight = 2
|
||||
+++
|
||||
|
||||
sukr builds your site structure from your `content/` directory. No routing config needed — the filesystem _is_ the config.
|
||||
|
||||
@@ -53,7 +53,7 @@ sukr automatically discovers sections during the build:
|
||||
|
||||
The **section type** determines which template renders the index. It resolves in order:
|
||||
|
||||
1. **Frontmatter override** — `section_type: blog` in the section's `_index.md`
|
||||
1. **Frontmatter override** — `section_type = "blog"` in the section's `_index.md`
|
||||
2. **Directory name** — `content/blog/` becomes type `blog`
|
||||
|
||||
For the full section type reference (built-in types, frontmatter fields, and template dispatch), see [Sections](features/sections.html).
|
||||
@@ -67,11 +67,11 @@ Navigation builds automatically from:
|
||||
|
||||
Items sort by `weight` in frontmatter (lower first), then alphabetically.
|
||||
|
||||
```yaml
|
||||
---
|
||||
title: Blog
|
||||
weight: 10 # Appears before items with weight > 10
|
||||
---
|
||||
```toml
|
||||
+++
|
||||
title = "Blog"
|
||||
weight = 10 # Appears before items with weight > 10
|
||||
+++
|
||||
```
|
||||
|
||||
### Hierarchical Navigation
|
||||
|
||||
Reference in New Issue
Block a user