New opus feed #41

Open
opened 2024-05-31 16:18:44 +00:00 by ken_fallon · 3 comments
Owner

We already produce opus files, so we should have a opus feed.

This should have a ideal name that we never need to change again ;-)

If we follow the convention of ??????(english grammer word here)???? eg 'hosts, series, eps. Then feeds would be logical.

Followed by specific "slug" for the item itself.

Should feeds be in ${WEB_ROOT}/feeds/opus.rss

We already produce opus files, so we should have a opus feed. This should have a ideal name that we never need to change again ;-) If we follow the convention of ??????(english grammer word here)???? eg 'hosts, series, eps. Then feeds would be logical. Followed by specific "[slug](https://en.wikipedia.org/wiki/Clean_URL#Slug)" for the item itself. Should feeds be in `${WEB_ROOT}/feeds/opus.rss`
Owner

Is this a hub issue, or is it an issue for the static site, or the hub now but the static site later?

I can add an opus feed to the static site if required.

At the moment all of the static feeds are under public_html, but, as you indicate, having them in a more meaningful hierarchy would be preferable - such as public_html/feeds/. Should this change (which would affect all feeds) be a new issue rather than part of this one?

Is this a hub issue, or is it an issue for the static site, or the hub now but the static site later? I can add an opus feed to the static site if required. At the moment all of the static feeds are under `public_html`, but, as you indicate, having them in a more meaningful hierarchy would be preferable - such as `public_html/feeds/`. Should this change (which would affect all feeds) be a new issue rather than part of this one?
Author
Owner

It would probably be easier to implement this as a php addition first.

It would probably be easier to implement this as a php addition first.
Author
Owner

Working on getting all the files transcoded

Working on getting all the files transcoded
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: HPR/hpr_hub#41
No description provided.