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

<!DOCTYPE html>
<html lang="<%= SiteSetting.default_locale %>" class="<%= html_classes %>">
  <head>
    <meta charset="utf-8">
    <title><%= content_for?(:title) ? yield(:title) : SiteSetting.title %></title>
    <meta name="description" content="<%= @description_meta || SiteSetting.site_description %>">
    <meta name="discourse_theme_key" content="<%= theme_key %>">
    <meta name="discourse_current_homepage" content="<%= current_homepage %>">
    <%= render partial: "layouts/head" %>
    <%= discourse_csrf_tags %>

    <%- if SiteSetting.enable_escaped_fragments? %>
      <meta name="fragment" content="!">
    <%- end %>

    <%- if shared_session_key %>
      <meta name="shared_session_key" content="<%= shared_session_key %>">
    <%- end %>

    <script>
      window.EmberENV = window.EmberENV || {};
      window.EmberENV['FORCE_JQUERY'] = true;
    </script>

    <%= preload_script "locales/#{I18n.locale}" %>
    <%= preload_script "ember_jquery" %>
    <%= preload_script "preload-store" %>
    <%= preload_script "vendor" %>
    <%= preload_script "pretty-text-bundle" %>
    <%= preload_script "application" %>
    <%- if allow_plugins? %>
    <%= preload_script "plugin" %>
    <%- end %>
    <%- if allow_third_party_plugins? %>
    <%= preload_script "plugin-third-party" %>
    <%- end %>

    <%- if staff? %>
      <script src="<%= ExtraLocalesController.url('admin') %>"></script>
      <%= preload_script "admin" %>
    <%- end %>

    <%- unless customization_disabled? %>
      <%= raw theme_lookup("head_tag") %>
    <%- end %>

    <%= render_google_universal_analytics_code %>
    <link rel="manifest" href="<%= Discourse.base_uri %>/manifest.json">

    <%- if SiteSetting.native_app_install_banner? %>
        <meta name="apple-itunes-app" content="app-id=1173672076">
    <%- end %>

    <%= render partial: "common/discourse_stylesheet" %>
    <%= render partial: "common/special_font_face" %>

    <%= yield :head %>

    <%= build_plugin_html 'server:before-head-close' %>
  </head>

  <body class="<%= body_classes %>">
    <%= render_google_tag_manager_code %>

    <div class='debug-eyeline'></div>

    <noscript data-path="<%= request.env['PATH_INFO'] %>">
      <%= render partial: 'header' %>
      <div id="main-outlet" class="wrap">
        <!-- preload-content: -->
        <%= yield %>
        <!-- :preload-content -->
        <footer>
          <nav itemscope itemtype='http://schema.org/SiteNavigationElement'>
            <a href='<%= path "/" %>'><%= t 'home_title' %></a>
            <%= link_to t('js.filters.categories.title'), path("/categories") %>
            <%= link_to t('guidelines_topic.title'), path("/guidelines") %>
            <%= link_to t('tos_topic.title'), path("/tos") %>
            <%= link_to t('privacy_topic.title'), path("/privacy") %>
          </nav>
        </footer>
      </div>

      <footer id='noscript-footer'>
        <p><%= t 'powered_by_html' %></p>
      </footer>
    </noscript>

    <%- unless customization_disabled? || loading_admin? %>
      <%= theme_lookup("header") %>
      <%= build_plugin_html 'server:header' %>
    <%- end %>

    <section id='main'>
    </section>

    <div id='offscreen-content'>
    </div>

    <% unless current_user %>
      <form id='hidden-login-form' method="post" action="<%=main_app.login_path%>" style="display: none;">
        <input name="username" type="text"     id="signin_username">
        <input name="password" type="password" id="signin_password">
        <input name="redirect" type="hidden">
        <input type="submit" id="signin-button" value="<%= t 'log_in' %>">
      </form>
    <% end %>

    <%- if @preloaded.present? %>
      <script>
      (function() {
        var ps = require('preload-store').default;
        <%- @preloaded.each do |key, json| %>
          ps.store("<%= key %>", <%= escape_unicode(json) %>);
        <% end %>
      })();
      </script>
    <%- end %>

    <%= yield :data %>

    <%= render :partial => "common/discourse_javascript" %>

    <%- unless customization_disabled? %>
      <%= raw theme_lookup("body_tag") %>
    <%- end %>
    <%= build_plugin_html 'server:before-body-close' %>
  </body>
