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

<!DOCTYPE html>
<html lang="<%= SiteSetting.default_locale %>">
  <head>
    <meta charset="utf-8">
    <title><%= content_for?(:title) ? yield(:title) + ' - ' + SiteSetting.title : SiteSetting.title %></title>
    <meta name="description" content="<%= @description_meta || SiteSetting.site_description %>">
    <%= render partial: "layouts/head" %>
    <%- if rtl? %>
        <%= discourse_stylesheet_link_tag(mobile_view? ? :mobile_rtl : :desktop_rtl) %>
    <%- else %>
        <%= discourse_stylesheet_link_tag(mobile_view? ? :mobile : :desktop) %>
    <%- end %>
    <%= theme_lookup("head_tag") %>
    <%= render_google_universal_analytics_code %>
    <%= yield :head %>
  </head>
  <body class="crawler">
    <%= theme_lookup("header") %>
    <header>
      <a href="<%= path "/" %>"><img src="<%=SiteSetting.logo_url%>" alt="<%=SiteSetting.title%>" id="site-logo" style="max-width: 150px;"></a>
    </header>
    <div id="main-outlet" class="wrap">
      <%= yield %>
    </div>
    <footer class="container">
      <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>
      <p><%= t 'powered_by_html' %></p>
    </footer>
    <%= render_google_analytics_code %>
    <%= theme_lookup("body_tag") %>
  </body>
  <%= yield :after_body %>
</html>
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-15 06:10:08 +08:00			`<!DOCTYPE html>`
			`<html lang="<%= SiteSetting.default_locale %>">`
			`<head>`
			`<meta charset="utf-8">`
			`<title><%= content_for?(:title) ? yield(:title) + ' - ' + SiteSetting.title : SiteSetting.title %></title>`
Add meta generator tag with the Discourse version. Use a partial for common head elements. 2014-06-20 06:17:52 +08:00			`<meta name="description" content="<%= @description_meta \|\| SiteSetting.site_description %>">`
			`<%= render partial: "layouts/head" %>`
Adds some styling for crawler view 2016-11-15 04:32:59 +08:00			`<%- if rtl? %>`
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 22:52:52 +08:00			`<%= discourse_stylesheet_link_tag(mobile_view? ? :mobile_rtl : :desktop_rtl) %>`
Adds some styling for crawler view 2016-11-15 04:32:59 +08:00			`<%- else %>`
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 22:52:52 +08:00			`<%= discourse_stylesheet_link_tag(mobile_view? ? :mobile : :desktop) %>`
move SiteText.{head,top,bottom} to SiteCustomization 2015-01-14 18:52:42 +08:00			`<%- 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 22:52:52 +08:00			`<%= theme_lookup("head_tag") %>`
FIX: Add Google Analytics code to crawler view 2015-02-02 16:49:58 +08:00			`<%= render_google_universal_analytics_code %>`
Include opengraph/oembed tags in the crawler layout. 2014-03-15 22:32:23 +08:00			`<%= yield :head %>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-15 06:10:08 +08:00			`</head>`
Adds some styling for crawler view 2016-11-15 04:32:59 +08: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 22:52:52 +08:00			`<%= theme_lookup("header") %>`
normalize crawler and no-js views 2015-01-15 17:31:30 +08:00			`<header>`
Adds some styling for crawler view 2016-11-15 04:32:59 +08:00			`<a href="<%= path "/" %>"><img src="<%=SiteSetting.logo_url%>" alt="<%=SiteSetting.title%>" id="site-logo" style="max-width: 150px;"></a>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-15 06:10:08 +08:00			`</header>`
UX: fix container layout 2015-07-28 16:02:39 +08:00			`<div id="main-outlet" class="wrap">`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-15 06:10:08 +08:00			`<%= yield %>`
			`</div>`
remove unnecessary <footer> tags 2014-11-12 21:35:20 +08:00			`<footer class="container">`
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 19:34:22 +08:00			`<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-05-01 00:46:19 +08: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 19:43:56 +08: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-22 04:55:07 +08: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 19:34:22 +08:00			`</nav>`
Put the 'Powered by Discourse...' message shown to crawlers and no-js visitors in a footer element so that SEO something something. 2014-06-20 05:32:26 +08:00			`<p><%= t 'powered_by_html' %></p>`
			`</footer>`
FIX: Add Google Analytics code to crawler view 2015-02-02 16:49:58 +08:00			`<%= render_google_analytics_code %>`
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 22:52:52 +08:00			`<%= theme_lookup("body_tag") %>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-15 06:10:08 +08:00			`</body>`
Open print dialog automatically 2016-08-01 13:06:55 +08:00			`<%= yield :after_body %>`
Detect Googlebot from user agent and use a different layout that doesn't load javascript 2014-02-15 06:10:08 +08:00			`</html>`