docs: add task-oriented architecture guide#178
Merged
Conversation
mattsse
force-pushed
the
mattsse/docs-information-architecture
branch
from
July 16, 2026 14:44
43e212c to
b091bb9
Compare
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.
Summary
Why
The site currently starts with installation and API-specific guides but does not explain how the crates compose or how to choose features. Users and coding agents have to infer the correct path from a long flat navigation tree, while the installation page mixes onboarding with an incomplete crate inventory.
Impact
Newcomers can choose a workflow before learning the whole stack, library authors can identify the correct dependency boundary, and agents get explicit task and feature vocabulary for retrieval. Versioned Cargo snippets remain generated from the single documentation version source.