A Map is a curated index - a page that tells you where to read, in what order, and why. Maps do not carry new knowledge; they organize existing Articles into a useful traversal. Some span more than one Path. Open one when you want a guided reading order through a whole subject in a single session.
Nine Maps in the library right now - two broad stacks for Web and AI, a narrower cut on the developer-facing AI surface, the designer's route through Claude Design, the engineering platform that runs underneath modern software, the route through internet search, and the marketing-analytics traversal alongside it.
The agent slice of the AI library, walked in full - from the idea and the context window through extensions and architectures to production and the frameworks that ship it.
The narrower cut of the AI library - just the tools that show up in a developer's day-to-day. Coding with Copilot or Claude Code, delegating to Claude Cowork, designing with Claude, generating images, plus the model and protocol underneath.
Every AI Path article sorted by layer - from foundation models up to the developer tools - with three reading orders for developers new to AI, agent builders, and depth-first readers.
The adoption route for a designer meeting Claude Design - the tool, the design-system language it reads, making yours machine-readable, and the fidelity ladder it hands back.
Every Design Path article sorted across eight layers - language and tokens, craft, vocabulary, fidelity, tools, handoff, brand and graphics - plus the AI design layer on top, with three reading orders.
The route through the search series - the pipeline inside a search engine, the two files that steer its crawler, the honest fundamentals of ranking well, the tags that measure the traffic, and the AI answer layer on top. Fourteen articles across Web and AI.
Getting traffic and measuring where it came from - the tagged links you send, the campaign they roll up into, the two ways people find you organically, and how you measure and optimize what comes back. Eight articles, the sibling of the internet-search map.
The platform craft underneath modern software - orchestration with Aspire, observability across services, and API documentation on top of OpenAPI. Three layers, every Engineering Path article in scope.
The flagship route across every Path - design, build, ship, and grow a product end to end, with AI woven through, plus three reading orders for founders, developers, and managers.
Every Web Path article sorted by layer - language, build tools, frameworks, API docs, orchestration - with a one-line reason and three reading orders for different readers. Pulls in API doc pieces from Engineering.
A Map is a peer of an Article, not a parent or child. Where an Article gives you a self-contained piece of knowledge ("What is Vite?"), a Map gives you a curated path through several Articles ("here is the Web stack in 2026 - read these eight in this order, organized by layer").
Maps can cross Paths. The Web stack Map sits under the Web Path conceptually but pulls in Engineering Articles where it makes sense. That is the whole point of having Maps as a distinct content type.
For the full model, read How StackNova is organized.