MVP release checklist

[hannahkane]

This is what we need to do before we can release an MVP version of the CMS to users. The MVP will allow users to create and publish a page with a single partial to the Teach site.

@flukeout @mmmavis @alicoding @vazquez @gvn @cadecairos @simonwex @xmatthewx

Please add to/edit this list:

• [x] refactor three onesie partials
• [x] Add three "simple" partials to pulldown menu of options
• [x] Add preview functionality
• [ ] resolve hosting issues

[hannahkane]

@mmmavis @Pomax @simonwex - I want to file a follow-up ticket about "migrating" current Teach site content to the CMS. What repo should I file that in - Teach?

[mmmavis]

@hannahkane is there a list of existing Teach pages that we are thinking to migrate to the CMS?

[hannahkane]

@mmmavis - no, not yet. I'd like to migrate both the Curriculum Workshop and Community Call landing pages, because I know there will be frequent updates to those. Otherwise, does it make sense to only migrate pages as needed (i.e. as requests for edits come in)?

[mmmavis]

@hannahkane +1 on migrate pages as needed.

I'd say file a ticket on Teach repo. :smiley:

[hannahkane]

Thanks, @mmmavis.

Re: the first comment in this ticket. Can we check off any of these items? Based on today's demo, it seems like we can check off items 2 and 3, right @alicoding and @mmmavis.

What about the first item, @gvn and @vazquez?

[gvn]

Yep, Ricardo and I finished refactoring the partials today.

[hannahkane]

Checking off items 2 and 3 from the checklist because I believe @mmmavis and @alicoding completed them, respectively.