Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Update the example theme to demonstrate all the use cases

    • This example theme should work for pattern library pages as well as for legacy pages
    • The process of implementing some of these (e.g. changing the font family) will expose the issues
  • Make extensive use of variables in Sass, rather than hard-coding colors, fonts etc into every file

    • This means that the variable can be overridden once, rather than having to override every file. 

    • These variables would themselves be documented so that their purpose is clear for theme authors

  • Update the pattern library documentation to include an example theme
  • Address any issues with theming the pattern library
  • Convert major pre-existing pages to the pattern library

  • Use the pattern library for all new front end features

  • Determine an approach for overriding JavaScript templates

    • A long term solution is to use HTTP/2 and then stop bundling JavaScript files

    • Maybe there could be a way to build theme versions of each JavaScript bundle (or at least those that have overridden templates)
  • Make an OEP that describes how to create themable front end interfaces
  • The default theme should be the only theme within edx-platform.  EdX should dogfood theming by applying edx.org's themes through the same mechanisms as the rest of the community.