discourse/app/assets/stylesheets/desktop.scss

@import "common";

@import "desktop/*";

// Import all component-specific files
@import "desktop/components/*";

/* These files doesn't actually exist, they are injected by Stylesheet::Compiler. */

@import "category_backgrounds";
Allow importing Discourse styles in custom stylesheets to modify vars. 2014-03-08 07:25:03 -06:00			`@import "common";`
Theming: a UI to choose some base colors that are applied to all the site css. CSS compiled outside of asset pipeline. 2014-05-02 16:46:03 -05:00
glob @import desktop and mobile scss 2020-05-20 17:05:27 -05:00			`@import "desktop/*";`
Improved Plugins SCSS management - Moves the import of plugins for both mobile and desktop from common after discourse loading, allowing plugins to overwrite - Make desktop-option behave like the mobile-option: SCSS/CSS marked with that option will only be loaded for desktop from now on and ignored in mobile - Add variables-keyword, allowing plugins to ship and overwrite variables before they get imported by discourse (great for theming) 2014-04-25 03:26:37 -05:00
Extracted/DRYed user-stream-item component CSS from user.css into own files - Renamed 'stream-item' component to 'user-stream-item' - Replaced generic 'item' class with clearer 'user-stream-item' class - Retained 'item' class for backward compatibility, marked as 'DEPRECATED' - Extracted CSS pertaining 'user-stream-item' component to component CSS files - Removed unnecessary duplication from 'user-stream-item' CSS - Removed unnecessary nesting from 'user-stream-item' CSS 2017-08-24 20:04:19 -05:00			`// Import all component-specific files`
			`@import "desktop/components/*";`

FEATURE: Native theme support 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 2017-04-12 09:52:52 -05:00			`/* These files doesn't actually exist, they are injected by Stylesheet::Compiler. */`
Improved Plugins SCSS management - Moves the import of plugins for both mobile and desktop from common after discourse loading, allowing plugins to overwrite - Make desktop-option behave like the mobile-option: SCSS/CSS marked with that option will only be loaded for desktop from now on and ignored in mobile - Add variables-keyword, allowing plugins to ship and overwrite variables before they get imported by discourse (great for theming) 2014-04-25 03:26:37 -05:00
FEATURE: Uploaded images to categories are shown when browsing 2014-06-27 16:06:59 -05:00			`@import "category_backgrounds";`