Rust-GPU / Rust-GPU/rust-gpu.github.io
Consider moving the website into main rust-gpu repo
未關閉
還沒有人認領這個 Issue。
- 主要語言
- MDX
- 星號
- 16
- 分支
- 8
- PR 合併指標
- 30 天內沒有已合併 PR
描述
I just threw it in here as that was the quickest way to get the webpage up with github pages.
Docs/website in the main repo:
Pros:
- Docs stay close to the code, so it’s easier to keep them updated alongside changes.
- Contributors only need to work in one place, so adding or updating docs is straightforward.
- No need to manage multiple repos—everything lives together.
Cons: - The repo gets bigger, which can slow down cloning and pull requests for everyone.
- Mixing code and doc issues in one place can get messy, making it harder to focus on core development.
Using a separate repo for docs/website:
Pros:
- Keeps the main repo cleaner and code-focused, so it’s easier to navigate.
- Doc updates are simpler to track and review on their own, without touching the code.
- Main repo stays leaner and faster to work with.
Cons: - It’s tougher to keep docs in sync with code changes, as they’re in different places.
- Managing a separate repo adds overhead, like additional issue tracking and reviews.
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
這個 issue 是一項儲存庫組織方案,而不是一項已定義的實作任務。請檢視目前的網站儲存庫和主要的 rust-gpu 儲存庫,然後決定網站和文件應該放在哪裡。完成的標準是得出並記錄一項明確的決定,包括遷移範圍。
由索引模型根據 Issue 內容生成。
評估
- 領域
- documentation
- Issue 類型
- 重構
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100