ghost/core/client/templates/modals/delete-all.hbs

{{#gh-modal-dialog action="closeModal" type="action" style="wide"
    title="Would you really like to delete all content from your blog?" confirm=confirm}}

    <p>This is permanent! No backups, no restores, no magic undo button. <br /> We warned you, ok?</p>

{{/gh-modal-dialog}}
Use CSS animations for modals No issue - Changes Modals to use CSS-based animations - All modals have an animation, so the option is removed from the handlebars helper - Removes `animation` from the handlebars helper, as all had one anyway - Removed the `centered` style - All modals should be left-aligned - Buttons now default to being on the left - Cleans up some styles (modal body top spacing) which #4632 helped clean up 2014-12-14 16:29:11 -05:00			`{{#gh-modal-dialog action="closeModal" type="action" style="wide"`
Creates Ember Modal infastructure resolves #2416 This is a pretty large commit but what it's adding are pretty fundamental to the admin app. - Creates top level actions on the ApplicationRoute for opening and closing modals. This allows sending the 'openModal' action from any template to open a modal. - Every modal template lives in 'templates/modals/{{modalName}}' - Each modal can have a backing controller of the same name that can provide additional control for that modal. Those controllers reside in 'controllers/modals/{{modalName}}' - Created the ModalDialog component which is where all the logic for the component resides. It's not at 100% parity with the existing Ghost modal system but it has the foundation for further fleshing out. It currently accepts parameters for styling how the modal should appear, which previously was defined in JS files in the Backbone admin. - This creates the 'delete all posts', 'delete this post', 'markdown', and 'upload' modal. Some are in more stages of completion than others, but I wanted to just get the foundation in place as fast as possible. - This also creates the UploadModal component which is a subclass of the ModalDialog component. The reason for this subclassing is that the UploadModal component directly accesses the DOM and when that occurs in Ember it should remain in a component definition. It's ready for extending to reach parity. Note: depending on needs the base ModalDialog class may need to be modified. 2014-03-30 23:07:05 -05:00			`title="Would you really like to delete all content from your blog?" confirm=confirm}}`

			`<p>This is permanent! No backups, no restores, no magic undo button. <br /> We warned you, ok?</p>`

Update Ember Components with proper gh- prefix GH-ISSUE 2373 2014-05-28 14:26:05 -05:00			`{{/gh-modal-dialog}}`