Our first task is to establish a clear scope of what we see to be mandatory features that must launch in an MVP, and then prioritise other features accordingly. I’ll make this post into a wiki which we can all edit.
Timeline: Meeting with Acquia team on Friday 23rd August at 1630hrs UK time to review scope
MVP must-have features
- Content pages as current site
- Blog (importing the current blog) with Discourse comment integration (& push to Discourse for new blogs if possible, but could be a phase 1)
- Documentation (using current gitbook)
- Login/register link (via Auth0)
- Link to forums
- Link to social channels
- Simple marketplace using Github repos (see staging site)
- Full mobile responsiveness
- Redirects in place for old resources
Phase 1 must-have features
- User profiles synced with forums
- Groups with ability to add members, events, resources etc & group-specific forum (e.g. for mauticamp or working group)
- Forum integration (full embedding within the site with SSO) - there is a port of the Discourse integration to Drupal 8: https://www.drupal.org/node/2880123 - this doesn’t seem to enable the ‘push to Discourse’ feature we have in the Wordpress integration currently, or the comments integration.
- Marketplace with internal review, ratings, comments
Phase 2 must-have features
- Ability to create private groups (e.g. for community working group)
- Multilingual capacity for content and structures (e.g. menus)
Nice to have features
- Content approval workflow with access control and multilingual support
Notes / Resources
- Open Social has been trialled by the community - this is a distribution of Drupal containing a set of modules which are considered helpful for communities. We can figure out which features we specifically need and cherry pick the modules to incorporate this into the brief above.
- Staging.mautic.org as a lot of work already done which is on the theme branch of https://github.com/mautic/website - it would be good if we can use this work in the MVP/theme development?