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

<!DOCTYPE html>
<html lang="<%= html_lang %>">
  <head>
    <meta charset="utf-8">
    <title><%= content_for?(:title) ? yield(:title) : SiteSetting.title %></title>
    <meta name="description" content="<%= @description_meta || SiteSetting.site_description %>">
    <%= render partial: "layouts/head" %>
    <%= render partial: "common/discourse_stylesheet" %>
    <%= theme_lookup("head_tag") %>
    <%= render_google_universal_analytics_code %>
    <%= yield :head %>
    <%= build_plugin_html 'server:before-head-close-crawler' %>
  </head>
  <body class="crawler <% if show_browser_update? %>browser-update<% end %>">
    <%= theme_lookup("header") %>
    <%= render partial: "layouts/noscript_header" %>
    <div id="main-outlet" class="wrap" role="main">
      <%= yield %>
    </div>
    <%= render partial: "layouts/noscript_footer" %>
    <%= theme_lookup("footer") %>
    <%= theme_lookup("body_tag") %>
    <% if show_browser_update? %>
      <div class="buorg"><div><%= I18n.t("js.browser_update").html_safe %></div></div>
    <% end %>
  </body>
  <%= yield :after_body %>
</html>
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 17:10:08 -05:00			`<!DOCTYPE html>`
FIX: HTML lang attribute expects hyphen instead of underscore 2018-08-20 13:55:58 +02:00			`<html lang="<%= html_lang %>">`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 17:10:08 -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 %>">`
			`<%= render partial: "layouts/head" %>`
UX: Make crawler view usable under different color schemes - Ensure the set of rendered `<link rel=stylesheet>` tags is consistent - Add var() references for all crawler-view styles. Basic color definitions are defined first, as a fallback for super old browsers 2022-04-06 17:10:46 +01:00			`<%= render partial: "common/discourse_stylesheet" %>`
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") %>`
FIX: Add Google Analytics code to crawler view 2015-02-02 00:49:58 -08:00			`<%= render_google_universal_analytics_code %>`
Include opengraph/oembed tags in the crawler layout. 2014-03-15 20:02:23 +05:30			`<%= yield :head %>`
FEATURE: add server:before-head-close-crawler outlet for plugins This outlet allows plugins to inject html prior to closing head tag 2018-10-25 16:31:05 +11:00			`<%= build_plugin_html 'server:before-head-close-crawler' %>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 17:10:08 -05:00			`</head>`
UX: Style edits (#19927) 2023-02-15 11:02:16 -06:00			`<body class="crawler <% if show_browser_update? %>browser-update<% 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: Make header/footer HTML consistent for crawler and noscript These were originally very similar, but have diverged over time. This makes it very difficult to manage styling. This commit moves the noscript header and footer into partials so they can be reused in both the crawler view and the `<noscript>` view. It also makes browser-update render the noscript content instead of the `<section id='main'>`, rather than adding adding the noscript inside the `<section>`. This provides better parity with the server-rendered crawler view. 2022-04-07 15:07:00 +01:00			`<%= render partial: "layouts/noscript_header" %>`
			`<div id="main-outlet" class="wrap" role="main">`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 17:10:08 -05:00			`<%= yield %>`
			`</div>`
UX: Make header/footer HTML consistent for crawler and noscript These were originally very similar, but have diverged over time. This makes it very difficult to manage styling. This commit moves the noscript header and footer into partials so they can be reused in both the crawler view and the `<noscript>` view. It also makes browser-update render the noscript content instead of the `<section id='main'>`, rather than adding adding the noscript inside the `<section>`. This provides better parity with the server-rendered crawler view. 2022-04-07 15:07:00 +01:00			`<%= render partial: "layouts/noscript_footer" %>`
DEV: consistent theme lookup in application / crawler / no-ember views (#7955) * removes `raw` helpers * include theme footer in the crawler view * include theme body tag content in no-ember pages 2019-07-31 01:00:46 +08:00			`<%= theme_lookup("footer") %>`
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("body_tag") %>`
FEATURE: Implement browser update in crawler view (#12448) browser-update script does not work correctly in some very old browsers because the contents of <noscript> is not accessible in JavaScript. For these browsers, the server can display the crawler page and add the browser update notice. Simply loading the browser-update script in the crawler view is not a solution because that means all crawlers will also see it. 2021-03-22 19:41:42 +02:00			`<% if show_browser_update? %>`
			`<div class="buorg"><div><%= I18n.t("js.browser_update").html_safe %></div></div>`
			`<% end %>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 17:10:08 -05:00			`</body>`
Open print dialog automatically 2016-08-01 02:06:55 -03:00			`<%= yield :after_body %>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 17:10:08 -05:00			`</html>`