Evaluate CMS options

[cnk]

Dependency

On hold per ES Lint #169 and Theming Issue #229

Overview

We have a number of content pages. It would be convenient if the project or product manager could update those pages using a content management system rather than having to commit code.

We are already using Django for our backend, so a Django-based CMS is one option. @cnk is experimenting with Wagtail-Pipit - which combines a Wagtail CMS API with a ReactJS front end.

Options for a more JavaScript-centric CMS include:

• KeystoneJS
• React-admin
• Strapi

Pages where we would use the CMS

• MVP of the CMS
  • Home Page
    • trending topics
    • manually curated organization logos
  • About
    • Update the video
  • FAQ
    • Add, edit and approve questions and answers
  • "Add organization to database" modal
• Post MVP of the CMS
  • FAQ
    • Featured FAQ

[ExperimentsInHonesty]

@cnk to talk to john darragh and tyler thome

[cnk]

1. Progress: Built initial project and started to play with it. No progress since Sunday demo
2. Blocks: Need to talk to people with more React architecture experience
3. Availabilty: a little
4. ETA: long

[Olivia-Chiong]

Progress: Done some tutorials Blocks: Needs some discussion with the team Availability: some time ETA: a week

[cnk]

1. Progress: Built initial combined repository with 4 docker containers. Next steps build storybook components.
2. Blocks: None
3. Availabilty: evenings
4. ETA: February 1

[mariastudnicka]

On hold per ES Lint #169 and Theming Issue #229