Discource-C
/
discourse
mirror of https://github.com/discourse/discourse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
discourse/app/views/layouts/application.html.erb

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

124 lines
4.2 KiB
Plaintext
Raw Normal View History

Initial release of Discourse
2013-02-05 14:16:51 -05:00
<!DOCTYPE html>
FIX: HTML lang attribute expects hyphen instead of underscore
2018-08-20 07:55:58 -04:00
<html lang="<%= html_lang %>" 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 %>">
Code review comments.
2021-06-17 22:16:26 -04:00
<meta name="discourse_theme_id" content="<%= theme_id %>">
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
Move CSS link tags above JS in the head CSS are blocking resources, so keeping them below JS delays rendering of the page. CSS should be loaded ASAP. This change speeds up first contentful paint by 0.2s on localhost. The slower the device, the bigger the difference could be.
2020-11-16 22:26:37 -05:00
<%= render partial: "common/discourse_stylesheet" %>
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 %>
FEATURE: Add plugin html hook to insert html before any other scripts
2019-03-05 13:39:42 -05:00
<%= build_plugin_html 'server:before-script-load' %>
PERF: Move `preload` hints to the `<head>` (#15008) We have two JS assets which are included in the `<body>` of responses. We were including the `<link rel='preload'` hint alongside the script tag in the body. Instead, we can move the preload hint to the `<head>` so that the browser discovers it earlier, and can start preloading the assets while the body is loading.
2021-11-18 13:02:16 -05:00
<link rel="preload" href="<%= script_asset_path "start-discourse" %>" as="script">
<link rel="preload" href="<%= script_asset_path "browser-update" %>" as="script">
FEATURE: Show noscript view to unsupported browsers (#9373)
2020-04-08 13:24:18 -04:00
<%= preload_script 'browser-detect' %>
FEATURE: try adding some preload hints for chrome
2017-04-17 11:52:43 -04:00
<%= preload_script "locales/#{I18n.locale}" %>
FEATURE: Load translation overrides without JS `eval`
2019-11-04 20:15:44 -05:00
<%- if ExtraLocalesController.client_overrides_exist? %>
<%= preload_script_url ExtraLocalesController.url('overrides') %>
<%- end %>
DEV: Allow Ember CLI assets to be used by development Rails app (#16511) Previously, accessing the Rails app directly in development mode would give you assets from our 'legacy' Ember asset pipeline. The only way to run with Ember CLI assets was to run ember-cli as a proxy. This was quite limiting when working on things which are bypassed when using the ember-cli proxy (e.g. changes to `application.html.erb`). Also, since `ember-auto-import` introduced chunking, visiting `/theme-qunit` under Ember CLI was failing to include all necessary chunks. This commit teaches Sprockets about our Ember CLI assets so that they can be used in development mode, and are automatically collected up under `/public/assets` during `assets:precompile`. As a bonus, this allows us to remove all the custom manifest modification from `assets:precompile`. The key changes are: - Introduce a shared `EmberCli.enabled?` helper - When ember-cli is enabled, add ember-cli `/dist/assets` as the top-priority Rails asset directory - Have ember-cli output a `chunks.json` manifest, and teach `preload_script` to read it and append the correct chunks to their associated `afterFile` - Remove most custom ember-cli logic from the `assets:precompile` step. Instead, rely on Rails to take care of pulling the 'precompiled' assets into the `public/assets` directory. Move the 'renaming' logic to runtime, so it can be used in development mode as well. - Remove fingerprinting from `ember-cli-build`, and allow Rails to take care of things Long-term, we may want to replace Sprockets with the lighter-weight Propshaft. The changes made in this commit have been made with that long-term goal in mind. tldr: when you visit the rails app directly, you'll now be served the current ember-cli assets. To keep these up-to-date make sure either `ember serve`, or `ember build --watch` is running. If you really want to load the old non-ember-cli assets, then you should start the server with `EMBER_CLI_PROD_ASSETS=0`. (the legacy asset pipeline will be removed very soon)
2022-04-21 11:26:34 -04:00
<%= preload_script "vendor" %>
FEATURE: try adding some preload hints for chrome
2017-04-17 11:52:43 -04:00
<%= preload_script "application" %>
DEV: Introduce plugin api for conditionally rendering assets (#9200)
2020-03-13 11:30:31 -04:00
<%- Discourse.find_plugin_js_assets(include_official: allow_plugins?, include_unofficial: allow_third_party_plugins?, request: request).each do |file| %>
DEV: Debundle plugin javascript assets and don't load if disabled (#7566) And don't load javascript assets if plugin is disabled. * precompile auto generated plugin js assets * SPEC: remove spec test functions * remove plugin js from test_helper Co-Authored-By: Régis Hanol <regis@hanol.fr> * DEV: using equality is slightly easier to read than inequality Co-Authored-By: Régis Hanol <regis@hanol.fr> * DEV: use `select` method instead of `find_all` for readability Co-Authored-By: Régis Hanol <regis@hanol.fr>
2019-07-15 10:52:54 -04:00
<%= preload_script file %>
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 %>
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? %>
FEATURE: Load translation overrides without JS `eval`
2019-11-04 20:15:44 -05:00
<%= preload_script_url ExtraLocalesController.url('admin') %>
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? %>
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 13:00:46 -04:00
<%= theme_translations_lookup %>
<%= theme_js_lookup %>
<%= 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
FIX: update Google Tag Manager javascript
2018-04-03 14:20:51 -04:00
<%= render_google_tag_manager_head_code %>
Google Universal Analytics
2014-01-25 19:42:25 -05:00
<%= render_google_universal_analytics_code %>
DEV: Allow actions to change the manifest endpoint (#14522)
2021-10-06 16:41:52 -04:00
<link id="manifest-link" rel="manifest" href=<%= manifest_url %> crossorigin="use-credentials">
Google Universal Analytics
2014-01-25 19:42:25 -05:00
FEATURE: Native app banner improvements This commit adds some improvements to native app banners for iOS and Android - iOS and Android now have separate settings for native app banners - app banners will now only show for users on TL1 and up - app ids are now in a hidden site setting to allow sites to switch to their own app, if desired - iOS only: the site URL is passed to the app arguments
2019-04-17 12:25:13 -04:00
<%- if include_ios_native_app_banner? %>
FIX: only use app argument for official iOS app banner When showing the native app banner, we include an app argument to automatically add the current site to the official DiscourseHub app. However, the app id can be changed via a hidden site setting, and when changed, that argument is no longer useful. This ensures the argument is only included for the official iOS app banner.
2019-08-27 10:23:57 -04:00
<meta name="apple-itunes-app" content="app-id=<%= SiteSetting.ios_app_id %><%= ios_app_argument %>">
FEATURE: Opt-in native Discourse app install banner on Android/iOS
2017-01-03 12:50:45 -05:00
<%- end %>
move stylesheet after js
2017-04-20 12:34:40 -04:00
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' %>
extract client side `Discourse` setup inline JS (#6409)
2018-10-02 00:29:04 -04:00
<%= tag.meta id: 'data-discourse-setup', data: client_side_setup_data %>
Extract `discourse_javascript.html.erb` to a scrip include * extract omniauth auth complete inline JS * extract Ember error logging inline JS * transpile `authentication-complete` This is CSP related work
2018-10-09 01:50:45 -04:00
DEV: Allow us to use Ember CLI assets in production This adds an optional ENV variable, `EMBER_CLI_PROD_ASSETS`. If truthy, compiling production assets will be done via Ember CLI and will replace the assets Rails would otherwise use.
2021-05-05 09:02:48 -04:00
<meta name="discourse/config/environment" content="<%=u discourse_config_environment %>" />
FIX: Cleanup authentication_data cookie after login (#11834) This cookie is only used during login. Having it persist after that can cause some unusual behavior, especially for sites with short session lengths. We were already deleting the cookie following a new signup, but not for existing users. This commit moves the cookie deletion logic out of the erb template, and adds logic and tests to ensure it is always deleted consistently. Co-authored-by: Jarek Radosz <jradosz@gmail.com>
2021-01-25 08:47:44 -05:00
<%- if authentication_data %>
<meta id="data-authentication" data-authentication-data="<%= authentication_data %>">
Extract `discourse_javascript.html.erb` to a scrip include * extract omniauth auth complete inline JS * extract Ember error logging inline JS * transpile `authentication-complete` This is CSP related work
2018-10-09 01:50:45 -04:00
<%- end %>
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 %>">
DEV: adds server:after-body-open (#14106) This change is to allow to add a node at the top of body. This is currently done through DOM in a plugin which is causing a full Recalculate Style.
2021-08-24 08:35:44 -04:00
<%- if allow_plugins? %>
<%= build_plugin_html 'server:after-body-open' %>
<%- end -%>
FIX: update Google Tag Manager javascript
2018-04-03 14:20:51 -04:00
<%= render_google_tag_manager_body_code %>
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'] %>">
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 10:07:00 -04:00
<%= render partial: "layouts/noscript_header" %>
FEATURE: screenreader landmarks for main, suggested topics In order to avoid a boatload of attributeBindings, I moved the root element of the suggested-topics component into the template. Also, autoformat their hbs files. Testing info: https://www.scottohara.me/blog/2018/03/03/landmarks.html#using-screen-readers-to-navigate-landmarks Additionally, flag modals with aria-modal=true to avoid the screenreader accidentally escaping the modal. There's no need to ever toggle the attribute to false, because we display:none the modal root when it's closed.
2020-04-07 14:39:50 -04:00
<div id="main-outlet" class="wrap" role="main">
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 -->
</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
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 10:07:00 -04:00
<%= render partial: "layouts/noscript_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: remove code that restricted "header" theme field from admin There was some old code that restricted a percentage of a themes code from admin, only when admin was refreshed, this leads to lots of confusion Conditional is now removed
2018-10-15 02:29:10 -04: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
<%= theme_lookup("header") %>
Code review comments.
2021-06-17 22:16:26 -04:00
<%- end %>
<%- if allow_plugins? %>
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>
<% 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 %>
FIX: close `data-preloaded` div tag
2018-10-01 03:24:27 -04:00
<div class="hidden" id="data-preloaded" data-preloaded="<%= preloaded_json %>"></div>
PERF: Move `preload` hints to the `<head>` (#15008) We have two JS assets which are included in the `<body>` of responses. We were including the `<link rel='preload'` hint alongside the script tag in the body. Instead, we can move the preload hint to the `<head>` so that the browser discovers it earlier, and can start preloading the assets while the body is loading.
2021-11-18 13:02:16 -05:00
<script src="<%= script_asset_path "start-discourse" %>"></script>
move large blobs out of `<head>` (#6428) it unnecessarily bloats the section and increases the payload dramatically for open graph tags.
2018-09-28 05:28:33 -04: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
PERF: Move `preload` hints to the `<head>` (#15008) We have two JS assets which are included in the `<body>` of responses. We were including the `<link rel='preload'` hint alongside the script tag in the body. Instead, we can move the preload hint to the `<head>` so that the browser discovers it earlier, and can start preloading the assets while the body is loading.
2021-11-18 13:02:16 -05:00
<script src="<%= script_asset_path "browser-update" %>"></script>
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? %>
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 13:00:46 -04:00
<%= theme_lookup("body_tag") %>
move SiteText.{head,top,bottom} to SiteCustomization
2015-01-14 05:52:42 -05:00
<%- end %>
Code review comments.
2021-06-17 22:16:26 -04:00
<%- if allow_plugins? %>
<%= build_plugin_html 'server:before-body-close' %>
<%- end %>
Initial release of Discourse
2013-02-05 14:16:51 -05:00
</body>
</html>