Build a student-informed content and SEO roadmap
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- next.js, typescript
- 领域
- content, documentation, search
调研方向
Start with related issue #22, then read the README and content guide to understand the existing catalogues, sample note files, and SEO setup. Map student audiences and their needs to the first courses, branches, and placement topics, then define review and publishing criteria for each resource type. Done means a phased, student-informed roadmap that covers the listed acceptance criteria and updates the README or content guide where the publishing process changes.
由索引模型根据 Issue 内容生成。
描述
Context
The course catalogue currently has no published subjects, and the guides and jobs catalogues are empty. Sample note files exist but are intentionally not published. The site already has technical SEO foundations, so useful reviewed content and accurate discovery signals need to grow together.
Proposal
Create a phased, student-informed plan for publishing original engineering study resources and placement guidance, then make genuinely useful pages easy to discover. Prioritize accuracy and curriculum fit over page count or arbitrary word-count targets.
Acceptance criteria
- Identify the first student audiences, courses/branches, and placement topics to serve, using student needs to prioritize them.
- Define review criteria and source/copyright expectations for notes, guides, and job/internship listings.
- Publish only complete, useful resources; keep empty or placeholder routes out of the index and sitemap.
- Ensure published pages have accurate titles, descriptions, canonical URLs, structured data where appropriate, and useful internal links.
- Check the live sitemap, robots rules, broken links, mobile usability, and search performance as content is added.
- Avoid thin, repetitive, keyword-stuffed pages and unsupported promises about rankings or placement outcomes.
- Update the README/content guide when the publishing process or available catalogues change.
Related planning issue: #22.
- 主要语言
- TypeScript
- 星标
- 1
- 派生
- 1
- 平均合并
- 8 小时 58 分钟
- 30 天内合并 PR
- 37
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
procoderji-com/procoderji 的其他 Issue
-
area:frontend bug
难度 2/5 1-3 小时 新手友好度 62/100
procoderji-com/procoderji#104 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
procoderji-com/procoderji#36 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 85/100
procoderji-com/procoderji#35 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 79/100
procoderji-com/procoderji#34 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 90/100
procoderji-com/procoderji#33 ·
维护者通常 1 天内回复
查看 procoderji-com/procoderji 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug platform-android
难度 2/5 1-3 小时 新手友好度 68/100
Termix-SSH/Mobile#146 · 1 条评论 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
devswha/herdr-web-ui#3875 ·
-
难度 1/5 1 小时以内 新手友好度 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复