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