framework/ember/app/templates/discussion.hbs

<header class="hero discussion-hero">
	<div class="container">
		<h2>{{title}}</h2>
	</div>
</header>

<div class="container">
	<nav class="discussion-nav">
		{{ui/controls/item-list items=view.sidebarItems}}
	</nav>

	{{discussions/stream-content
		viewName="streamContent"
		stream=stream
		class="discussion-posts posts"
		component="discussions/post-wrapper"
		updateStart="updateStart"}}
</div>
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 14:56:10 +08:00			`<header class="hero discussion-hero">`
			`<div class="container">`
			`<h2>{{title}}</h2>`
			`</div>`
Hello world! 2014-12-20 14:26:46 +08:00			`</header>`

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 14:56:10 +08:00			`<div class="container">`
			`<nav class="discussion-nav">`
			`{{ui/controls/item-list items=view.sidebarItems}}`
			`</nav>`
Working on responsive dropdown menu components. 2015-01-02 09:16:40 +08:00
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 14:56:10 +08:00			`{{discussions/stream-content`
			`viewName="streamContent"`
			`stream=stream`
			`class="discussion-posts posts"`
			`component="discussions/post-wrapper"`
			`updateStart="updateStart"}}`
			`</div>`