roadmap.sh is a map, not a course

nilbuild/developer-roadmap is the repository behind roadmap.sh. It collects interactive learning paths for developer roles, technologies, and career tracks: frontend, backend, DevOps, full stack, computer science, AI engineer, data engineer, machine learning, system design, Kubernetes, Rust, Go, React, Node.js, product management, engineering management, and many more.

The most useful way to read it is as a map. It is not a full course platform like freeCodeCamp. It is not a university-style curriculum like OSSU. It is not a single interview-prep book. roadmap.sh answers a different question: “What should I learn next, and how do the topics fit together?”

As of 2026-06, the repository has 356,750 stars, 44,191 forks, and 13 open issues. It is a TypeScript project, points to https://roadmap.sh, and was pushed on 2026-06-10. The current GitHub slug is nilbuild/developer-roadmap; the old kamranahmedse/developer-roadmap path resolves to the same repository. That detail matters because many older articles and bookmarks still use the previous owner path.

What is inside

The README lists a wide set of roadmaps. The core career paths include Frontend, Backend, DevOps, DevSecOps, Full Stack, QA, Product Manager, Engineering Manager, Software Architect, Data Analyst, Data Engineer, AI Data Scientist, AI Engineer, MLOps, Network Engineer, Cyber Security, Technical Writer, DevRel, Forward Deployed Engineer, and Game Developer.

The technology paths cover the usual developer stack: HTML, CSS, JavaScript, TypeScript, Python, Django, Go, Rust, Java, Kotlin, Spring Boot, C++, PHP, Laravel, Ruby, Rails, Android, iOS, Flutter, React, Next.js, React Native, Vue, Angular, Node.js, GraphQL, SQL, PostgreSQL, Redis, MongoDB, Elasticsearch, Docker, Kubernetes, Terraform, AWS, Cloudflare, Linux, Bash, and more.

The repository also has best-practice sections and question sets. The README links to backend performance, frontend performance, code review, API security, and AWS best practices, plus questions for JavaScript, Node.js, React, backend, and frontend. Recent roadmap directories include newer AI-focused paths such as ai-agents, ai-engineer, ai-red-teaming, claude-code, openclaw, and vibe-coding.

That breadth is the value. It lets a learner compare paths before committing months to one route.

Local development

The README gives a real local setup. It is not an install command for a library; it is how to run the roadmap.sh app locally. The README uses a shallow clone; this version shows the same setup with a normal clone so the command remains copyable here:

git clone [email protected]:nilbuild/developer-roadmap.git
cd developer-roadmap
pnpm add @roadmapsh/editor@npm:@roadmapsh/dummy-editor -w
pnpm install

Then run the development server:

pnpm dev

The README also says to rename .env.example to .env before running the app. That detail is easy to miss if you only copy the commands. If your goal is only to use the roadmaps, do not run the app locally. Use roadmap.sh. Local development is for contributing content, changing the site, or testing roadmap edits.

Contribution rules explain the product taste

The contributing guide is the best source for understanding roadmap.sh’s editorial model. For a new roadmap, contributors can open an issue with a textual roadmap or build one in the roadmap editor and submit the link. For an existing roadmap, typo fixes go through markdown files, but adding or removing nodes should start as an issue.

The important rule is that the project is not trying to include everything. The guide says the goal is to list the skills most relevant today. It asks contributors not to add things they have not evaluated personally, limits topic popups to concise content, and caps resources at 8 links per topic. It also rejects GeeksforGeeks links and discourages self-promotion.

That editorial stance is why the project has stayed readable. A roadmap that includes every tool becomes a directory. roadmap.sh works because it tries to rank topics by practical learning order and current relevance.

The license caveat

Do not treat the repository content like a permissive open educational resource. GitHub reports the license as NOASSERTION, and the license file is custom. It says the text and images are protected by copyright, allows personal use, allows sharing links to the repository or roadmap.sh, and restricts republishing images, project files, or content from the repository without prior consent. Read the license before copying roadmap images or content into a blog, newsletter, course, or internal wiki.

This matters more here than it would for a normal code library. The valuable asset is not just the app shell. It is the curated roadmap content.

Recent issues show it is an app now