</html>
Initial release of Discourse 2013-02-05 14:16:51 -05:00			`<!DOCTYPE html>`
formally remove IE9 support 2016-01-03 02:49:52 -05:00			`<html lang="<%= SiteSetting.default_locale %>" class="<%= html_classes %>">`
Initial release of Discourse 2013-02-05 14:16:51 -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>`
Add meta generator tag with the Discourse version. Use a partial for common head elements. 2014-06-19 18:17:52 -04:00			`<meta name="description" content="<%= @description_meta \|\| SiteSetting.site_description %>">`
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			`<meta name="discourse_theme_key" content="<%= theme_key %>">`
FEATURE: Allow the user to select a custom home page (#5268) * Add user_home configuration option * Use the new user_home preference to actually show the right home page * Fix trailing whitespace * Update user_option_serializer.rb * Fix JavaScript default homepage tests * Use an object instead of a giant switch * Remove trailing whitespace * Make the default `user_home` set to `null` instead of `0` * Rename user_home to homepage_id 2017-11-09 14:45:19 -05:00			`<meta name="discourse_current_homepage" content="<%= current_homepage %>">`
Add meta generator tag with the Discourse version. Use a partial for common head elements. 2014-06-19 18:17:52 -04:00			`<%= render partial: "layouts/head" %>`
remove csrf, font-face, css from js-off + crawler 2015-01-15 03:41:30 -05:00			`<%= discourse_csrf_tags %>`
use canonical-url plugin to make view more clean 2013-02-13 06:04:43 -05:00
CHANGE: We now include the `_escaped_fragment_` support by default, but only if the crawler check fails. It is a fallback for non-google search engines that support the Ajax crawling API. 2014-02-20 17:02:26 -05:00			`<%- if SiteSetting.enable_escaped_fragments? %>`
FIX: rss link in category pages 2015-01-02 07:06:57 -05:00			`<meta name="fragment" content="!">`
CHANGE: We now include the `_escaped_fragment_` support by default, but only if the crawler check fails. It is a fallback for non-google search engines that support the Ajax crawling API. 2014-02-20 17:02:26 -05:00			`<%- end %>`

FEATURE: allow long polling to go to a different url Added the site setting long_polling_base_url , this allows you to farm long polling to a different server. This setting is very important if a CDN is serving dynamic content. 2014-10-23 22:38:00 -04:00			`<%- if shared_session_key %>`
FIX: rss link in category pages 2015-01-02 07:06:57 -05:00			`<meta name="shared_session_key" content="<%= shared_session_key %>">`
FEATURE: allow long polling to go to a different url Added the site setting long_polling_base_url , this allows you to farm long polling to a different server. This setting is very important if a CDN is serving dynamic content. 2014-10-23 22:38:00 -04:00			`<%- end %>`

Upgrade jQuery 2016-02-10 12:14:37 -05:00			`<script>`
			`window.EmberENV = window.EmberENV \|\| {};`
			`window.EmberENV['FORCE_JQUERY'] = true;`
			`</script>`

FEATURE: try adding some preload hints for chrome 2017-04-17 11:52:43 -04:00			`<%= preload_script "locales/#{I18n.locale}" %>`
			`<%= preload_script "ember_jquery" %>`
			`<%= preload_script "preload-store" %>`
			`<%= preload_script "vendor" %>`
			`<%= preload_script "pretty-text-bundle" %>`
			`<%= preload_script "application" %>`
FEATURE: Add basic support for Safe Mode In Safe Mode all JS extensions and site customizations are disabled. To access Safe Mode visit `sitename.org/safe-mode` 2016-11-21 00:46:02 -05:00			`<%- if allow_plugins? %>`
FEATURE: try adding some preload hints for chrome 2017-04-17 11:52:43 -04:00			`<%= preload_script "plugin" %>`
FEATURE: Add basic support for Safe Mode In Safe Mode all JS extensions and site customizations are disabled. To access Safe Mode visit `sitename.org/safe-mode` 2016-11-21 00:46:02 -05:00			`<%- end %>`
			`<%- if allow_third_party_plugins? %>`
FEATURE: try adding some preload hints for chrome 2017-04-17 11:52:43 -04:00			`<%= preload_script "plugin-third-party" %>`
FEATURE: Add basic support for Safe Mode In Safe Mode all JS extensions and site customizations are disabled. To access Safe Mode visit `sitename.org/safe-mode` 2016-11-21 00:46:02 -05:00			`<%- end %>`
REFACTOR: Migrate markdown functionality in ES6 2016-06-14 14:31:51 -04:00
Our JS includes belong at the top of the file, that way we can start downloading and parsing them earlier and not wait for the rest of the page Our noscript stuff belongs at the bottom, we should not hold off any js work while noscript is downloading 2013-09-04 20:41:11 -04:00			`<%- if staff? %>`
FIX: cache admin locale file for 24 hours 2018-01-08 18:23:49 -05:00			`<script src="<%= ExtraLocalesController.url('admin') %>"></script>`
FEATURE: try adding some preload hints for chrome 2017-04-17 11:52:43 -04:00			`<%= preload_script "admin" %>`
Our JS includes belong at the top of the file, that way we can start downloading and parsing them earlier and not wait for the rest of the page Our noscript stuff belongs at the bottom, we should not hold off any js work while noscript is downloading 2013-09-04 20:41:11 -04:00			`<%- end %>`

move SiteText.{head,top,bottom} to SiteCustomization 2015-01-14 05:52:42 -05:00			`<%- unless customization_disabled? %>`
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			`<%= raw theme_lookup("head_tag") %>`
move SiteText.{head,top,bottom} to SiteCustomization 2015-01-14 05:52:42 -05:00			`<%- end %>`
FEATURE: allow for custom HTML inside the <head> tags 2014-01-02 10:22:04 -05:00
Google Universal Analytics 2014-01-25 19:42:25 -05:00			`<%= render_google_universal_analytics_code %>`
FEATURE: Add web manifest for Chrome users. 2015-09-20 11:00:30 -04:00			`<link rel="manifest" href="<%= Discourse.base_uri %>/manifest.json">`
Google Universal Analytics 2014-01-25 19:42:25 -05:00
FEATURE: Opt-in native Discourse app install banner on Android/iOS 2017-01-03 12:50:45 -05:00			`<%- if SiteSetting.native_app_install_banner? %>`
			`<meta name="apple-itunes-app" content="app-id=1173672076">`
			`<%- end %>`

move stylesheet after js 2017-04-20 12:34:40 -04:00			`<%= render partial: "common/discourse_stylesheet" %>`
			`<%= render partial: "common/special_font_face" %>`

RSS of a topic via new route Adds TopicView#recent_posts; Post#by_newest, #with_user, #author_readable; User#readable_name Autodiscovery tag in topic show HTML. 2013-02-21 13:20:00 -05:00			`<%= yield :head %>`
Pass a context in when using a HTML builder 2017-04-18 12:35:19 -04:00
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' %>`
Initial release of Discourse 2013-02-05 14:16:51 -05:00			`</head>`

