YAML frontmatter rendered improperly #2558

New Issue

GiteaMirror · 2025-11-02T04:40:24-06:00

GiteaMirror commented

2025-11-02 04:40:24 -06:00

Originally created by @mcnesium on GitHub (Nov 22, 2018).

Exemplary, in a Jekyll project, markdown files have a YAML front matter like this default one in index.md:

---
# Feel free to add content and custom Front Matter to this file.
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults

layout: default
---

Gitea tries to render it as if it was regular Markdown:

Instead, it should detect it being the YAML frontmatter and render it properly, e.g. like this (screenshot created by adding four spaces in front of each line in the front matter):

Gitea Version: 4c1f1f9

Originally created by @mcnesium on GitHub (Nov 22, 2018). Exemplary, in a Jekyll project, markdown files have a YAML front matter like this default one in `index.md`: ```markdown --- # Feel free to add content and custom Front Matter to this file. # To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults layout: default --- ``` Gitea tries to render it as if it was regular Markdown: ![screenshot from 2018-11-22 10-28-41](https://user-images.githubusercontent.com/476060/48894061-12796d00-ee42-11e8-8473-e560b6d8e576.png) Instead, it should detect it being the YAML frontmatter and render it properly, e.g. like this (screenshot created by adding four spaces in front of each line in the front matter): ![screenshot from 2018-11-22 10-30-03](https://user-images.githubusercontent.com/476060/48894032-02618d80-ee42-11e8-8a5b-ddb8e29c7f86.png) - Gitea Version: 4c1f1f9

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 04:40:24 -06:00

GiteaMirror closed this issue

2025-11-02 04:40:24 -06:00

GiteaMirror commented

2025-11-02 04:40:25 -06:00

@stale[bot] commented on GitHub (Jan 21, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 21, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:40:25 -06:00

@mcnesium commented on GitHub (Jan 22, 2019):

refresh/unstale

@mcnesium commented on GitHub (Jan 22, 2019): refresh/unstale

GiteaMirror commented

2025-11-02 04:40:26 -06:00

@ghost commented on GitHub (Sep 18, 2019):

There is an open pull request for gogs: https://github.com/gogs/gogs/pull/4643

@ghost commented on GitHub (Sep 18, 2019): There is an open pull request for gogs: https://github.com/gogs/gogs/pull/4643

GiteaMirror commented

2025-11-02 04:40:26 -06:00

@dakira commented on GitHub (Dec 5, 2019):

I have the same problem. Would be nice if the front matter just weren't rendered at all. Edit: I guess this should be implemented on the side of the markdown parser. Which parser is in use by Gitea?

@dakira commented on GitHub (Dec 5, 2019): I have the same problem. Would be nice if the front matter just weren't rendered at all. Edit: I guess this should be implemented on the side of the markdown parser. Which parser is in use by Gitea?

GiteaMirror commented

2025-11-02 04:40:26 -06:00

@davidsvantesson commented on GitHub (Feb 21, 2020):

@zeripath Do you think the change to goldmark makes a difference for this issue, does it have any specific support for it?

@davidsvantesson commented on GitHub (Feb 21, 2020): @zeripath Do you think the change to goldmark makes a difference for this issue, does it have any specific support for it?

GiteaMirror commented

2025-11-02 04:40:27 -06:00

@dakira commented on GitHub (Feb 24, 2020):

@davidsvantesson I haven't checked how it looks now, but Goldmark definitely has support for yaml frontmatter. It is used as the default renderer for Hugo which does also have yaml frontmatter.

@dakira commented on GitHub (Feb 24, 2020): @davidsvantesson I haven't checked how it looks now, but Goldmark definitely has support for yaml frontmatter. It is used as the default renderer for Hugo which does also have yaml frontmatter.

GiteaMirror commented

2025-11-02 04:40:27 -06:00

@zeripath commented on GitHub (Mar 28, 2020):

@davidsvantesson @dakira we would need to use the https://github.com/yuin/goldmark-meta extension.

I guess it would probably be quite easy to do. The issue is deciding whether to always enable it or not.

I mean yaml front matter is a particular extension to commonmark - it may not be expected.

@zeripath commented on GitHub (Mar 28, 2020): @davidsvantesson @dakira we would need to use the https://github.com/yuin/goldmark-meta extension. I guess it would probably be quite easy to do. The issue is deciding whether to always enable it or not. I mean yaml front matter is a particular extension to commonmark - it may not be expected.

GiteaMirror referenced this issue

2025-11-02 12:11:18 -06:00

[PR #2558] [MERGED] Remove go version check for make fmt #16466

GiteaMirror referenced this issue

2025-11-02 12:11:22 -06:00

[PR #2561] [MERGED] Backport: Remove go version check for make fmt (#2558) #16469

Sign in to join this conversation.