Feature: Organize documentation topics in beginner-friendly learning order
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 领域
- content, documentation
调研方向
该 issue 未指定文件、测试或入口点。首先查找文档主题当前是如何排序的，以及如何切换视图；当存在一个可选的、以学习为重点的排序，同时字母顺序的参考视图仍然可用，并且具有如 C 示例中那样定义的渐进顺序时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Feature request
I have checked existing issues and labels, and this feature appears to be frequent among the learners and followers. We follow your developed curriculum, and we do support it, but almost everybody finds it frustrating to navigate and search for each topic based on the standard order/structure.
Summary
Currently, all documentation topics are sorted alphabetically, which creates a poor learning experience for beginners and anyone studying a new technology for the first time. Alphabetical ordering places advanced concepts before fundamental ones (e.g., "Algorithm" appears before basic syntax in C documentation), making it difficult to follow a logical learning progression.
This feature should add an optional "Learning Paths" mode that organizes documentation topics in a structured, beginner-friendly order. Users could toggle between the current alphabetical view (maintained for reference use) and learning-focused view that follows natural learning sequences from basic to advanced concepts.
This enhancement would transform DevDocs from purely a reference tool into a more comprehensive learning platform while maintaining its core strengths, making it especially valuable for students, career changers, and developers learning new technologies.
Examples
In C documents (as well as other documents with similar issue)
Alphabetical sorting: Algorithm → Atomic → Basic Syntax → Variables
Ideal learning order: Basic Syntax → Variables → Functions → Algorithm → Advanced Topics
Thank you for your attention to this matter.
- 主要语言
- Ruby
- 星标
- 39.5k
- 派生
- 2.6k
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 13
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
freeCodeCamp/devdocs 的其他 Issue
-
docs/improvement
难度 2/5 1-3 小时 新手友好度 62/100
freeCodeCamp/devdocs#1989 · 4 条评论 · 4 个 reaction ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 20/100
freeCodeCamp/devdocs#2731 ·
维护者通常 1 天内回复
-
feature
难度 5/5 一周以上 新手友好度 25/100
freeCodeCamp/devdocs#2712 ·
维护者通常 1 天内回复
-
feature
难度 5/5 一周以上 新手友好度 30/100
freeCodeCamp/devdocs#2683 · 1 条评论 ·
维护者通常 1 天内回复
-
feature
难度 4/5 3-5 天 新手友好度 45/100
freeCodeCamp/devdocs#2673 ·
维护者通常 1 天内回复
查看 freeCodeCamp/devdocs 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 1/5 1 小时以内 新手友好度 90/100
TheOdinProject/curriculum#31423 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
oxidize-rb/rb-sys#807 ·