UX: Apply the category class on initial page load 2016-07-04 12:10:52 -04:00			`<body class="<%= body_classes %>">`
FEATURE: Google Tag Manager Universal Analytics support 2016-07-14 13:52:37 -04:00			`<%= render_google_tag_manager_code %>`

UX: Allow the timeline to scroll mid post 2016-05-26 16:23:47 -04:00			`<div class='debug-eyeline'></div>`

Block browser-update.js in robots.txt. Move noscript block above everything else in application layout. 2014-02-14 15:32:49 -05:00			`<noscript data-path="<%= request.env['PATH_INFO'] %>">`
FIX: Support text only logos when activating account. 2015-02-25 11:35:47 -05:00			`<%= render partial: 'header' %>`
UX: fix container layout 2015-07-28 04:02:39 -04:00			`<div id="main-outlet" class="wrap">`
Block browser-update.js in robots.txt. Move noscript block above everything else in application layout. 2014-02-14 15:32:49 -05:00			`<!-- preload-content: -->`
			`<%= yield %>`
			`<!-- :preload-content -->`
FEATURE: add microdata prop and more links for crawler - add microdata based on schema.org - add breadcrumb on the top of topic - add navigations link on the bottom of every pages - add category description on the category list 2015-02-13 06:34:22 -05:00			`<footer>`
			`<nav itemscope itemtype='http://schema.org/SiteNavigationElement'>`
FIX: crawler pages and RSS had broken links for sites deployed to a subfolder with relative_url_root 2015-04-30 12:46:19 -04:00			`<a href='<%= path "/" %>'><%= t 'home_title' %></a>`
PERF: remove 10-20ms of work from every page view <% s=Time.now; main_app.categories_path main_app.guidelines_path main_app.tos_path main_app.privacy_path p (Time.now-s)*1000%> Returns 10-20ms consistently on i7-4770k, on shared hosts the cost could easily reach 40ms This code simply calculates the strings /categories /guidelines /tos /privacy It is ludicrous to spend this enormous amount of work just to calculate 4 strings. I do not know if this is something specific about Discourse or a bug in Rails (I tried without the main_app prefix and got similar results), regardless we can got to avoid these _path APIs for now Discovered this when running a flamegraph on our home page. 2016-01-21 06:43:56 -05:00			`<%= link_to t('js.filters.categories.title'), path("/categories") %>`
			`<%= link_to t('guidelines_topic.title'), path("/guidelines") %>`
			`<%= link_to t('tos_topic.title'), path("/tos") %>`
