---
# System prepended metadata

title: Fedora Websites Revamp

---

# Fedora Websites Revamp
_Active Meeting Space_

## Context

## Attendees

## Meeting Recording
https://peertube.linuxrocks.online/w/vYFMSBBf2Jq6f2hoSLATYK

## Agenda
- [Project Board](https://gitlab.com/groups/fedora/websites-apps/fedora-websites/-/boards/4623394)
- [Merge Requests](https://gitlab.com/groups/fedora/websites-apps/fedora-websites/-/merge_requests)
- [Follow up with action items from last week](https://gitlab.com/groups/fedora/websites-apps/fedora-websites/-/wikis/meeting-logs/revamp/2022-09-21)

### Sprint Structure

Can we formalize our sprint structure? Should we try to establish 2-week sprints, and use the milestone feature in GitLab so we can assign items to milestones. Looking to improve code review process, and help part-time contributors keep up-to-date. 

### Enabling part-time contributors

It can be hard to keep up with the chat discussion - it's great we have so much activity, but it can be daunting to folks who are always playing catch up. Can we use issues to track discussion more, and try to copy/paste chat decisions into relevant tickets etc?

### Cleaning up the board in-progress section

Are we really in-progress on everything there? Can we use in-progress for stuff we're working on this sprint, and stuff we're committed to working on but not yet, maybe use a "next sprint" column or smtg like that?

### Configuring localhost

A quick HOWTO - demo will start around the 8:20 mark in the recording.

1. Clone the fedora-websites-3.0 repo: git@gitlab.com:fedora/websites-apps/fedora-websites/fedora-websites-3.0.git (can grab from the "Clone" blue dropdown button in the right. Can also use the https link - downside of using https is that when you push you have to provide your username/password)
1. Once pulled down, open up preferred code editor (vscode, vscodium, etc) [can do without a code editor but more convenient with one] Doesn't require any vscode extensions installed if you are using it.
1. You will node installed on your system. (Fedora should have node by default.) Run `node -v` to see if it's installed, if not, you can run `sudo dnf install nodejs` to get it installed.
1. In a terminal, go to the root directory of the checkout(fedora-websites-3.0) and run `npm i` (or `npm install`, same command) to install all the needed node modules into the project directory
1. The `package.json` file in the directory has the list of packages that will be installed
1. To run the code, now type `npm run dev` - this will spin up a 

### CMS Testing

Ashlyn to give overview on what's done, why, and next steps (e.g. idea for scripting split/merge of the template yaml) 

Very minimal, and still more work to be done. The config is switched to have everything broken up into these categories:

- Workstation Pages
- IoT Pages
- Server Pages
- Flock
- Start

Ashlyn has added tool tips to the fields. This also doesn't include the editorial workflow so it's not auto-saving, and there's no difference between save and publish right now. Right now, specifically trying to figure out this aspect of the configuration: the fieldset. Then the second phase will be to getting it live with the editorial workflow that allows save vs publish, with editor roles that can create content and admin roles that can push content live.

Part of the reason this is so simplified is because of how long the config.yml file for each section's template gets. It's 168 lines for the Flock page template.  To make it truly static, we'd have to have one template per page. 

Why not have one template and handle variations per page?
- Concern is that as page designs shift over time, having just one template is going to be hard to work with.
- Very much a future problem we're looking to avoid. 
- Having the templates split up could help isolate different teams from impacting other teams' pages.

One idea we talked about yesterday, make a folder for yml files for each individual page template section, and have a script that just concatenates them together for the netlify-cms config.yml. Downside is that it removes the ability to add a new page... but we can just create a new yml file that will get concatened into the config.yml file in CI. 

Niko more concerned about content ymls being split for translation purposes, not as concerned about the template config yml being super long.

Ask Hari & Greg is the new vesrion of the CMS easier to use? Hari thinks it looks better, just needs to try it. But from the start looks better already (in the new simplified state.)

Ashlyn interested in leveraging the markdown/rich content aspect of the content textbox for managing the more complex content.

netlify-cms only supports yaml for the config (no JSON support afawk)

Plan B if netlify-cms doesn't work, we could look into headless wordpress with the Fedora wordpress contract. But seems like netlify-cms would work. Downside of wordpress headless is that you're storing stuff in the wordpress DB. 

Next steps - 
- [ ] Ashlyn to work on getting this to work on localhost workflow
- [ ] Split the template yamls
- [ ] We test content entry for one of the pages, try to minimize custom yaml and make use of the rich markup / markdown field and see what's possible. (cards and list items to look at but basic text areas should work fine)

Issues: https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/issues/51 , https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/issues/57

Development focused stage: testing CMS in dev
Content editor focused stage: CMS hosted for editors

Try out the CMS locally in your dev env and provide feedback in the ticket here:
https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/issues/57

### Documentation

### Overview of progress made since last week
 
### Open Floor

## Action Items