docs: add release notes feed #334
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a release notes feed.
It adds a JSON feed at https://ghostty.org/docs/install/release-notes/feed.json and links to it in the release notes overview. It adds a metadata link to the root layout — maybe this should only be in the release notes overview page?
Currently, it reimplements a simple Markdown to HTML parser using
unified, since it seems the existing parser inloadDocsPageFromRelativeFilePathdoesn't offer the raw HTML string. It doesn't yet render the front-matter like title and description or the footnotes header. The order of items implicitly relies on the filesystem ordering of the MDX documents. It parses the date string from the description which could be brittle — maybe a separate date property could be added to the front matter?Fixes #296.