Repository navigation
Modernise documentation and enable agent-friendly output - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the duplicated long homepage with a responsive hero and focused guides for installation, inputs, execution, composition, Baked, and agent inspection. Preserve the existing page routes and detailed examples in Markdown references, with explicit sidebar groups.
Use Ranvier's published Partas.Nacara theme and AgentFriendly, Directives, and OgImage plugins. AgentFriendly now generates llms.txt, llms-full.txt, Markdown copies and alternate links; remove the old static index and duplicate post-build merge. Enable link validation after agent files are written.
Validation:
test --quick): 558 suite tests and 22 Debug/Release compiler probes passed; 10 ignored tests.The existing FSharp.Compiler.Service exact-version restore warning remains. The published Partas.Nacara packages require FSharp.Core 11, confined to the documentation project; package versions and library targets are unchanged.