correct path 2016-01-21 15:55:07 -05:00			`<%= link_to t('privacy_topic.title'), path("/privacy") %>`
FEATURE: add microdata prop and more links for crawler - add microdata based on schema.org - add breadcrumb on the top of topic - add navigations link on the bottom of every pages - add category description on the category list 2015-02-13 06:34:22 -05:00			`</nav>`
			`</footer>`
Block browser-update.js in robots.txt. Move noscript block above everything else in application layout. 2014-02-14 15:32:49 -05:00			`</div>`
FEATURE: add microdata prop and more links for crawler - add microdata based on schema.org - add breadcrumb on the top of topic - add navigations link on the bottom of every pages - add category description on the category list 2015-02-13 06:34:22 -05:00
de-duplicate <footer> ids 2014-06-24 03:12:01 -04:00			`<footer id='noscript-footer'>`
Put the 'Powered by Discourse...' message shown to crawlers and no-js visitors in a footer element so that SEO something something. 2014-06-19 17:32:26 -04:00			`<p><%= t 'powered_by_html' %></p>`
			`</footer>`
Block browser-update.js in robots.txt. Move noscript block above everything else in application layout. 2014-02-14 15:32:49 -05:00			`</noscript>`

FIX: do not load custom header in admin section 2015-08-15 08:09:07 -04:00			`<%- unless customization_disabled? \|\| loading_admin? %>`
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' %>`
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations." 2013-12-18 14:47:22 -05:00			`<%- end %>`
Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations. 2013-12-01 19:11:20 -05:00
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations." 2013-12-18 14:47:22 -05:00			`<section id='main'>`
			`</section>`

Put Ember 1.8.1 + fixes back. 2014-12-04 08:48:25 -05:00			`<div id='offscreen-content'>`
			`</div>`

Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations." 2013-12-18 14:47:22 -05:00			`<% unless current_user %>`
FIX: Plugins were broken for initial payloads Our plugins use rails engines which are mounted against the main application's `ApplicationController`. This works great but path helpers need to reference `main_app` in order for it not to blow up. 2015-04-09 12:26:24 -04:00			`<form id='hidden-login-form' method="post" action="<%=main_app.login_path%>" style="display: none;">`
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations." 2013-12-18 14:47:22 -05:00			`<input name="username" type="text" id="signin_username">`
			`<input name="password" type="password" id="signin_password">`
			`<input name="redirect" type="hidden">`
Allow translating "Log In" button in HTML code. 2014-08-12 05:23:45 -04:00			`<input type="submit" id="signin-button" value="<%= t 'log_in' %>">`
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations." 2013-12-18 14:47:22 -05:00			`</form>`
			`<% end %>`

			`<%- if @preloaded.present? %>`
			`<script>`
REFACTOR: PreloadStore to ES6 2016-07-04 14:15:51 -04:00			`(function() {`
			`var ps = require('preload-store').default;`
			`<%- @preloaded.each do \|key, json\| %>`
			`ps.store("<%= key %>", <%= escape_unicode(json) %>);`
			`<% end %>`
			`})();`
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations." 2013-12-18 14:47:22 -05:00			`</script>`
			`<%- end %>`
Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations. 2013-12-11 11:17:55 -05:00
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations." 2013-12-18 14:47:22 -05:00			`<%= yield :data %>`
remove trailing whitespaces :heart: 2013-02-25 11:42:20 -05:00
Revert "Re-apply with fixes: Stop using user agent to detect mobile devices. Use a media query and yepnope to load the appropriate css and customizations." 2013-12-18 14:47:22 -05:00			`<%= render :partial => "common/discourse_javascript" %>`
add query parameter to temporarily disable customization 2013-11-12 12:13:17 -05:00
move SiteText.{head,top,bottom} to SiteCustomization 2015-01-14 05:52:42 -05:00			`<%- unless customization_disabled? %>`
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			`<%= raw theme_lookup("body_tag") %>`
move SiteText.{head,top,bottom} to SiteCustomization 2015-01-14 05:52:42 -05:00			`<%- end %>`
UX: Support for custom error pages and headers in plugins 2017-11-14 16:31:44 -05:00			`<%= build_plugin_html 'server:before-body-close' %>`
Initial release of Discourse 2013-02-05 14:16:51 -05:00			`</body>`
			`</html>`