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

RSS feed for documentation #8979

Open
emanruse opened this issue Feb 26, 2024 · 6 comments
Open

RSS feed for documentation #8979

emanruse opened this issue Feb 26, 2024 · 6 comments
Assignees
Labels
C: website P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.

Comments

@emanruse
Copy link

The problem you're addressing (if any)

Currently, there is no convenient way for users to get notifications about new documentation articles or updates.

The solution you'd like

Provide an RSS feed(s) on the website, so users can subscribe selectively for:

  • newly published documentation articles
  • updates to existing articles

The value to a user, and who that user might be

Be informed about documentation updates.

@emanruse emanruse added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. labels Feb 26, 2024
@andrewdavidwong
Copy link
Member

andrewdavidwong commented Feb 26, 2024

I think you can either:

  1. Use this: https://github.com/QubesOS/qubes-doc/commits/main.atom

or

  1. "Watch" https://github.com/QubesOS/qubes-doc, then get your own GitHub notifications as an RSS feed.

@emanruse
Copy link
Author

emanruse commented Feb 28, 2024 via email

@andrewdavidwong
Copy link
Member

What about the first option? I think that works without any kind of registration.

@emanruse
Copy link
Author

emanruse commented Feb 28, 2024 via email

@unman
Copy link
Member

unman commented Mar 2, 2024 via email

@andrewdavidwong
Copy link
Member

On Wed, Feb 28, 2024 at 01:38:47PM -0800, andrewdavidwong wrote: Assigned #8979 to @unman.
I was afraid that was coming my way.

No need to fear. This just means it's up to you, as the documentation and website maintainer, to decide how to triage the issue. If you don't believe any action should be taken, you are free to close the issue without taking any. If you believe it should be labeled "help wanted," you are free to unassign yourself.

My assigning it to you isn't a way of saying that you should do anything. Rather, it's a way of saying that you should decide what should be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: website P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

No branches or pull requests

3 participants