Mozilla Foundation currently uses the Calypso Content Management System (CMS) to provide staff and community with easy-to-use, reusable templates appropriate for many use cases. The CMS allows you to create, update, and share your content without needing coding or design skills.
The CMS is ideal for the following situations:
- You need to publish your content quickly. Any registered user can quickly create and publish content without requiring dev or design resources.
- Your content requires regular updates from staff. You can give edit access to multiple staff and contributors, and have a system for tracking their contributions.
- Add something about branding. ie. we may not want highly branded sites for projects/initiatives that are still being tested.
- Your content doesn’t fit into one of our pre-defined layouts. The CMS layouts are designed and tested against existing use cases, and we encourage folks to think creatively about how each existing layout could support content. Sometimes there will be instances where we need something bespoke. If this is the case…[insert process for requesting new layouts here, maybe something simple like, “Talk to the Design Director and a PM”)]
- Your content requires uniquely designed styles (e.g. colors, fonts). Each template allows for some design flexibility to allow custom illustrations, photographs and other graphics, which helps us maintain a unified and consistent brand palette across Foundation properties, but sometimes we need to break outside the box.
- You need to build a complex site with many pages, such as one of the hub sites (e.g. teach.mozilla.org or mozillascience.org)
- If you require complex interactions, data storage, or authentication, the CMS won’t be a good choice for you.
- If your content requires the user to be logged in. The CMS does not support user authentication.
- Your content requires a localization tool. The CMS does not yet support localization. Of course, you can populate a page with content in any left-to-right language, but we do not yet facilitate the translation of strings or show relationships between translated content.
[provide user documentation for creating a new page and applying a layout]
(see layouts here: mozilla/mofo-cms-experiment#23)
 |
 |
 |
|---|---|---|
| Step-by-step with side nav | Two-column, embedded video stream and etherpad | Header image without CTA and alternating blocks |
| Create guides, lesson plans, and other informational documents. The side nav lets visitors progress through step-by-step content. | This layout can be used to create landing pages for recurring live-streamed events, such as community calls. | This layout can be used as a landing page for an event, program, or campaign. You can choose whether your feature image has a CTA, or if you have several CTAs aligned in a row. |
| View an example here | View an example here |
 |
 |
|---|---|
| Header image with CTA and CTAs in a row | List |
| Use this layout to curate a set of links you wish to share with your community. | |
| View an example here |
[add detail about, for example, adding more CTAs to a layout]
[provide answer]
Yes, Calypso supports saving and previewing your work before publishing. You can also “unpublish” something even after it’s been published.
No worries. Simply [instructions here]
Calypso’s got you covered. It won’t allow the same document to be edited by two people at the same time.
[insert details about how this works. e.g. granular privs? on a per article basis? can we have an approval flow where edits need to be approved before publishing?]
Yes. [insert info about the functionality, including how to set an expiry date and what will happen on that date - e.g. will the user be notified?]