framework/ember/app/templates/composer.hbs

<div class="composer-handle"></div>

{{ui/controls/item-list items=view.controlItems class="composer-controls"}}

<div class="composer-content">
	{{#if content}}
		{{view content}}
	{{/if}}
</div>
Hello world! 2014-12-20 16:56:46 +10:30			`<div class="composer-handle"></div>`

Improve post composer + replying - Make it modular so that different entry points can show different things and respond differently (reply, new discussion, edit post) - Resizable - Fullscreen - Confirm on close 2015-02-02 16:57:59 +10:30			`{{ui/controls/item-list items=view.controlItems class="composer-controls"}}`
Hello world! 2014-12-20 16:56:46 +10:30
Implement redesign, refactor everything - Write CSS for everything, update templates. - Refactor discussion view. Stream is split into two components (content and scrubber) which have their own responsibilities. - Extract pane functionality into a mixin. - Implement global “back button” system. You give a “paneable” target to the application controller, the back button will modulate its pane-related properties as necessary, and call an action when the button is clicked. - Extract welcome-hero into its own component. - Lots of other general improvements/refactoring. The code is quite well-commented so take a look! 2015-01-16 17:26:10 +10:30			`<div class="composer-content">`
Improve post composer + replying - Make it modular so that different entry points can show different things and respond differently (reply, new discussion, edit post) - Resizable - Fullscreen - Confirm on close 2015-02-02 16:57:59 +10:30			`{{#if content}}`
			`{{view content}}`
			`{{/if}}`
Implement redesign, refactor everything - Write CSS for everything, update templates. - Refactor discussion view. Stream is split into two components (content and scrubber) which have their own responsibilities. - Extract pane functionality into a mixin. - Implement global “back button” system. You give a “paneable” target to the application controller, the back button will modulate its pane-related properties as necessary, and call an action when the button is clicked. - Extract welcome-hero into its own component. - Lots of other general improvements/refactoring. The code is quite well-commented so take a look! 2015-01-16 17:26:10 +10:30			`</div>`