Author: @brianfive This is a draft.

Summary

Recommendation is to use a system where we can outsource authoring and review, but then Academy team would own the publishing and display. This would give Academy the flexibility of owning our UI and building Web3 features directly.

There's an array of "headless CMS" system that would be adopted, all with pros and cons.

Allogy's Capillary system could be a possibility with additional features to make it more headless, like a public API.

Below are business requirements for the system, as well as walk through of three scenarios.

Requirements

• Handle onboarding 1 authoring partner per month (3 per season)
• Content publishing process should include:
  • web-based authoring of structured content and media management
  • Media should include formatted text, code blocks, images
  • ability to review content, and optionally give feedback within the tool
  • web-based publishing with ability to create drafts, optionally with version history
  • a process to manage permissions on who can edit content
• Ability to build and integrate Web3 features (front-end and back-end)
  • An example would be Proof of Competency which could be developed independently or in partnership with other companies/platforms.
• Data needs to be portable if decision to move in the future
• What about LMS features?
• Visibility into content utilization

Open Questions

• Is localization a requirement?
• Should content include video? (I think the question should be “what type of content should we have, and more importantly why?) - piablo
• How do we start onboarding sponsored content quickly?

Scenarios

There are three scenarios highlighted:

• Headless CMS + Academy UI (Recommended)
• Academy Homegrown
• Allogy Capillary Learning Management System

Scenario 1: Headless CMS and Custom UI (Recommended)