Essentially we want Calypso to be able to query mozmaker-templates via a very basic REST API:

For example:

GET /partials

["3-boxes", "guide", "resource-list"]

GET /partial/3-boxes

{
  "cssUrl": "http://mozilla.github.io/mozmaker-templates/demo/templates/3-boxes/style.css",
  "htmlPartial": "<div class="theme theme--charcoal">
  <section class="container">
    <h1 class="header-headline">Mozilla Club Resources</h1>
  </section>

  <section class="container">
    <h2>Important Links</h2>

    <ul class="Boxes">
   ..."
}

http://mozilla.github.io/mozmaker-templates/api/ I can't access any of the api now.

We've started this layout, but during the March 11 heartbeat, we need to finalize. This should include:

• design for specific use case (Curriculum Workshop landing page) (p1)
• generic design (p2)
• design review and necessary revisions

A couple options:

• Don't use images in templates
• Base 64 encode images and add to CSS
• Put images on CDN

Let's make sure people are starting with nice clean HTML!

Add version number to healthcheck.

Let's create a more explicit linkage between the two projects since Foxlight is a dependency we're extending here.

This should also be bundled into the dist folder on gh-pages.

Change it...everywhere.

Guide will become a template that autogenerates the sidenav based on a content block partial.

(Totally open to a different name for this layout)

This should include:

• design for specific use case (Club page—spec to come)
• generic design
• design review and necessary revisions

Right now the partials are hardcoded, so let's split it up into a proper template pulling 3 partials.

We've started this layout, but during the March 11 heartbeat, we need to finalize. This should include:

• design for specific use case (Letters to the Next President campaign) (p1)
• generic design (p2)
• design review and necessary revisions

We should avoid using <button> and use <a> instead as Wordpress API converts <button> into <p>.

/cc @gvn @flukeout @vazquez

This is because the ncp filter isn't working and everything is being copied over.

We need to do some fixups to the SCSS so that we're passing mofo-style.

See here: https://travis-ci.org/mozilla/mozmaker-templates

Or run npm test locally to see the errors...

We just published the Curriculum Workshop page, which we also want to convert into a template type. This page has two unique features...

• An embedded Youtube video player (for a Google hangout On Air call)
• An embedded Etherpad

We'll need to figure out a clever way for letting the content author specify the URLs for both of these (cc @gvn @mmmavis)

These are the styles and this is the markup.

cc @vazquez

Right now we only see the grey themes, so it'd be useful to have a color switcher.

We're moving away from LESS, so we need to use SCSS for our new templates. 👍

(Totally open to a different name for this layout)

This should include:

• design for specific use case (MSL Study Group Handbook)
• generic design
• design review and necessary revisions

Some files are getting cached between builds, which is causing confusion & errors.

SImilar to how mozmaker is set up to include pre-compiled assets in the module.

Intended primarily for consumption by our fork of Calypso.

Switch default branch to master.

We've started this layout, but during the March 11 heartbeat, we need to finalize. This should include:

• design for specific use case (Clubs Guides page) (p1)
• generic design (p2)
• design review and necessary revisions

We've started the List layout, but during the March 11 heartbeat, we need to finalize. This should include:

• design for specific use case (Clubs resources page) (p1)
• generic design (p2)
• design review and necessary revisions

We need to remove any custom CSS from the partials and leverage Onesie (and Bootstrap) as much as possible. It overcomplicates the CMS if we have to pull custom CSS for each partial. TinyMCE will have Onesie and Bootstrap available though.

This doesn't mean that we have to necessarily change the design, but if we do need CSS that isn't defined in Onesie, then it should be promoted to a template that wraps the partial.

CC: @simonwex @mmmavis @flukeout @vazquez