You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since it's not a simple config option, I wanted to open up an issue for discussion with y'all first. Is this something you would be willing to add? If so, here are a few options that come to mind:
We could build out an RSS that pulls from the GitHub API and looks for PRs that affect markdown files in the docs directory and publish an item in the feed describing that change.
We could use the built in feed tool, enable the blog, and add automatic blog posts to each PR (either by making it a requirement of the PR, or maybe some additional GitHub action to generate based on the PR description/changeset).
Maybe extend the Docusaurus feed option to just work with docs as well? It's all Markdown like the blog posts, so it seems like there might be something there.
To be clear, I am volunteering to do the work for any one of these options. But since they're all somewhat bespoke, I wanted to check in with y'all about a preferred approach.
Thanks for your consideration!
The text was updated successfully, but these errors were encountered:
I mentioned this in Slack: I would love to have an RSS feed where I can subscribe to new recipes and recipe changes.
It looks like Docusaurus has support for a blog feed, but not for actual docs.
They have a thread here that says they probably won't build one.
Since it's not a simple config option, I wanted to open up an issue for discussion with y'all first. Is this something you would be willing to add? If so, here are a few options that come to mind:
docs
directory and publish an item in the feed describing that change.To be clear, I am volunteering to do the work for any one of these options. But since they're all somewhat bespoke, I wanted to check in with y'all about a preferred approach.
Thanks for your consideration!
The text was updated successfully, but these errors were encountered: