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 天內回覆