The current issue tracker does not look like a static list. Recent issues include roadmap feedback for Network Engineer and LeetCode, a quiz problem where question length exceeds 500 characters, an AI-related 404, and a leaderboard bug where an “Active” list shows fewer unique users than expected. Recent pull requests include fixes for AI quiz verification and resource-link additions for product-manager and server-side-game-developer topics.

Those issues say roadmap.sh has grown into an interactive learning product. Roadmaps, quizzes, questions, leaderboards, and generated or editor-backed content all have product bugs. That is different from a markdown-only awesome list where the main failure mode is a stale link.

For users, this is a good sign and a warning. The site has more learning surface than a static diagram, but the moving parts mean some newer paths or quizzes can have rough edges.

Compared with freeCodeCamp, OSSU, CIU, and system-design-primer

freeCodeCamp/freeCodeCamp is a learning platform with interactive lessons, projects, progress, and certificates. Choose it when you want guided practice and proof of completion. roadmap.sh is better when you want to decide what to learn next before choosing a course or project.

OSSU computer-science is a self-taught CS curriculum map. As of 2026-06 it has 204,803 stars and points learners through external courses. Choose OSSU when your goal is a CS-degree-like path. Choose roadmap.sh when you need role-specific or technology-specific paths such as backend, DevOps, AI engineer, or Kubernetes.

The Odin Project curriculum is a structured web development path. It is narrower than roadmap.sh and more course-like. It is useful if you already know web development is the route. roadmap.sh is useful before that decision, or when you want to branch into another track.

jwasham/coding-interview-university is an interview-oriented study plan with 351,116 stars as of 2026-06. It is better for long-form interview preparation. donnemartin/system-design-primer has 352,595 stars as of 2026-06 and is better for system design interviews. roadmap.sh covers both broader career planning and many technology tracks, but it will not replace focused interview prep.

When roadmap.sh is the right choice

Use roadmap.sh at the start of a learning cycle, when you are trying to choose a path, audit gaps, or explain a career route to someone else. It is especially good for learners who feel lost between many topics and need a visual order. It also helps teams define onboarding tracks: frontend basics, backend basics, DevOps basics, or a language-specific path.

Do not use it as your only learning material. A roadmap tells you what to study, but mastery still comes from building projects, reading docs, debugging real failures, and getting feedback. For practice, pair it with codecrafters-io/build-your-own-x, freeCodeCamp, The Odin Project, official docs, or project work.

The repo’s strength is orientation. The risk is checklist learning: marking nodes without doing the work. Treat each node as a decision point, not a trophy.

Star curve reading

The sampled star history shows developer-roadmap growing from a 2017 learning map into one of the largest education repositories on GitHub. The curve is sampled because the repo is very large, so individual point spacing should not be overread. The durable signal is that role-based learning paths have stayed relevant across frontend churn, cloud adoption, interview prep, and the recent AI tooling cycle.

The latest README confirms that the project keeps adding new paths rather than only maintaining the classic frontend and backend maps. That is why the repo still matters.

For a platform with exercises and certificates, read freeCodeCamp/freeCodeCamp. For project ideas after choosing a path, see codecrafters-io/build-your-own-x. For broad developer resource lists, see sindresorhus/awesome. The wider discovery hub is GitHub trending repositories.

FAQ

What is nilbuild/developer-roadmap? It is the GitHub repository behind roadmap.sh, a set of interactive developer roadmaps, guides, best practices, and questions.

Is roadmap.sh the same as a course? No. It is mainly a learning map. It tells you what to learn and in what order, but you still need courses, docs, projects, and practice.

Why do some links mention kamranahmedse/developer-roadmap? That older GitHub path now resolves to nilbuild/developer-roadmap. As of 2026-06, the current slug is nilbuild/developer-roadmap.

Can I reuse roadmap.sh content in my own article or course? Read the license first. The repository uses a custom copyright notice, not a standard permissive content license, and restricts republishing content without consent.

How do I run roadmap.sh locally? Clone the repository, run pnpm add @roadmapsh/editor@npm:@roadmapsh/dummy-editor -w, run pnpm install, rename .env.example to .env, then run pnpm dev.