Possible improvements to YAML frontmatter handling? #5940

Closed
opened 2025-11-02 06:40:52 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @TrollDecker on GitHub (Sep 3, 2020).

  • Gitea version (or commit ref): 1.12.3

Description

👋 🙂

Thank you for the frontmatter formatting thingy for Markdown files. Really helps to tidy things up.
Only thing is, I think there's a bit of room for improvement?

For a start, I'm not keen on having each field be a column, because it squishes everything up when it reaches page width and just makes things messy, like in the screenshot below. Would it not make more sense to have each field be a row instead? If need be, possibly collapsible ones?

And in addition, I feel like YAML collections should be treated more like lists? in the below screenshot, they just render as something akin to an array without any comma separation, making it near impossible to tell single- and multi-word items apart. Less than ideal.

Screenshots

Screenshot_2020-09-03 BookData(1)

Originally created by @TrollDecker on GitHub (Sep 3, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.12.3 ## Description :wave: :slightly_smiling_face: Thank you for the frontmatter formatting thingy for Markdown files. Really helps to tidy things up. Only thing is, I think there's a bit of room for improvement? For a start, I'm not keen on having each field be a column, because it squishes everything up when it reaches page width and just makes things messy, like in the screenshot below. Would it not make more sense to have each field be a row instead? If need be, possibly collapsible ones? And in addition, I feel like YAML collections should be treated more like lists? in the below screenshot, they just render as something akin to an array without any comma separation, making it near impossible to tell single- and multi-word items apart. Less than ideal. ## Screenshots ![Screenshot_2020-09-03 BookData(1)](https://user-images.githubusercontent.com/4513715/92164482-5417b400-ee2d-11ea-8185-af4f8bc4da6a.png)
GiteaMirror added the issue/staletype/upstream labels 2025-11-02 06:40:52 -06:00
Author
Owner

@zeripath commented on GitHub (Sep 3, 2020):

The rendering essentially comes from yuin/goldmark-meta so it might be better to put a feature request there.

However there are a couple of options which gitea provides: setting the gitea value or the gitea meta value to none will hide it, table will show the table and details will hide the table behind a details and summary.

@zeripath commented on GitHub (Sep 3, 2020): The rendering essentially comes from yuin/goldmark-meta so it might be better to put a feature request there. However there are a couple of options which gitea provides: setting the gitea value or the gitea meta value to none will hide it, table will show the table and details will hide the table behind a details and summary.
Author
Owner

@TrollDecker commented on GitHub (Sep 4, 2020):

Ah, fair enough, thanks. 😅

@TrollDecker commented on GitHub (Sep 4, 2020): Ah, fair enough, thanks. :sweat_smile:
Author
Owner

@stale[bot] commented on GitHub (Nov 9, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 9, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@6543 commented on GitHub (Apr 30, 2022):

not possible for now see https://github.com/yuin/goldmark-meta/pull/6

@6543 commented on GitHub (Apr 30, 2022): not possible for now see https://github.com/yuin/goldmark-meta/pull/6
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5940