discourse/app/views/layouts/no_ember.html.erb

<!DOCTYPE html>
<html lang="<%= SiteSetting.default_locale %>">
<head>
  <meta charset="utf-8">
  <title><%= content_for?(:title) ? yield(:title) : SiteSetting.title %></title>
  <meta name="description" content="">
  <%= render partial: "layouts/head" %>
  <%= render partial: "common/special_font_face" %>
  <%= render partial: "common/discourse_stylesheet" %>
  <%= discourse_csrf_tags %>

  <%= theme_lookup("head_tag") %>
  <%= yield(:no_ember_head) %>
  <%= build_plugin_html 'server:before-head-close' %>
</head>
<body <% if @custom_body_class %>class="<%= @custom_body_class %>"<% end %>>
  <%= theme_lookup("header") %>
  <%= build_plugin_html 'server:header' %>
  <section id='main'>
    <%= render partial: 'header' %>
    <div id="main-outlet" class="<%= @container_class ? @container_class : 'wrap' %>">
      <%= yield %>
    </div>
  </section>
  <%= theme_lookup("footer") %>
  <%= build_plugin_html 'no-client:footer' %>
  <%= build_plugin_html 'server:before-body-close' %>
</body>
</html>
Initial release of Discourse 2013-02-05 14:16:51 -05:00			`<!DOCTYPE html>`
Use the correct locale in html lang attribute 2013-07-04 14:32:16 -04:00			`<html lang="<%= SiteSetting.default_locale %>">`
switch no_js view back to old layout 2015-01-15 15:29:37 -05:00			`<head>`
			`<meta charset="utf-8">`
don't force SiteSetting.title into meta title tag 2017-06-12 13:50:30 -04:00			`<title><%= content_for?(:title) ? yield(:title) : SiteSetting.title %></title>`
switch no_js view back to old layout 2015-01-15 15:29:37 -05:00			`<meta name="description" content="">`
			`<%= render partial: "layouts/head" %>`
			`<%= render partial: "common/special_font_face" %>`
			`<%= render partial: "common/discourse_stylesheet" %>`
			`<%= discourse_csrf_tags %>`

FEATURE: Native theme support This feature introduces the concept of themes. Themes are an evolution of site customizations. Themes introduce two very big conceptual changes: - A theme may include other "child themes", children can include grand children and so on. - A theme may specify a color scheme The change does away with the idea of "enabled" color schemes. It also adds a bunch of big niceties like - You can source a theme from a git repo - History for themes is much improved - You can only have a single enabled theme. Themes can be selected by users, if you opt for it. On a technical level this change comes with a whole bunch of goodies - All CSS is now compiled using a custom pipeline that uses libsass see /lib/stylesheet - There is a single pipeline for css compilation (in the past we used one for customizations and another one for the rest of the app - The stylesheet pipeline is now divorced of sprockets, there is no reliance on sprockets for CSS bundling - CSS is generated with source maps everywhere (including themes) this makes debugging much easier - Our "live reloader" is smarter and avoid a flash of unstyled content we run a file watcher in "puma" in dev so you no longer need to run rake autospec to watch for CSS changes 2017-04-12 10:52:52 -04:00			`<%= theme_lookup("head_tag") %>`
Rename `no_js` layout to `no_ember` While sometimes `no_js` was used for visitors without js (for example disabling it on your browser) it was also used for some pages that were disabled to JS capable browsers, including the 404 page. Even worse, sometimes it was used on pages that had Javascript, such as our `/activate-account` route. It has been renamed to `no_ember` to indicate what it really is, a layout for the site that doesn't load our Ember.js application. 2015-01-15 15:56:53 -05:00			`<%= yield(:no_ember_head) %>`
UX: Support for custom error pages and headers in plugins 2017-11-14 16:31:44 -05:00			`<%= build_plugin_html 'server:before-head-close' %>`
switch no_js view back to old layout 2015-01-15 15:29:37 -05:00			`</head>`
Add body class to `account-created` route 2016-05-05 14:37:09 -04:00			`<body <% if @custom_body_class %>class="<%= @custom_body_class %>"<% end %>>`
FEATURE: Native theme support This feature introduces the concept of themes. Themes are an evolution of site customizations. Themes introduce two very big conceptual changes: - A theme may include other "child themes", children can include grand children and so on. - A theme may specify a color scheme The change does away with the idea of "enabled" color schemes. It also adds a bunch of big niceties like - You can source a theme from a git repo - History for themes is much improved - You can only have a single enabled theme. Themes can be selected by users, if you opt for it. On a technical level this change comes with a whole bunch of goodies - All CSS is now compiled using a custom pipeline that uses libsass see /lib/stylesheet - There is a single pipeline for css compilation (in the past we used one for customizations and another one for the rest of the app - The stylesheet pipeline is now divorced of sprockets, there is no reliance on sprockets for CSS bundling - CSS is generated with source maps everywhere (including themes) this makes debugging much easier - Our "live reloader" is smarter and avoid a flash of unstyled content we run a file watcher in "puma" in dev so you no longer need to run rake autospec to watch for CSS changes 2017-04-12 10:52:52 -04:00			`<%= theme_lookup("header") %>`
UX: Support for custom error pages and headers in plugins 2017-11-14 16:31:44 -05:00			`<%= build_plugin_html 'server:header' %>`
FIX: Support text only logos when activating account. 2015-02-25 11:35:47 -05:00			`<section id='main'>`
			`<%= render partial: 'header' %>`
UX: fix container layout 2015-07-28 04:02:39 -04:00			`<div id="main-outlet" class="<%= @container_class ? @container_class : 'wrap' %>">`
FIX: Support text only logos when activating account. 2015-02-25 11:35:47 -05:00			`<%= yield %>`
normalize crawler and no-js views 2015-01-15 04:31:30 -05:00			`</div>`
FIX: Support text only logos when activating account. 2015-02-25 11:35:47 -05:00			`</section>`
FEATURE: Native theme support This feature introduces the concept of themes. Themes are an evolution of site customizations. Themes introduce two very big conceptual changes: - A theme may include other "child themes", children can include grand children and so on. - A theme may specify a color scheme The change does away with the idea of "enabled" color schemes. It also adds a bunch of big niceties like - You can source a theme from a git repo - History for themes is much improved - You can only have a single enabled theme. Themes can be selected by users, if you opt for it. On a technical level this change comes with a whole bunch of goodies - All CSS is now compiled using a custom pipeline that uses libsass see /lib/stylesheet - There is a single pipeline for css compilation (in the past we used one for customizations and another one for the rest of the app - The stylesheet pipeline is now divorced of sprockets, there is no reliance on sprockets for CSS bundling - CSS is generated with source maps everywhere (including themes) this makes debugging much easier - Our "live reloader" is smarter and avoid a flash of unstyled content we run a file watcher in "puma" in dev so you no longer need to run rake autospec to watch for CSS changes 2017-04-12 10:52:52 -04:00			`<%= theme_lookup("footer") %>`
UX: Support for custom error pages and headers in plugins 2017-11-14 16:31:44 -05:00			`<%= build_plugin_html 'no-client:footer' %>`
			`<%= build_plugin_html 'server:before-body-close' %>`
switch no_js view back to old layout 2015-01-15 15:29:37 -05:00			`</body>`
Initial release of Discourse 2013-02-05 14:16:51 -05:00			`</html>`