framework/ember/app/templates/error.hbs

<header class="hero error-hero">
	<div class="container">
		<h2>Error</h2>
	</div>
</header>

<div class="error-area">
	<div class="container">
		<p>{{message}}</p>

		<pre>{{stack}}</pre>
	</div>
</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 17:26:10 +10:30			`<header class="hero error-hero">`
			`<div class="container">`
			`<h2>Error</h2>`
			`</div>`
			`</header>`
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="error-area">`
			`<div class="container">`
			`<p>{{message}}</p>`
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			`<pre>{{stack}}</pre>`
			`</div>`
			`</div>`