github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-12-17 03:03:42 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
12cf3320c2
discourse/app/assets/javascripts/admin/templates/customize-themes-edit.hbs

79 lines
2.6 KiB
Handlebars
Raw Normal View History

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
<div class="current-style {{if maximized 'maximized'}}">
<div class='wrapper'>
<h2>{{i18n 'admin.customize.theme.edit_css_html'}} {{#link-to 'adminCustomizeThemes.show' model.id replace=true}}{{model.name}}{{/link-to}}</h2>
FEATURE: added error messages for bad theme CSS / JS
2017-04-20 04:46:28 +08:00
{{#if error}}
FEATURE: Theme settings (2) (#5611) Allows theme authors to specify custom theme settings for the theme. Centralizes the theme/site settings into a single construct
2018-03-05 08:04:23 +08:00
<pre class='field-error'>{{error}}</pre>
FEATURE: added error messages for bad theme CSS / JS
2017-04-20 04:46:28 +08:00
{{/if}}
FEATURE: Only show overridden option for theme css also fixes bad styling of mobile glyph
2017-04-20 03:24:00 +08:00
<div class='edit-main-nav'>
<ul class='nav nav-pills target'>
{{#if showCommon}}
FEATURE: Theme settings (2) (#5611) Allows theme authors to specify custom theme settings for the theme. Centralizes the theme/site settings into a single construct
2018-03-05 08:04:23 +08:00
<li>
{{#link-to 'adminCustomizeThemes.edit' model.id 'common' fieldName replace=true}}
{{i18n 'admin.customize.theme.common'}}
{{/link-to}}
</li>
FEATURE: Only show overridden option for theme css also fixes bad styling of mobile glyph
2017-04-20 03:24:00 +08:00
{{/if}}
{{#if showDesktop}}
FEATURE: Theme settings (2) (#5611) Allows theme authors to specify custom theme settings for the theme. Centralizes the theme/site settings into a single construct
2018-03-05 08:04:23 +08:00
<li>
{{#link-to 'adminCustomizeThemes.edit' model.id 'desktop' fieldName replace=true}}
{{i18n 'admin.customize.theme.desktop'}}
{{d-icon 'desktop'}}
{{/link-to}}
</li>
FEATURE: Only show overridden option for theme css also fixes bad styling of mobile glyph
2017-04-20 03:24:00 +08:00
{{/if}}
{{#if showMobile}}
FEATURE: Theme settings (2) (#5611) Allows theme authors to specify custom theme settings for the theme. Centralizes the theme/site settings into a single construct
2018-03-05 08:04:23 +08:00
<li class='mobile'>
{{#link-to 'adminCustomizeThemes.edit' model.id 'mobile' fieldName replace=true}}
{{i18n 'admin.customize.theme.mobile'}}
{{d-icon 'mobile'}}
{{/link-to}}
</li>
{{/if}}
FEATURE: Only show overridden option for theme css also fixes bad styling of mobile glyph
2017-04-20 03:24:00 +08:00
</ul>
<div class='show-overidden'>
<label>
{{input type="checkbox" checked=onlyOverridden}}
FEATURE: Theme settings (2) (#5611) Allows theme authors to specify custom theme settings for the theme. Centralizes the theme/site settings into a single construct
2018-03-05 08:04:23 +08:00
{{i18n 'admin.settings.show_overriden'}}
FEATURE: Only show overridden option for theme css also fixes bad styling of mobile glyph
2017-04-20 03:24:00 +08:00
</label>
</div>
<div class='clearfix'></div>
</div>
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
<div class='admin-controls'>
<ul class='nav nav-pills fields'>
{{#each fields as |field|}}
<li>
{{#link-to 'adminCustomizeThemes.edit' model.id currentTargetName field.name replace=true title=field.title}}
Rename `{{fa-icon}}` to `{{d-icon}}` so it can be more generic
2017-07-27 04:25:09 +08:00
{{#if field.icon}}{{d-icon field.icon}} {{/if}}
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
{{i18n field.key}}
{{/link-to}}
</li>
{{/each}}
<li class='toggle-maximize'>
<a {{action "toggleMaximize"}}>
REFACTOR: Replace some `fa-*` uses with helpers
2017-07-27 04:33:17 +08:00
{{d-icon maximizeIcon}}
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
</a>
</li>
</ul>
</div>
FIX: maximize css editor not working
2017-05-11 03:42:51 +08:00
{{ace-editor content=activeSection editorId=editorId mode=activeSectionMode autofocus="true"}}
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
<div class='admin-footer'>
<div class='status-actions'>
{{#unless model.changed}}
<a class='preview-link' href={{previewUrl}} target='_blank' title="{{i18n 'admin.customize.explain_preview'}}">{{i18n 'admin.customize.preview'}}</a>
{{/unless}}
</div>
<div class='buttons'>
DEV: upgrades from Ember 2.13 to Ember 3.5.1 (#6808) Co-Authored-By: Bianca Nenciu <nbianca@users.noreply.github.com> Co-Authored-By: David Taylor <david@taylorhq.com>
2019-01-10 18:06:01 +08:00
{{#d-button action=(action "save") disabled=saveDisabled class='btn-primary'}}
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
{{saveButtonText}}
{{/d-button}}
</div>
</div>
</div>
</div>
Reference in New Issue Copy Permalink