bug: title of main homepage is not set from project description #112

Closed
opened 2026-07-25 20:41:10 +00:00 by hugo · 1 comment
Owner

the full render of the home page (any language) is not using the project description as title as it is done in bDS2. This is required, since the main home page otherwise just has no title showing.

the full render of the home page (any language) is not using the project description as title as it is done in bDS2. This is required, since the main home page otherwise just has no title showing.
hugo added the bug label 2026-07-25 20:41:10 +00:00
hugo added the critical label 2026-08-01 07:56:17 +00:00
Author
Owner

Implemented in commit 085a3e8. Root and localized home routes now receive the bDS2-compatible core archive context, so existing Liquid list templates render the project description as the visible homepage heading while retaining it as the document title. Updated the Allium ArchiveContext contract and README, and added a full-generation regression test covering main and secondary languages. Verified with cargo fmt --check, cargo build --workspace, Clippy with -D warnings, cargo test --workspace, allium check specs, and allium analyse specs. Neutral review against the issue, bDS2 build_root_outputs behavior, and the Allium template contract found no remaining gaps.

Implemented in commit 085a3e8. Root and localized home routes now receive the bDS2-compatible core archive context, so existing Liquid list templates render the project description as the visible homepage heading while retaining it as the document title. Updated the Allium ArchiveContext contract and README, and added a full-generation regression test covering main and secondary languages. Verified with cargo fmt --check, cargo build --workspace, Clippy with -D warnings, cargo test --workspace, allium check specs, and allium analyse specs. Neutral review against the issue, bDS2 build_root_outputs behavior, and the Allium template contract found no remaining gaps.
hugo closed this issue 2026-08-01 08:12:21 +00:00
Sign in to join this conversation.