Attendees:

• Ari Rizzitano (Deactivated)
• Calen Pennington (Deactivated)
• Dave Ormsbee
• John Mark Walker (Deactivated)
• Ned Batchelder (Deactivated)

Tactical Issues: Hawthorn

Q: Some small things are going to change/break, where should we document and by when?

...

(We're punting on this for now, though we'll make tickets for the documentation.)

Longer Term: Making Themes Better

Q: How was the community involved for Comprehensive Theming development?

...

• Can't override underscore templates.
• Slow compilation/test cycle.
• Unclear documentation.
• No stable API – things shift around from release to release.
• Three versions of CSS floating around.
• Large files to override.
• We don't know what we can delete.
• edx.org has no stake in getting theming right, difficult to resource large scale changes – but that might change with rebranding project
  • All new branding stuff should be in a theme.

Ways people want to theme

• Style: We want to get folks using Bootstrap for CSS Theming – better defined, well understood by a large community.
• Structural changes: Continue this, but make no release-to-release promises. Better tooling to flag changes that were made? We should gather requirements here.
• Text changes: ("certificate" example for Stanford)
• Logo

...

• Ned: Ideally, we'd have a technical design to better separate our concerns from theirs and give stability. Not sure what that would look like.
• For text replacement, look at what Studio Front End does.
• Make Comprehensive Theming and Webpack work together?
  • Do we really have to right now?

Next Steps

•  Dave Ormsbee: Write to edXchange/mailing list/Slack about theming efforts.
•  Ari Rizzitano (Deactivated): Bootstrap rollout vision – update existing OEP with plan of action.
•  Dave Ormsbee: Make epic and tickets around theming documentation.

...