Information architecture
This section outlines how I defined the structure, labeling, and hierarchy of this portfolio and specifically, the Nimbuswiz documentation.
| Page | Coverage |
|---|---|
| Docs site structure | URL schema, nav hierarchy, content organization |
| Taxonomy | Content types, controlled vocabulary, labeling rules |
| Project roadmap | User segments, prioritized backlog, quarterly roadmap |
| Personas | Three deep personas for NimbusWiz, plus the cross-persona tensions that shape product decisions |
| Journey maps | Paired journey maps: a professional DevOps Engineer and a non-technical casual user through the same pipeline |