CMS MVP

[meg-gutshall]

Goal

The MVP goal is to allow selected individuals, who aren't programmers, to edit the content on certain pages of the Ruby for Good website.

Motivation

Adding a CMS for content management allows non-programmers to contribute to the website much more easily as creating a GitHub account and editing markdown is a gigantic blocker for someone who doesn't regularly work with code.

Plan of Execution

1. Decide on which CMS to implement. Grav CMS was originally targeted as it is free and open-source, but this is not yet our final decision.
2. Create an admin portal using the chosen CMS.
3. Build account creation and login workflows.
4. Create two user roles: super_admin and content_manager.
   a. The super_admin will have unrestrained access to all features in the admin portal.
   b. The content_manager will only have access to specific sections, which they have permission to edit.
5. Test thoroughly!!

If we have to get more granular than the steps listed above, we will, but let's focus on finishing the MVP first and implementing additional features later.

Possible Blockers

• Finding a safe way to store user info
  • We'll need to be sure that the PII is stored securely. I don't have any ideas for this at the moment besides using OAuth to handle account creation and login.
• Adding a CMS admin panel to a GitHub Pages site
  • Can GitHub Pages support this?
  • We may need to write a custom GitHub Action to get the Jekyll site to build correctly after adding the CMS.

---

Let me know if I missed anything in the outline above. I welcome continued discussion on this post so we can figure out what the best path forward should be!

[sagarp2901]

Hi Meg,

I’d be very happy to discuss this further and contribute to the efforts. I do understand the problem and have some industry experience of dealing with sensitive information. I’ll review Grav cms and gather some thoughts.

We should discuss the requirements of version controlling files and governance on what content is getting published and ability to roll back to previous versions of content. I’d assume Grav provides this out of the box.

Looking forward to collaborating on this!