2. Separate explanation from lookup
Add Reference as another content mount rather than another branch in a local active_page enum. The sidebar explicitly orders its entries; the article still comes from Markdown.
Search is an enhancement over the generated content. Enabling it emits the index and browser search assets. It does not turn this Static site into a search server, and the articles remain readable without JavaScript.
{"id":"fission-tabs-1","tabs":[{"index":0,"label":"fission.toml","value":"fission-toml"},{"index":1,"label":"src/home.rs","value":"src-home-rs"},{"index":2,"label":"site/reference-sidebar.toml","value":"site-reference-sidebar-toml"},{"index":3,"label":"content/reference/project.mdx","value":"content-reference-project-mdx"}]}
{"id":"fission-tabs-1","index":0,"label":"fission.toml","value":"fission-toml"}
targets = ["static-site"]
[app]
name = "atlas-docs"
app_id = "rs.example.atlas.docs"
[site]
entry = "crate::site_app"
title = "Atlas Docs"
description = "Task guides and precise configuration reference."
base_url = "https://atlas-docs.example.com"
out_dir = "dist/site"
default_locale = "en-US"
locales = ["en-US", "es-ES"]
generate_sitemap = true
generate_robots = true
[site.code_highlighting]
enabled = true
[[site.nav]]
title = "Learn"
href = "/docs/overview/"
[[site.routes]]
path = "/docs"
source = "content/docs"
template = "fission::site::documentation"
sidebar = "site/docs-sidebar.toml"
[site.search]
enabled = true
output_path = "search"
min_token_len = 2
[[site.nav]]
title = "Reference"
href = "/reference/project/"
[[site.routes]]
path = "/reference"
source = "content/reference"
template = "fission::site::documentation"
sidebar = "site/reference-sidebar.toml"
{"id":"fission-tabs-1","index":1,"label":"src/home.rs","value":"src-home-rs"}
use fission::prelude::*;
fission_component! {
pub DocumentationHome<()> {}
view(_home, _state, cx) {
let tokens = &cx.view.env().theme.tokens;
} =>
Container(Column(gap: tokens.spacing.l, children: [
SemanticsRegion(identifier: Some("site-heading-1:atlas-docs".into()), child:
Text(cx.tr("home.title")).size(tokens.typography.heading1_size)),
Text(cx.tr("home.description")),
Link::to(cx.tr("home.learn"), "docs/overview/"),
Link::to(cx.tr("home.reference"), "reference/project/"),
])).padding_all(tokens.spacing.l).bg(tokens.colors.background)
}
{"id":"fission-tabs-1","index":2,"label":"site/reference-sidebar.toml","value":"site-reference-sidebar-toml"}
[[items]]
title = "Project record"
href = "/reference/project/"
level = 1
{"id":"fission-tabs-1","index":3,"label":"content/reference/project.mdx","value":"content-reference-project-mdx"}
---
title: Atlas project record
description: Fields and constraints for the plan.txt record used by the first-project guide.
---
This is the contract used by our example plan, not a Fission manifest schema.
## Outcome
Required. One sentence naming the result the project should produce. Keep implementation steps in Next step instead.
## Owner
Required. The person responsible for coordinating the next decision. This label does not grant access or establish an authenticated identity.
## Next step
Required. One action someone can take now. Replace it when that action is complete; do not keep several conflicting next steps.
## Example
```text
Outcome: publish the support handover guide
Owner: the release coordinator
Next step: ask support which questions are missing
```
[Create a first project](/docs/learn/quickstart/) explains why these fields are useful.
{"id":"fission-tabs-1"}
Search for outcome, then open the project-record reference. Follow its link back to the guide. With JavaScript disabled, verify that both direct routes and the page-outline links still work.
Show the app previewHide the app preview
Show the app preview
Hide the app preview