solutions-architecture
Небо - не пределSite about solutions architecture
Comments (0)
Sign in to leave a comment
Project Tasks
37 tasksGenerate system requirement document
Generate personas & user flows
Architecture
Workspace task plan
Create flow for Solutions architecture practitioner
Create flow for Site visitor evaluating architecture solutions
Landing
Architecture Content
Landing / Route Header
Landing / Hero Route Map
Landing / Annotation Band
Landing / Orientation Copy
Landing / Content Previews
Landing / Footer
Route Header
Footer
Fix Landing: The required station links all lead to the same generic content-list destination (), so…
Fix Landing review finding: frontend/src/components/Landing Hero Route Map.jsx: The…
Accept Landing as it is
Retry First Page
Fix Landing: The three station links use /architecture-content#${station.anchor} with anchors…
Fix Landing: The route line only draws once after intersection via and has no repeating timeline or…
Fix Landing review findings: frontend/src/components/Landing Hero Route Map.jsx: The three… (+1 more)
Architecture Content / Route Header
Architecture Content / Placard List
Architecture Content / Item Reader
Architecture Content / Footer
Create frontend_modules diagram
Create sequence diagram
Serve full architecture items with readable measure and diagram equivalents
Support browsing, category switching, and retry for architecture content
Serve placard lists with diagram data and failure recovery
Serve individual items with diagrams, categories, and load recovery
Serve Landing content previews with loading, empty, and retry states
Serve browsable placard listings with category moves and retry
Wire Architecture Content page to live content, categories, and recovery
Wire Landing page to live previews, navigation, and motion behavior
solutions-architecture
Make systems make sense.
Orientation
solutions-architecture is a public site about solutions architecture: the architectural approaches and solutions it covers, how they fit together, and the reasoning behind the technical decisions. Every page is open to read — no accounts, no sign-in.
It is for two overlapping groups of readers: solutions architecture practitioners who want to understand the approaches and solutions presented, and visitors evaluating architecture solutions who need to compare them and judge whether they fit their needs.
The content is organised to be browsed by category label and route number, following the solution stages — DiscoverDesignDeliver — so you can scan, compare, and settle into the parts that matter.
Public reading surface · no sign-in required
03Route previews
Selected architecture lines
Three published lines from the architecture content, each staged at a numbered stop. Open any placard to read the full item.
Bounded contexts before components
Why the boundary decision precedes the component decision in any solutions architecture.
Contracts at the seams
Designing the interfaces between systems so integration stays legible as the solution grows.
Runbooks as architecture
Treating operational procedure as a first-class architectural artefact rather than an afterthought.
solutions-architecture
Make systems make sense.
Orientation
solutions-architecture is a public site about solutions architecture: the architectural approaches and solutions it covers, how they fit together, and the reasoning behind the technical decisions. Every page is open to read — no accounts, no sign-in.
It is for two overlapping groups of readers: solutions architecture practitioners who want to understand the approaches and solutions presented, and visitors evaluating architecture solutions who need to compare them and judge whether they fit their needs.
The content is organised to be browsed by category label and route number, following the solution stages — DiscoverDesignDeliver — so you can scan, compare, and settle into the parts that matter.
Public reading surface · no sign-in required
03Route previews
Selected architecture lines
Three published lines from the architecture content, each staged at a numbered stop. Open any placard to read the full item.
Bounded contexts before components
Why the boundary decision precedes the component decision in any solutions architecture.
Contracts at the seams
Designing the interfaces between systems so integration stays legible as the solution grows.
Runbooks as architecture
Treating operational procedure as a first-class architectural artefact rather than an afterthought.
No comments yet. Be the first!