[Website] Parse markdown headings with id for use with anchors

未關閉
#8,012 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
55/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
markdown
領域
frontend

研究方向

The request concerns Markdown project descriptions on Modrinth.com, but names no implementation files or tests. Start by locating where project descriptions are parsed and rendered, then check how heading anchors and user supplied HTML IDs are handled. Done means Markdown headings produce usable anchors, links to them scroll to the heading, and existing IDs remain safe.

由索引模型根據 Issue 內容生成。

描述

Please confirm the following.
What parts of Modrinth is your feature request related too?

Modrinth.com website

Is your suggested feature related to a problem? Please describe.

I would like to use anchors in my markdown project description.

## Features

[Go to features](#features)

This is how it works on GitHub

Describe the solution you'd like

No response

Describe alternatives you've considered

Today this is already possible by doing something like

<h2 id="features">Features</h2>

[Go to features](#features)
Additional context

GitHub's system works by turning

# Heading

into

<element id="user-content-heading"></element>

and scrolling there with javascript from a https://url#heading in the url


If I see correctly you could also try to break the modrinth site by taking over existing id's like __NUXT_DATA__
But maybe that is a non-issue because we expect users to take care when they use html id.

主要語言
Rust
星號
2.5k
分支
663
平均合併
2 天 11 小時
30 天內合併 PR
122

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

modrinth/code 的其他 Issue

查看 modrinth/code 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。