Archetype definitions about jupiterbroadcasting.com HOT 3 OPEN

Honestly, I think this can be moved to Milestone 2.0. For now we can just direct people to GH if they want to edit something. I don't see very many people trying to author new content either (besides new episodes (which are made via the scraper for now as well)), so I don't think we really have to worry about this for 1.0 (archtypes or a CMS)

from jupiterbroadcasting.com.

If we implement #110, then instead of defining archetype definitions, we could hook the project up to a headless CMS and update/add episodes/hosts/guests that way. If you'd like an example just let me know, I can point you to 2 just off the top of my head. 🙂 (didn't want to mention them if this isn't the appropriate issue)

from jupiterbroadcasting.com.

Alright, since #110 is done now. Do we want to possibly think about doing a CMS instead of archtypes?

I know that this is a bigger convo if we do a CMS (because people have opinions on UIs 🙃 and also depends on how much JB wants to self-host), but it's something we can entertain now that things are in the page format.

I gave some examples of if we were to use NetlifyCMS (something I've used with hugo sites before) in #110 (here is some of that):

Lastly, whenever there is a chance for implementing the CMS. If you're using pages for pulling people, at least with NetlifyCMS, you can reference those pages and their front matter with relative ease via the relation widget.
That widget allows you to propagate information for the user to select from (i.e. hosts or guests when creating a new episode for a show). Here is a picture (using the netlify CMS docs as an example, since they've implemented it) of what it'd look like:

This would also help with contributions and not having to create a local hugo environment, because of 2 things:

• https://www.netlifycms.org/docs/open-authoring/
• https://www.netlifycms.org/docs/custom-widgets/ & widgets in general

The first one allows people to use the CMS w/their GH accounts, and it'll transparently create a PR on the backend. It's almost like GH's editing except it keeps all their content constructed with however we've defined it in the NetlifyCMS config.

Then the second one can be better seen here: #8 (reply in thread)

You can see how it essentially prompts the users to fill in boxes based on the what we've defined in the config and give a preview (not the best looking 😅 ) to the right of what the CMS is expecting to do with it.

from jupiterbroadcasting.com.