github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-12-02 14:45:02 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
d1924c7328
discourse/app/views/common/_discourse_stylesheet.html.erb

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

32 lines
994 B
Plaintext
Raw Normal View History

FEATURE: Add stylesheets to bootstrap.json endpoint This allows API consumers (such as Ember CLI) to dynamically get a list of styles to embed.
2020-09-05 02:09:55 +08:00
<%= discourse_color_scheme_stylesheets %>
FEATURE: automatic dark mode (#10341) A first step to adding automatic dark mode color scheme switching. Adds a new SCSS file at `color_definitions.scss` that serves to output all SCSS color variables as CSS custom properties. And replaces all SCSS color variables with the new CSS custom properties throughout the stylesheets. This is an alpha feature at this point, can only be enabled via console using the `default_dark_mode_color_scheme_id` site setting.
2020-08-04 10:57:10 +08:00
FEATURE: support user local switching to RTL correctly FEATURE: support RTL in multisite
2015-05-20 13:56:54 +08:00
<%- if rtl? %>
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 22:52:52 +08:00
<%= discourse_stylesheet_link_tag(mobile_view? ? :mobile_rtl : :desktop_rtl) %>
FEATURE: support user local switching to RTL correctly FEATURE: support RTL in multisite
2015-05-20 13:56:54 +08:00
<%- else %>
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 22:52:52 +08:00
<%= discourse_stylesheet_link_tag(mobile_view? ? :mobile : :desktop) %>
FEATURE: support user local switching to RTL correctly FEATURE: support RTL in multisite
2015-05-20 13:56:54 +08:00
<%- end %>
move stylesheet
2013-02-11 19:41:23 +08:00
:s/moderator?/staff/g ... our naming was kind of crazy, renamed moderator? to staff
2013-05-02 15:22:27 +08:00
<%- if staff? %>
FEATURE: Serve RTL versions of admin and plugins CSS bundles for RTL locales (#21876) Prior to this commit, we didn't have RTL versions of our admin and plugins CSS bundles and we always served LTR versions of those bundles even when users used an RTL locale, causing admin and plugins UI elements to never look as good as when an LTR locale was used. Example of UI issues prior to this commit were: missing margins, borders on the wrong side and buttons too close to each other etc. This commit creates an RTL version for the admin CSS bundle as well as RTL bundles for all the installed plugins and serves those RTL bundles to users/sites who use RTL locales.
2023-06-01 10:27:11 +08:00
<%- if rtl? %>
<%= discourse_stylesheet_link_tag(:admin_rtl) %>
<%- else %>
<%= discourse_stylesheet_link_tag(:admin) %>
<%- end %>
Allow importing Discourse styles in custom stylesheets to modify vars.
2014-03-08 21:25:03 +08:00
<%- end %>
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations."
2013-12-19 03:47:22 +08:00
DEV: Make wizard an ember addon (#17027) Co-authored-by: David Taylor <david@taylorhq.com>
2022-06-17 20:50:21 +08:00
<%- if admin? %>
FEATURE: Serve RTL versions of admin and plugins CSS bundles for RTL locales (#21876) Prior to this commit, we didn't have RTL versions of our admin and plugins CSS bundles and we always served LTR versions of those bundles even when users used an RTL locale, causing admin and plugins UI elements to never look as good as when an LTR locale was used. Example of UI issues prior to this commit were: missing margins, borders on the wrong side and buttons too close to each other etc. This commit creates an RTL version for the admin CSS bundle as well as RTL bundles for all the installed plugins and serves those RTL bundles to users/sites who use RTL locales.
2023-06-01 10:27:11 +08:00
<%- if rtl? %>
<%= discourse_stylesheet_link_tag(:wizard_rtl) %>
<%- else %>
<%= discourse_stylesheet_link_tag(:wizard) %>
<%- end %>
DEV: Make wizard an ember addon (#17027) Co-authored-by: David Taylor <david@taylorhq.com>
2022-06-17 20:50:21 +08:00
<%- end %>
FEATURE: Serve RTL versions of admin and plugins CSS bundles for RTL locales (#21876) Prior to this commit, we didn't have RTL versions of our admin and plugins CSS bundles and we always served LTR versions of those bundles even when users used an RTL locale, causing admin and plugins UI elements to never look as good as when an LTR locale was used. Example of UI issues prior to this commit were: missing margins, borders on the wrong side and buttons too close to each other etc. This commit creates an RTL version for the admin CSS bundle as well as RTL bundles for all the installed plugins and serves those RTL bundles to users/sites who use RTL locales.
2023-06-01 10:27:11 +08:00
<%- Discourse.find_plugin_css_assets(include_official: allow_plugins?, include_unofficial: allow_third_party_plugins?, mobile_view: mobile_view?, desktop_view: !mobile_view?, request: request, rtl: rtl?).each do |file| %>
DEV: Load plugin stylesheets before theme stylesheets (#9240) This is a more logical order, since themes are more lightweight than plugins, and are often used to augment plugin styles
2020-03-20 00:02:12 +08:00
<%= discourse_stylesheet_link_tag(file) %>
<%- end %>
PERF: Eager load Theme associations in Stylesheet Manager. Before this change, calling `StyleSheet::Manager.stylesheet_details` for the first time resulted in multiple queries to the database. This is because the code was modelled in a way where each `Theme` was loaded from the database one at a time. This PR restructures the code such that it allows us to load all the theme records in a single query. It also allows us to eager load the required associations upfront. In order to achieve this, I removed the support of loading multiple themes per request. It was initially added to support user selectable theme components but the feature was never completed and abandoned because it wasn't a feature that we thought was worth building.
2021-06-15 14:57:17 +08:00
<%- if theme_id.present? %>
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 22:52:52 +08:00
<%= discourse_stylesheet_link_tag(mobile_view? ? :mobile_theme : :desktop_theme) %>
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations."
2013-12-19 03:47:22 +08:00
<%- end %>
Reference in New Issue Copy Permalink