github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-11-25 09:42:07 +08:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity
f002c58a30
discourse/app/assets/javascripts/admin/addon/templates/customize-themes-show.hbs

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

321 lines
12 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="show-current-style">
FIX: Disallow editing of remote themes (#11189) Allowing the editing of remote themes has been something Discourse has advised against for some time. This commit removes the ability to edit or upload files to remote themes from Admin > Customize to enforce the recommended practice.
2020-11-13 23:57:49 +08:00
{{plugin-outlet name="admin-customize-themes-show-top" args=(hash theme=model)}}
UX: improvements to admin theme UI
2018-08-31 03:23:15 +08:00
<div class="title">
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
{{#if editingName}}
{{text-field value=model.name autofocus="true"}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{d-button action=(action "finishedEditingName") class="btn-primary btn-small submit-edit" icon="check"}}
{{d-button action=(action "cancelEditingName") class="btn-small cancel-edit" icon="times"}}
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
{{else}}
DEV: enforces no-invalid-interactive linting rule (#8907)
2020-02-11 22:55:16 +08:00
<span>{{model.name}}</span>
{{d-button
action=(action "startEditingName")
icon="pencil-alt"
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
class="btn-small"
DEV: enforces no-invalid-interactive linting rule (#8907)
2020-02-11 22:55:16 +08:00
}}
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
{{/if}}
UX: improvements to admin theme UI
2018-08-31 03:23:15 +08:00
</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
FIX: Display errors in single theme pages (#6449) Currently the errors are not well handled. So it breaks the whole UI of admin themes list page.
2018-10-04 05:03:06 +08:00
{{#each model.errors as |error|}}
<div class="alert alert-error">
DEV: Fix and enable the 'require-button-type' lint
2020-04-14 06:22:35 +08:00
<button type="button" class="close" data-dismiss="alert" aria-label={{i18n "modal.dismiss_error"}}>×</button>
FIX: Display errors in single theme pages (#6449) Currently the errors are not well handled. So it breaks the whole UI of admin themes list page.
2018-10-04 05:03:06 +08:00
{{error}}
</div>
{{/each}}
FEATURE: allow disabling theme components (#7812) This allows you to temporarily disable components without having to remove them from a theme. This feature is very handy when doing quick fix engineering.
2019-07-03 16:18:11 +08:00
{{#unless model.supported}}
FEATURE: Support additional metadata in theme about.json (#6944) New `about.json` fields (all optional): - `authors`: An arbitrary string describing the theme authors - `theme_version`: An arbitrary string describing the theme version - `minimum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. - `maximum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. A localized description for a theme can be provided in the language files under the `theme_metadata.description` key The admin UI has been re-arranged to display this new information, and give more prominence to the remote theme options.
2019-01-25 22:19:01 +08:00
<div class="alert alert-error">
{{i18n "admin.customize.theme.required_version.error"}}
{{#if model.remote_theme.minimum_discourse_version}}
{{i18n "admin.customize.theme.required_version.minimum" version=model.remote_theme.minimum_discourse_version}}
{{/if}}
{{#if model.remote_theme.maximum_discourse_version}}
UX: Correct locale key for theme compatibility error
2019-02-28 22:40:33 +08:00
{{i18n "admin.customize.theme.required_version.maximum" version=model.remote_theme.maximum_discourse_version}}
FEATURE: Support additional metadata in theme about.json (#6944) New `about.json` fields (all optional): - `authors`: An arbitrary string describing the theme authors - `theme_version`: An arbitrary string describing the theme version - `minimum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. - `maximum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. A localized description for a theme can be provided in the language files under the `theme_metadata.description` key The admin UI has been re-arranged to display this new information, and give more prominence to the remote theme options.
2019-01-25 22:19:01 +08:00
{{/if}}
</div>
{{/unless}}
FEATURE: allow disabling theme components (#7812) This allows you to temporarily disable components without having to remove them from a theme. This feature is very handy when doing quick fix engineering.
2019-07-03 16:18:11 +08:00
{{#unless model.enabled}}
<div class="alert alert-error">
{{#if model.disabled_by}}
{{i18n "admin.customize.theme.disabled_by"}}
{{#user-link user=model.disabled_by}}
{{avatar model.disabled_by imageSize="tiny"}}
{{model.disabled_by.username}}
{{/user-link}}
{{format-date model.disabled_at leaveAgo="true"}}
{{else}}
{{i18n "admin.customize.theme.disabled"}}
{{/if}}
{{d-button
class="btn-default"
action=(action "enableComponent")
icon="check"
label="admin.customize.theme.enable"}}
</div>
{{/unless}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
<div class="metadata control-unit">
{{#if model.remote_theme}}
theme settings need some bottom margin
2020-09-26 08:34:29 +08:00
{{#if model.remote_theme.remote_url}}
{{#if sourceIsHttp}}
<a class="remote-url" href={{remoteThemeLink}}>{{i18n "admin.customize.theme.source_url"}}{{d-icon "link"}}</a>
{{else}}
UX: Show theme git branch for private repositories (#11166)
2020-11-09 19:33:38 +08:00
<div class="remote-url">
<code>{{model.remote_theme.remote_url}}</code>
{{#if model.remote_theme.branch}}
(<code>{{model.remote_theme.branch}}</code>)
{{/if}}
</div>
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{/if}}
theme settings need some bottom margin
2020-09-26 08:34:29 +08:00
{{/if}}
{{#if model.remote_theme.about_url}}
<a class="url about-url" href={{model.remote_theme.about_url}}>{{i18n "admin.customize.theme.about_theme"}}{{d-icon "link"}}</a>
{{/if}}
{{#if model.remote_theme.license_url}}
<a class="url license-url" href={{model.remote_theme.license_url}}>{{i18n "admin.customize.theme.license"}}{{d-icon "link"}}</a>
{{/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
theme settings need some bottom margin
2020-09-26 08:34:29 +08:00
{{#if model.description}}
<span class="theme-description">{{model.description}}</span>
{{/if}}
FEATURE: Support additional metadata in theme about.json (#6944) New `about.json` fields (all optional): - `authors`: An arbitrary string describing the theme authors - `theme_version`: An arbitrary string describing the theme version - `minimum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. - `maximum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. A localized description for a theme can be provided in the language files under the `theme_metadata.description` key The admin UI has been re-arranged to display this new information, and give more prominence to the remote theme options.
2019-01-25 22:19:01 +08:00
theme settings need some bottom margin
2020-09-26 08:34:29 +08:00
{{#if model.remote_theme.authors}}<span class="authors"><span class="heading">{{i18n "admin.customize.theme.authors"}}</span> {{model.remote_theme.authors}}</span>{{/if}}
{{#if model.remote_theme.theme_version}}<span class="version"><span class="heading">{{i18n "admin.customize.theme.version"}}</span> {{model.remote_theme.theme_version}}</span>{{/if}}
FEATURE: Support additional metadata in theme about.json (#6944) New `about.json` fields (all optional): - `authors`: An arbitrary string describing the theme authors - `theme_version`: An arbitrary string describing the theme version - `minimum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. - `maximum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. A localized description for a theme can be provided in the language files under the `theme_metadata.description` key The admin UI has been re-arranged to display this new information, and give more prominence to the remote theme options.
2019-01-25 22:19:01 +08:00
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
<div class="control-unit">
{{#if model.remote_theme.is_git}}
UX: Add editing guidance for remote themes (#12111)
2021-02-17 23:24:34 +08:00
<div class="alert alert-info">
{{html-safe (i18n "admin.customize.theme.remote_theme_edits" repoURL=remoteThemeLink)}}
</div>
FEATURE: color-palettes component (#6992)
2019-02-08 21:01:14 +08:00
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#if showRemoteError}}
<div class="error-message">
{{d-icon "exclamation-triangle"}} {{i18n "admin.customize.theme.repo_unreachable"}}
</div>
<div class="raw-error">
<code>{{model.remoteError}}</code>
</div>
{{/if}}
FEATURE: color-palettes component (#6992)
2019-02-08 21:01:14 +08:00
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#if model.remote_theme.commits_behind}}
{{d-button action=(action "updateToLatest") icon="download" class="btn-primary" label="admin.customize.theme.update_to_latest"}}
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class
2019-12-04 14:13:41 +08:00
{{else}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{d-button action=(action "checkForThemeUpdates") icon="sync" class="btn-default" label="admin.customize.theme.check_for_updates"}}
{{/if}}
<span class="status-message">
{{#if updatingRemote}}
{{i18n "admin.customize.theme.updating"}}
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class
2019-12-04 14:13:41 +08:00
{{else}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#if model.remote_theme.commits_behind}}
FIX: Gracefully handle force pushes for remote themes (#11325) Force pushing a commit to a theme repository used to break the updater, because the system was not able to count the commits behind the old and new version. This operation failed because a force push deleted the old commits. The user was prompted with a simple "500 server error" message.
2020-11-23 21:29:22 +08:00
{{#if hasOverwrittenHistory}}
{{i18n "admin.customize.theme.has_overwritten_history"}}
{{else}}
{{i18n "admin.customize.theme.commits_behind" count=model.remote_theme.commits_behind}}
{{/if}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#if model.remote_theme.github_diff_link}}
<a href={{model.remote_theme.github_diff_link}}>
{{i18n "admin.customize.theme.compare_commits"}}
</a>
{{/if}}
{{else}}
{{#unless showRemoteError}}
{{i18n "admin.customize.theme.up_to_date"}} {{format-date model.remote_theme.updated_at leaveAgo="true"}}
{{/unless}}
{{/if}}
FEATURE: Support additional metadata in theme about.json (#6944) New `about.json` fields (all optional): - `authors`: An arbitrary string describing the theme authors - `theme_version`: An arbitrary string describing the theme version - `minimum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. - `maximum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. A localized description for a theme can be provided in the language files under the `theme_metadata.description` key The admin UI has been re-arranged to display this new information, and give more prominence to the remote theme options.
2019-01-25 22:19:01 +08:00
{{/if}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
</span>
{{else}}
<span class="status-message">
{{d-icon "info-circle"}} {{i18n "admin.customize.theme.imported_from_archive"}}
</span>
{{/if}}
</div>
{{else}}
theme settings need some bottom margin
2020-09-26 08:34:29 +08:00
<span class="heading">{{i18n "admin.customize.theme.creator"}}</span>
<span>
{{#user-link user=model.user}}
{{format-username model.user.username}}
{{/user-link}}
</span>
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{/if}}
</div>
FEATURE: Add auto update field to themes (#11102) Themes marked for auto update will be automatically updated when Discourse is updated. This is triggered by discourse_docker or docker_manager running Rake task 'themes:update'.
2020-11-16 20:44:09 +08:00
{{#if showCheckboxes}}
UX: display info about extra files and uploader (#9595) Co-authored-by: David Taylor <david@taylorhq.com>
2020-04-30 22:02:38 +08:00
<div class="control-unit">
FEATURE: Add auto update field to themes (#11102) Themes marked for auto update will be automatically updated when Discourse is updated. This is triggered by discourse_docker or docker_manager running Rake task 'themes:update'.
2020-11-16 20:44:09 +08:00
{{#unless model.component}}
FIX: Checkbox value should not leak between themes (#11327) This commit includes a hack to ensure didInsertElement is called only once.
2020-11-24 18:10:28 +08:00
{{inline-edit-checkbox action=(action "applyDefault") labelKey="admin.customize.theme.is_default" checked=model.default modelId=model.id}}
{{inline-edit-checkbox action=(action "applyUserSelectable") labelKey="admin.customize.theme.user_selectable" checked=model.user_selectable modelId=model.id}}
FEATURE: Add auto update field to themes (#11102) Themes marked for auto update will be automatically updated when Discourse is updated. This is triggered by discourse_docker or docker_manager running Rake task 'themes:update'.
2020-11-16 20:44:09 +08:00
{{/unless}}
{{#if model.remote_theme}}
FIX: Checkbox value should not leak between themes (#11327) This commit includes a hack to ensure didInsertElement is called only once.
2020-11-24 18:10:28 +08:00
{{inline-edit-checkbox action=(action "applyAutoUpdateable") labelKey="admin.customize.theme.auto_update" checked=model.auto_update modelId=model.id}}
FEATURE: Add auto update field to themes (#11102) Themes marked for auto update will be automatically updated when Discourse is updated. This is triggered by discourse_docker or docker_manager running Rake task 'themes:update'.
2020-11-16 20:44:09 +08:00
{{/if}}
UX: display info about extra files and uploader (#9595) Co-authored-by: David Taylor <david@taylorhq.com>
2020-04-30 22:02:38 +08:00
</div>
FEATURE: Add auto update field to themes (#11102) Themes marked for auto update will be automatically updated when Discourse is updated. This is triggered by discourse_docker or docker_manager running Rake task 'themes:update'.
2020-11-16 20:44:09 +08:00
{{/if}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
FEATURE: themes and components split * FEATURE: themes and components split * two seperate methods to switch theme type * use strict equality operator
2018-08-24 09:30:00 +08:00
{{#unless model.component}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#d-section class="form-horizontal theme settings control-unit"}}
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class
2019-12-04 14:13:41 +08:00
<div class="row setting">
<div class="setting-label">
{{i18n "admin.customize.theme.color_scheme"}}
</div>
<div class="setting-value">
{{color-palettes
content=colorSchemes
filterable=true
forceEscape=true
value=colorSchemeId
icon="paint-brush"}}
FEATURE: color-palettes component (#6992)
2019-02-08 21:01:14 +08:00
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class
2019-12-04 14:13:41 +08:00
<div class="desc">{{i18n "admin.customize.theme.color_scheme_select"}}</div>
</div>
<div class="setting-controls">
{{#if colorSchemeChanged}}
{{d-button action=(action "changeScheme") class="ok submit-edit" icon="check"}}
{{d-button action=(action "cancelChangeScheme") class="cancel cancel-edit" icon="times"}}
{{/if}}
</div>
UX: improvements to admin theme UI
2018-08-31 03:23:15 +08:00
</div>
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class
2019-12-04 14:13:41 +08:00
{{/d-section}}
FEATURE: themes and components split * FEATURE: themes and components split * two seperate methods to switch theme type * use strict equality operator
2018-08-24 09:30:00 +08:00
{{/unless}}
FEATURE: Support additional metadata in theme about.json (#6944) New `about.json` fields (all optional): - `authors`: An arbitrary string describing the theme authors - `theme_version`: An arbitrary string describing the theme version - `minimum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. - `maximum_discourse_version`: Theme will be auto-disabled for lower versions. Must be a valid version descriptor. A localized description for a theme can be provided in the language files under the `theme_metadata.description` key The admin UI has been re-arranged to display this new information, and give more prominence to the remote theme options.
2019-01-25 22:19:01 +08:00
{{#if parentThemes}}
<div class="control-unit">
<div class="mini-title">{{i18n "admin.customize.theme.component_of"}}</div>
<ul>
{{#each parentThemes as |theme|}}
<li>{{#link-to "adminCustomizeThemes.show" theme replace=true}}{{theme.name}}{{/link-to}}</li>
{{/each}}
</ul>
</div>
{{/if}}
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class
2019-12-04 14:13:41 +08:00
{{#if model.component}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#d-section class="form-horizontal theme settings control-unit"}}
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class
2019-12-04 14:13:41 +08:00
<div class="row setting">
{{theme-setting-relatives-selector setting=relativesSelectorSettingsForComponent model=model class="theme-setting"}}
</div>
{{/d-section}}
{{else}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#d-section class="form-horizontal theme settings control-unit"}}
FEATURE: ability to add all active components to theme (#8447) * FEATURE: ability to add all active components to theme * FIX: add a component to all themes takes only active ones * FIX: move select components/themes to top * FIX: improve defaultIsAvailable * FIX: Add filter(Boolean) and remove btn class
2019-12-04 14:13:41 +08:00
<div class="row setting">
{{theme-setting-relatives-selector setting=relativesSelectorSettingsForTheme model=model class="theme-setting"}}
</div>
{{/d-section}}
FEATURE: Ability to add components to all themes (#8404) * FEATURE: Ability to add components to all themes This is the first and functional step from that topic https://dev.discourse.org/t/adding-a-theme-component-is-too-much-work/15398/16 The idea here is that when a new component is added, the user can easily assign it to all themes (parents). To achieve that, I needed to change a site-setting component to accept `setDefaultValues` action and `setDefaultValuesLabel` translated label. Also, I needed to add `allowAny` option to disable that for theme selector. I also refactored backend to accept both parent and child ids with one method to avoid duplication (Renamed `add_child_theme!` to more general `add_relative_theme!`) * FIX: Improvement after code review * FIX: Improvement after code review2 * FIX: use mapBy and filterBy directly
2019-11-28 13:19:01 +08:00
{{/if}}
FIX: Only block local edits for git-sourced themes (#11450) Themes uploaded as zip files are given a row in the `remote_themes` table to store metadata, even though they are not truly remote.
2020-12-10 03:41:42 +08:00
{{#unless model.remote_theme.is_git}}
FIX: Disallow editing of remote themes (#11189) Allowing the editing of remote themes has been something Discourse has advised against for some time. This commit removes the ability to edit or upload files to remote themes from Admin > Customize to enforce the recommended practice.
2020-11-13 23:57:49 +08:00
<div class="control-unit">
<div class="mini-title">{{i18n "admin.customize.theme.css_html"}}</div>
{{#if model.hasEditedFields}}
<div class="description">{{i18n "admin.customize.theme.custom_sections"}}</div>
<ul>
{{#each editedFieldsFormatted as |field|}}
<li>{{field}}</li>
{{/each}}
</ul>
{{else}}
<div class="description">
{{i18n "admin.customize.theme.edit_css_html_help"}}
</div>
{{/if}}
FEATURE: themes and components split * FEATURE: themes and components split * two seperate methods to switch theme type * use strict equality operator
2018-08-24 09:30:00 +08:00
FIX: Disallow editing of remote themes (#11189) Allowing the editing of remote themes has been something Discourse has advised against for some time. This commit removes the ability to edit or upload files to remote themes from Admin > Customize to enforce the recommended practice.
2020-11-13 23:57:49 +08:00
{{d-button
class="btn-default edit"
action=(action "editTheme")
label="admin.customize.theme.edit_css_html"}}
</div>
FEATURE: support uploads for themes This allows themes to bundle various assets
2017-05-10 05:20:28 +08:00
FIX: Disallow editing of remote themes (#11189) Allowing the editing of remote themes has been something Discourse has advised against for some time. This commit removes the ability to edit or upload files to remote themes from Admin > Customize to enforce the recommended practice.
2020-11-13 23:57:49 +08:00
<div class="control-unit">
<div class="mini-title">{{i18n "admin.customize.theme.uploads"}}</div>
{{#if model.uploads}}
<ul class="removable-list">
{{#each model.uploads as |upload|}}
<li>
<span class="col">${{upload.name}}: <a href={{upload.url}} rel="noopener noreferrer" target="_blank">{{upload.filename}}</a></span>
<span class="col">
{{d-button action=(action "removeUpload") actionParam=upload class="second btn-default btn-default cancel-edit" icon="times"}}
</span>
</li>
{{/each}}
</ul>
{{else}}
<div class="description">{{i18n "admin.customize.theme.no_uploads"}}</div>
{{/if}}
{{d-button action=(action "addUploadModal") class="btn-default" icon="plus" label="admin.customize.theme.add"}}
</div>
{{/unless}}
FEATURE: support uploads for themes This allows themes to bundle various assets
2017-05-10 05:20:28 +08:00
UX: display info about extra files and uploader (#9595) Co-authored-by: David Taylor <david@taylorhq.com>
2020-04-30 22:02:38 +08:00
{{#if extraFiles.length}}
<div class="control-unit">
<div class="mini-title">{{i18n "admin.customize.theme.extra_files"}}</div>
UX: collapse extra files when browsing a theme component (#9610)
2020-05-02 02:19:17 +08:00
<details>
<summary>
{{#if model.remote_theme}}
{{i18n "admin.customize.theme.extra_files_remote"}}
{{else}}
{{i18n "admin.customize.theme.extra_files_upload"}}
{{/if}}
</summary>
<ul>
{{#each extraFiles as |extraFile|}}
<li>{{extraFile.name}}</li>
{{/each}}
</ul>
</details>
UX: display info about extra files and uploader (#9595) Co-authored-by: David Taylor <david@taylorhq.com>
2020-04-30 22:02:38 +08:00
</div>
{{/if}}
If there are no settings do now show section
2018-03-05 08:11:21 +08:00
{{#if hasSettings}}
UX: improvements to admin theme UI
2018-08-31 03:23:15 +08:00
<div class="control-unit">
<div class="mini-title">{{i18n "admin.customize.theme.theme_settings"}}</div>
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#d-section class="form-horizontal theme settings control-unit"}}
UX: improvements to admin theme UI
2018-08-31 03:23:15 +08:00
{{#each settings as |setting|}}
theme settings need some bottom margin
2020-09-26 08:34:29 +08:00
{{theme-setting-editor setting=setting model=model class="theme-setting control-unit"}}
FEATURE: Support for localized themes (#6848) - Themes can supply translation files in a format like `/locales/{locale}.yml`. These files should be valid YAML, with a single top level key equal to the locale being defined. For now these can only be defined using the `discourse_theme` CLI, importing a `.tar.gz`, or from a GIT repository. - Fallback is handled on a global level (if the locale is not defined in the theme), as well as on individual keys (if some keys are missing from the selected interface language). - Administrators can override individual keys on a per-theme basis in the /admin/customize/themes user interface. - Theme developers should access defined translations using the new theme prefix variables: JavaScript: `I18n.t(themePrefix("my_translation_key"))` Handlebars: `{{theme-i18n "my_translation_key"}}` or `{{i18n (theme-prefix "my_translation_key")}}` - To design for backwards compatibility, theme developers can check for the presence of the `themePrefix` variable in JavaScript - As part of this, the old `{{themeSetting.setting_name}}` syntax is deprecated in favour of `{{theme-setting "setting_name"}}`
2019-01-17 19:46:11 +08:00
{{/each}}
{{/d-section}}
</div>
{{/if}}
{{#if hasTranslations}}
<div class="control-unit">
<div class="mini-title">{{i18n "admin.customize.theme.theme_translations"}}</div>
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#d-section class="form-horizontal theme settings translations control-unit"}}
FEATURE: Support for localized themes (#6848) - Themes can supply translation files in a format like `/locales/{locale}.yml`. These files should be valid YAML, with a single top level key equal to the locale being defined. For now these can only be defined using the `discourse_theme` CLI, importing a `.tar.gz`, or from a GIT repository. - Fallback is handled on a global level (if the locale is not defined in the theme), as well as on individual keys (if some keys are missing from the selected interface language). - Administrators can override individual keys on a per-theme basis in the /admin/customize/themes user interface. - Theme developers should access defined translations using the new theme prefix variables: JavaScript: `I18n.t(themePrefix("my_translation_key"))` Handlebars: `{{theme-i18n "my_translation_key"}}` or `{{i18n (theme-prefix "my_translation_key")}}` - To design for backwards compatibility, theme developers can check for the presence of the `themePrefix` variable in JavaScript - As part of this, the old `{{themeSetting.setting_name}}` syntax is deprecated in favour of `{{theme-setting "setting_name"}}`
2019-01-17 19:46:11 +08:00
{{#each translations as |translation|}}
{{theme-translation translation=translation model=model class="theme-translation"}}
UX: improvements to admin theme UI
2018-08-31 03:23:15 +08:00
{{/each}}
{{/d-section}}
</div>
If there are no settings do now show section
2018-03-05 08:11:21 +08:00
{{/if}}
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
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
<div class="theme-controls">
theme settings need some bottom margin
2020-09-26 08:34:29 +08:00
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
<a href={{previewUrl}} title={{i18n "admin.customize.explain_preview"}} rel="noopener noreferrer" target="_blank" class="btn btn-default">{{d-icon "desktop"}}{{i18n "admin.customize.theme.preview"}}</a>
<a class="btn btn-default export" rel="noopener noreferrer" target="_blank" href={{downloadUrl}}>{{d-icon "download"}} {{i18n "admin.export_json.button_text"}}</a>
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
UX: Remove Convert option for system themes (#12033)
2021-02-11 08:20:13 +08:00
{{#if showConvert}}
UX: Stop attempts to convert the default theme to a component by removing button Client-side of the fix.
2021-01-12 07:01:55 +08:00
{{d-button action=(action "switchType") label="admin.customize.theme.convert" icon=convertIcon class="btn-default btn-normal" title=convertTooltip}}
UX: Remove Convert option for system themes (#12033)
2021-02-11 08:20:13 +08:00
{{/if}}
FEATURE: allow disabling theme components (#7812) This allows you to temporarily disable components without having to remove them from a theme. This feature is very handy when doing quick fix engineering.
2019-07-03 16:18:11 +08:00
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{#if model.component}}
{{#if model.enabled}}
{{d-button
class="btn-default"
action=(action "disableComponent")
icon="ban"
label="admin.customize.theme.disable"}}
{{else}}
{{d-button
class="btn-default"
action=(action "enableComponent")
icon="check"
label="admin.customize.theme.enable"}}
{{/if}}
FEATURE: allow disabling theme components (#7812) This allows you to temporarily disable components without having to remove them from a theme. This feature is very handy when doing quick fix engineering.
2019-07-03 16:18:11 +08:00
{{/if}}
UX: Minor layout fixes and improved consistency on theme admin
2020-08-25 10:51:58 +08:00
{{d-button action=(action "destroy") label="admin.customize.delete" icon="trash-alt" class="btn-danger"}}
</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>
Reference in New Issue Copy Permalink