Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more fields to the commands #1082

Closed
waldyrious opened this issue Sep 21, 2016 · 8 comments
Closed

Add more fields to the commands #1082

waldyrious opened this issue Sep 21, 2016 · 8 comments
Labels
syntax Issues related to the content and markup of the pages.

Comments

@waldyrious
Copy link
Member

waldyrious commented Sep 21, 2016

e.g. URL (mentioned in #934), see also (tracked in #481), maybe platform (related to #190)?

We will need to decide details in dedicated issues, but overall discussion about a potential new page format (including markdown syntax, see #784 and #958) should happen in a coordinated way, hence this issue.

@waldyrious waldyrious added the syntax Issues related to the content and markup of the pages. label Sep 21, 2016
@waldyrious
Copy link
Member Author

Another field proposal: original manpage (#1248)

@waldyrious
Copy link
Member Author

The first one (URL) is now properly tracked in #2649.

@zlatanvasovic
Copy link
Contributor

Isn't this all already implemented @waldyrious?

@waldyrious
Copy link
Member Author

waldyrious commented May 21, 2020

@zdroid how so? IIUC only URL and see also are supported at the moment. Even then, neither is implemented in a structured way.

Since we're already using markdown, one possibility to make these fields consistent and extensible would be to use the frontmatter metadata format, like this:

---
foo: bar
baz: qux
---

(rest of markdown content)

That would make our pages compatible with other markdown processing tools and in particular with other cheatsheet repositories, as described by @chrisallenlane in chubin/cheat.sheets#101 (comment).

@chrisallenlane
Copy link

+1. Front-matter has worked really well for cheat. I think it would be the most painless approach to make the cheatsheet repositories portable, without imposing meaningful constraints on any of our individual projects.

Just shout if I can somehow be of service.

@sbrl
Copy link
Member

sbrl commented May 27, 2020

Ah, thanks for opening this issue @waldyrious!

Indeed, taking a more structured approach would be great.

Front-matter does sound like a good idea. It bothers me a bit that it's above the main title of the page though - but that's not a big deal.

I'm not sure that it's part of the CommonMark spec though, so it would require a breaking change update to the client specification.

We'd also have to perform an automated update to existing pages, and potentially rename the .zip archive too (which might be a good opportunity to deal with that other issue that was talking about restructuring the .zip file by splitting it into multiple languages, but I can't remember the issue number).

@waldyrious
Copy link
Member Author

Good point. @chrisallenlane do you know if these metadata blocks can be added to the bottom of the markdown file rather than the beginning? It would be great if we could keep our format cat/less-friendly.

@Managor
Copy link
Collaborator

Managor commented Oct 8, 2024

I'm not seeing any unresolved proposals in this issue. If I missed any, please reopen the issue.

@Managor Managor closed this as completed Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
syntax Issues related to the content and markup of the pages.
Projects
None yet
Development

No branches or pull requests

5 participants