Why roadmaps
A single topic page answers one question well: what is a B-tree index, how does REST compare to GraphQL, why does a load balancer matter. But "how do I become a backend engineer" isn't one question; it's an ordering problem. Which concepts come first, which ones depend on which, and where do you actually stop and read something in full.
Roadmaps are our answer to that ordering problem. A roadmap is a short, curated sequence of steps for a role or goal, Backend Developer and Frontend Developer are live today, where every step links directly into a full Cloud Tech by Victor topic page.
What a roadmap is not
It is not a course, and it is not a tracked learning path. There's no account to create, no percentage-complete bar, and nothing saved about you between visits. A roadmap is a static, read-only map, the same seven categories and topic pages you'd find by browsing, just given a deliberate order and a reason for that order. That's a deliberate choice, not a missing feature: Cloud Tech by Victor doesn't do accounts, and a roadmap that "remembered" where you left off would need one.
How it's built
Each roadmap is one file, same as a topic: a title, a description, and an ordered list of steps, each optionally pointing at a real topic slug. If a step doesn't yet have a matching topic, it simply renders as plain text instead of a link; the roadmap can describe the full path even before every step has a page behind it yet.
Two roadmaps ship today, both built entirely from existing topic pages. More will follow as the topic library grows.