This feature introduces the concept of themes. Themes are an evolution
of site customizations.
Themes introduce two very big conceptual changes:
- A theme may include other "child themes", children can include grand
children and so on.
- A theme may specify a color scheme
The change does away with the idea of "enabled" color schemes.
It also adds a bunch of big niceties like
- You can source a theme from a git repo
- History for themes is much improved
- You can only have a single enabled theme. Themes can be selected by
users, if you opt for it.
On a technical level this change comes with a whole bunch of goodies
- All CSS is now compiled using a custom pipeline that uses libsass
see /lib/stylesheet
- There is a single pipeline for css compilation (in the past we used
one for customizations and another one for the rest of the app
- The stylesheet pipeline is now divorced of sprockets, there is no
reliance on sprockets for CSS bundling
- CSS is generated with source maps everywhere (including themes) this
makes debugging much easier
- Our "live reloader" is smarter and avoid a flash of unstyled content
we run a file watcher in "puma" in dev so you no longer need to run
rake autospec to watch for CSS changes
|
||
|---|---|---|
| .. | ||
| admin-dashboard.js.es6 | ||
| admin-user.js.es6 | ||
| api-key.js.es6 | ||
| backup-status.js.es6 | ||
| backup.js.es6 | ||
| color-scheme-color.js.es6 | ||
| color-scheme.js.es6 | ||
| email-log.js.es6 | ||
| email-preview.js.es6 | ||
| email-settings.js.es6 | ||
| email-template.js.es6 | ||
| flagged-post.js.es6 | ||
| incoming-email.js.es6 | ||
| permalink.js.es6 | ||
| report.js.es6 | ||
| screened-email.js.es6 | ||
| screened-ip-address.js.es6 | ||
| screened-url.js.es6 | ||
| site-setting.js.es6 | ||
| site-text.js.es6 | ||
| staff-action-log.js.es6 | ||
| theme.js.es6 | ||
| tl3-requirements.js.es6 | ||
| user-field.js.es6 | ||
| version-check.js.es6 | ||
| web-hook.js.es6 | ||