Ghost/ghost/admin/app/components/settings/form-fields/site-description.hbs

<div ...attributes>
    <div class="flex-grow-1">
        <label class="gh-setting-title" for="site-description">Site description</label>
        <div class="gh-setting-desc mb3">Used in your theme, meta data and search results</div>
        <div class="gh-setting-action" data-test-setting="description">
            <GhFormGroup @errors={{this.settings.errors}} @hasValidated={{this.settings.hasValidated}} @property="description" @class="description-container">
                <input
                    id="site-description"
                    type="text"
                    class="gh-input"
                    value={{this.settings.description}}
                    {{on "input" this.update}}
                    {{on "blur" this.validate}}
                    data-test-input="siteDescription"
                >
                <GhErrorMessage @errors={{this.settings.errors}} @property="description"/>
            </GhFormGroup>
        </div>
    </div>
</div>
Refactored general design settings form components refs https://github.com/TryGhost/Team/issues/1310 We want to use parts of the "Brand setting" form in a separate streamlined settings screen after site setup but that wasn't possible without a lot of duplication. - extracted individual form fields into separate components for re-use - included minor refactors like using `uploader.registerFileInput` and `uploader.triggerFileDialog` instead of continually duplicating the same file input trigger method - fixed accessibility issues - changed input titles from `<div>` to `<label>` and associated with the component's input fields - changed `<img {{on "click" upload}}>` to `<input type="image">` so they act as proper buttons and are linked to the label (required a styling change so `img` and `input[type="image"]` are treated equally) - finished cleanup of `.description-container-labs` by renaming to `.description-container` 2022-02-04 19:04:01 +03:00			`<div ...attributes>`
			`<div class="flex-grow-1">`
			`<label class="gh-setting-title" for="site-description">Site description</label>`
			`<div class="gh-setting-desc mb3">Used in your theme, meta data and search results</div>`
			`<div class="gh-setting-action" data-test-setting="description">`
			`<GhFormGroup @errors={{this.settings.errors}} @hasValidated={{this.settings.hasValidated}} @property="description" @class="description-container">`
			`<input`
			`id="site-description"`
			`type="text"`
			`class="gh-input"`
			`value={{this.settings.description}}`
			`{{on "input" this.update}}`
			`{{on "blur" this.validate}}`
🐛 Fixed close button on "unsaved changes" modal not always behaving like "Stay" button no issue The close button in the unsaved changes modal used the `@close` action directly compared to the "Stay" button which used `(fn @close false)`. The close button version without explicit arguments resulted in the first argument being a `PointerEvent` instance which if checked as a modal return value as `if (shouldClose)` would evaluate as truthy therefore matching the "Leave" behaviour instead of the "Stay" behaviour. - changed modal to explicitly call `(fn @close false)` when the close button is clicked - updated design settings route to have an explicit `shouldLeave === true` check so default behaviour is always "Stay" 2022-04-14 14:39:10 +03:00			`data-test-input="siteDescription"`
Refactored general design settings form components refs https://github.com/TryGhost/Team/issues/1310 We want to use parts of the "Brand setting" form in a separate streamlined settings screen after site setup but that wasn't possible without a lot of duplication. - extracted individual form fields into separate components for re-use - included minor refactors like using `uploader.registerFileInput` and `uploader.triggerFileDialog` instead of continually duplicating the same file input trigger method - fixed accessibility issues - changed input titles from `<div>` to `<label>` and associated with the component's input fields - changed `<img {{on "click" upload}}>` to `<input type="image">` so they act as proper buttons and are linked to the label (required a styling change so `img` and `input[type="image"]` are treated equally) - finished cleanup of `.description-container-labs` by renaming to `.description-container` 2022-02-04 19:04:01 +03:00			`>`
			`<GhErrorMessage @errors={{this.settings.errors}} @property="description"/>`
			`</GhFormGroup>`
			`</div>`
			`</div>`
			`</div>`