Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Strategic Refactor: Establish Persona-Based Documentation Paths

未关闭
#250 11 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

@IQRAZAM 已经在做这个了。

开始于 2026年2月21日。

  • #260 来自 @gyanranjanpanda —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
冷清
技术栈
markdown
领域
documentation

调研方向

首先审查 PR #249 以及 issue 中引用的 Slack 投票结果。审核现有的 .rst 和 .md 文档,并根据 Legal/Compliance、Security/SCA 或 Dev/Integrators persona 为每个文件添加标签。完成标准是提供已标记的内容映射、拟议的 Sphinx 站点地图,以及至少两个角色的用户旅程文档。

由索引模型根据 Issue 内容生成。

描述

documentation

Problem Statement: Currently, the AboutCode documentation is structured primarily around tool functionality. However, our ongoing research into User Roles (see PR #249) indicates that our audience is split between highly technical developers, legal compliance officers, and security researchers. Each of these groups has different "information hunger" and entry points.

Proposal: Conduct a comprehensive audit of the existing documentation to map current content against the newly defined personas:

  • Legal/Compliance: High-level summaries, license policy guides, and reporting features.

  • Security/SCA: Vulnerability database integration and scanning workflows.

  • Dev/Integrators: CLI usage, API documentation, and CI/CD pipeline integration.

  • Goals:

    • Identify Gaps: Determine which roles are currently underserved by the documentation.
    • Navigation Overhaul: Propose a "Choose Your Own Adventure" style landing page for docs.aboutcode.org.
    • Language Consistency: Ensure that non-technical roles aren't hit with jargon in the introductory sections.
  • Acceptance Criteria:

    • A spreadsheet or map of existing .rst/.md files tagged by target persona.
    • A proposed new Site Map for the Sphinx documentation.
    • A "User Journey" document for at least two primary roles (e.g., a first-time Compliance Officer vs. a Senior DevOps Engineer).
  • Additional Context: This issue will directly consume the results of the Slack poll initiated in #249 to ensure the reorganization is data-driven.

主要语言
Batchfile
星标
310
派生
255
平均合并
10 小时 5 分钟
30 天内合并 PR
1

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aboutcode-org/aboutcode 的其他 Issue

查看 aboutcode-org/aboutcode 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。