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

Fix top-level headers on docs pages

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
65/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
html
领域
documentation

调研方向

The payload names no files, only four live pages: quickstart (correct), filemanager, settings and develop-dotnet-plugins (incorrect). Start by comparing how the quickstart page's <h1> title is written in its Markdown source with the other three, then find where the site builds the sidebar and page header. Done when every page has one top-level <h1> at the top, left out of the sidebar, with no prose before it.

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

描述

Lots of docs pages are doing the top-level header wrong.

This page does it correctly with an <h1>: https://cspotcode.com/Flow-Launcher-docs/#/quickstart
This page does it incorrectly with an <h2>: https://cspotcode.com/Flow-Launcher-docs/#/filemanager?id=custom-file-manager
This page does it incorrectly with an <h3>: https://cspotcode.com/Flow-Launcher-docs/#/settings
This page does it incorrectly with prose preceding the first header, which renders adjacent to "Edit this page": https://cspotcode.com/Flow-Launcher-docs/#/develop-dotnet-plugins

Note: these are links to the latest revision of our forthcoming docs updates, but the same issues exist on the main website

Note how the <h1> title behaves correctly:

  • Omitted from the sidebar, so we don't see duplicate headings
  • Appears at the top of the rendered page

The others violate these bullet points.

主要语言
Svelte
星标
23
派生
23
平均合并
7 天 6 小时
30 天内合并 PR
5

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

Flow-Launcher/docs 的其他 Issue

查看 Flow-Launcher/docs 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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