A learning library for builders, structured around two primary experiences - structured learning and knowledge discovery. The platform architecture is intentionally simple.
Topics are neither - they're labels that help users find content across both.
A structured sequence of Articles - a roadmap through a subject, from first principles to production.
A standalone piece of knowledge - the core content unit of StackNova.
A label for discovery and filtering. Not a content type - never a container.
A Path is a curated learning journey: a roadmap through a subject, from first principles to production. Paths primarily organize Articles into a deliberate learning sequence.
An Article is the core content unit of StackNova - a standalone piece of knowledge. Articles can take many forms; they live inside Paths but each one stands on its own.
Topics are organizational labels - not a content type. Articles belong to Topics; Topics don't own content directly - they surface related Articles across the library. One Article can belong to many Topics.
A three-level hierarchy creates real problems. A single Article often belongs to multiple Topics - "Docker" lives under Cloud, DevOps, and Platform Engineering all at once. Three levels force a choice the data shouldn't force.
Where does "Docker" live - under Cloud, DevOps, or Platform Engineering? All three. Forcing one parent means duplicating the content or losing it from the other two.
Topics are labels on Articles, not containers above them. The Article has one home in a Path and any number of Topic labels for discovery.
StackNova favors a flat, flexible knowledge architecture. Each piece has one job, and they compose without overlap.
provide structure
provide knowledge
provide discovery
This keeps the library scalable, searchable, and easy to navigate as the platform grows.