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 %>
    <% if show_browser_update? %>
      <style>.buorg {position:absolute; z-index:111111; width:100%; top:0px; left:0px; background:#FDF2AB; text-align:left; font-family: sans-serif; color:#000; font-size: 14px;} .buorg div {padding: 8px;} .buorg a, .buorg a:visited {color:#E25600; text-decoration: underline;} @media print { .buorg { display: none !important; } }</style>
    <% end %>
    <%= build_plugin_html 'server:before-head-close-crawler' %>
  </head>
  <body class="crawler">
    <%= theme_lookup("header") %>
    <header>
      <a href="<%= path "/" %>">
        <h1><%=SiteSetting.title%></h1>
      </a>
    </header>
    <div id="main-outlet" class="wrap">
      <%= yield %>
    </div>
    <footer class="container wrap">
      <nav class='crawler-nav'>
        <ul>
        <li itemscope itemtype='http://schema.org/SiteNavigationElement'>
          <span itemprop='name'>
            <a href='<%= path "/" %>' itemprop="url"><%= t 'home_title' %> </a>
          </span>
        </li>
        <li itemscope itemtype='http://schema.org/SiteNavigationElement'>
          <span itemprop='name'>
            <a href='<%= path "/categories" %>' itemprop="url"><%= t 'js.filters.categories.title' %> </a>
          </span>
        </li>
        <li itemscope itemtype='http://schema.org/SiteNavigationElement'>
          <span itemprop='name'>
            <a href='<%= path "/guidelines" %>' itemprop="url"><%= t 'guidelines_topic.title' %> </a>
          </span>
        </li>
        <li itemscope itemtype='http://schema.org/SiteNavigationElement'>
          <span itemprop='name'>
            <a href='<%= path "/tos" %>' itemprop="url"><%= t 'tos_topic.title' %> </a>
          </span>
        </li>
        <li itemscope itemtype='http://schema.org/SiteNavigationElement'>
          <span itemprop='name'>
            <a href='<%= path "/privacy" %>' itemprop="url"><%= t 'privacy_topic.title' %> </a>
          </span>
        </li>
        </ul>
      </nav>
      <p class='powered-by-link'><%= t 'powered_by_html' %></p>
    </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 16:10:08 -06:00			`<!DOCTYPE html>`
FIX: HTML lang attribute expects hyphen instead of underscore 2018-08-20 06:55:58 -05:00			`<html lang="<%= html_lang %>">`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 16:10:08 -06:00			`<head>`
			`<meta charset="utf-8">`
don't force SiteSetting.title into meta title tag 2017-06-12 12:50:30 -05: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 17:17:52 -05: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 11:10:46 -05: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 09:52:52 -05:00			`<%= theme_lookup("head_tag") %>`
FIX: Add Google Analytics code to crawler view 2015-02-02 02:49:58 -06:00			`<%= render_google_universal_analytics_code %>`
Include opengraph/oembed tags in the crawler layout. 2014-03-15 09:32:23 -05:00			`<%= yield :head %>`
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 12:41:42 -05:00			`<% if show_browser_update? %>`
			`<style>.buorg {position:absolute; z-index:111111; width:100%; top:0px; left:0px; background:#FDF2AB; text-align:left; font-family: sans-serif; color:#000; font-size: 14px;} .buorg div {padding: 8px;} .buorg a, .buorg a:visited {color:#E25600; text-decoration: underline;} @media print { .buorg { display: none !important; } }</style>`
			`<% end %>`
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 00:31:05 -05: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 16:10:08 -06:00			`</head>`
Adds some styling for crawler view 2016-11-14 14:32:59 -06:00			`<body class="crawler">`
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 09:52:52 -05:00			`<%= theme_lookup("header") %>`
normalize crawler and no-js views 2015-01-15 03:31:30 -06:00			`<header>`
FIX: Do not display broken image on crawler/print view (#6575) 2018-11-07 16:28:45 -06:00			`<a href="<%= path "/" %>">`
linting (#16360) 2022-04-02 10:47:01 -05:00			`<h1><%=SiteSetting.title%></h1>`
FIX: Do not display broken image on crawler/print view (#6575) 2018-11-07 16:28:45 -06:00			`</a>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 16:10:08 -06:00			`</header>`
UX: fix container layout 2015-07-28 03:02:39 -05:00			`<div id="main-outlet" class="wrap">`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 16:10:08 -06:00			`<%= yield %>`
			`</div>`
UX: Improve posts layout for crawler (#7286) 2019-04-03 04:58:00 -05:00			`<footer class="container wrap">`
Improve support for old browsers (#9515) * FEATURE: Improve crawler view * FIX: Make lazyYT crawler-friendly * DEV: Rename discourse-internet-explorer to discourse-unsupported-browser * DEV: Detect more unsupported browsers Follow-up to 4eebbd221239eaa3fc7e6f1bd6a9dcf0239b8444. * FIX: Hide browser update notice in print view 2020-04-29 13:40:21 -05:00			`<nav class='crawler-nav'>`
UX: Cleanup crawler styles, improve schema.org markup (#7668) * Cleaning up crawler styles, improving some schema.org markup * Cleaning up crawler styles, improving some schema.org markup * additional styling * add space for pagination 2019-06-02 21:03:16 -05:00			`<ul>`
FIX: Resolve Schema.org validation issues 2020-05-05 08:56:04 -05:00			`<li itemscope itemtype='http://schema.org/SiteNavigationElement'>`
			`<span itemprop='name'>`
			`<a href='<%= path "/" %>' itemprop="url"><%= t 'home_title' %> </a>`
			`</span>`
			`</li>`
			`<li itemscope itemtype='http://schema.org/SiteNavigationElement'>`
			`<span itemprop='name'>`
			`<a href='<%= path "/categories" %>' itemprop="url"><%= t 'js.filters.categories.title' %> </a>`
			`</span>`
			`</li>`
			`<li itemscope itemtype='http://schema.org/SiteNavigationElement'>`
			`<span itemprop='name'>`
			`<a href='<%= path "/guidelines" %>' itemprop="url"><%= t 'guidelines_topic.title' %> </a>`
			`</span>`
			`</li>`
			`<li itemscope itemtype='http://schema.org/SiteNavigationElement'>`
			`<span itemprop='name'>`
			`<a href='<%= path "/tos" %>' itemprop="url"><%= t 'tos_topic.title' %> </a>`
			`</span>`
			`</li>`
			`<li itemscope itemtype='http://schema.org/SiteNavigationElement'>`
			`<span itemprop='name'>`
			`<a href='<%= path "/privacy" %>' itemprop="url"><%= t 'privacy_topic.title' %> </a>`
			`</span>`
			`</li>`
UX: Cleanup crawler styles, improve schema.org markup (#7668) * Cleaning up crawler styles, improving some schema.org markup * Cleaning up crawler styles, improving some schema.org markup * additional styling * add space for pagination 2019-06-02 21:03:16 -05:00			`</ul>`
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 05:34:22 -06:00			`</nav>`
UX: don't show crawler navigation in print view (#6551) * UX: adds CSS classes to crawler navigation links * UX: hide crawler navigation in print view 2018-11-01 17:18:07 -05:00			`<p class='powered-by-link'><%= t 'powered_by_html' %></p>`
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 16:32:26 -05:00			`</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-30 12:00:46 -05: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 09:52:52 -05: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 12:41:42 -05: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 16:10:08 -06:00			`</body>`
Open print dialog automatically 2016-08-01 00:06:55 -05:00			`<%= yield :after_body %>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-14 16:10:08 -06:00			`</html>`