Issue 5329 - Optimize website-boilerplate for sharing on social media networks

includes/meta/standard.tmpl

 {#
  # This file is part of the website-defaults,
  # Copyright (C) 2017 eyeo GmbH
  #
  # website-defaults is free software: you can redistribute it and/or modify
  # it under the terms of the GNU General Public License version 3 as
  # published by the Free Software Foundation.
  #
  # website-defaults is distributed in the hope that it will be useful,
  # but WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  # GNU General Public License for more details.
  #
  # You should have received a copy of the GNU General Public License
  # along with website-defaults. If not, see <http://www.gnu.org/licenses/>.
  #
  # ---
  #
  # # Essential meta data for all websites
  #
  # ## title
  #
  # Optimal format
- # :  Primary Keeyword - Secondary Keyword | Brand Name
+ # :  Primary Keyword - Secondary Keyword | Brand Name
  #
  # Optimal length
  # :  50-60 characters (600px wide on desktop)
  #
  # Fallback
  # :  First highest level heading
  #
  # Nuance
  # :  Titles are user facing, therefore it's important that they are readable.
  #    But they must also be very compact. Full scentences, punctuation, and
  #    uncommon words are discouraged unless they are specifically targeted.
  #
  # ## description
  #
  # Optimal format
  #  :  Scentence
  #
  # Optimal length
  # :  Less than 160 characters
  #
  # Fallback
  # :  First 160 characters of phrasing content
  #
  # Nuance
  # :  Descriptions are no longer directly weighted by popular search engines.
  #    A good description introduces a page to encourage a click (which is
  #    directly weighted by popular search engines) in less than 160 characters.
  #}
 <meta charset="utf-8">
 <meta http-equiv="x-ua-compatible" content="ie=edge">

[juliandoucette, 2017/06/20 14:57:54]

Note: We have had discussions about these meta tags in the past (http-equiv &
viewport) and determined that they were necessary for responsiveness on mobile
and IE (I think).

 <meta name="viewport" content="width=device-width, initial-scale=1">
 {% if title %}

[juliandoucette, 2017/06/20 14:57:54]

Note: I had considered enforcing the optimal format of titles via something
like: title - category | site_name. But I decided against it so that we can have
a more fine-grained control of the title length. 

   <title>{{ title | translate("page-title", "Meta page title") }}</title>
 {% endif %}
 {% if description %}
   <meta name="description" content="{{ description | translate("page-description", "Meta page description") }}">
 {% endif %}

[juliandoucette, 2017/06/21 15:28:48]

Looks like we're missing alternate links! :O

Are we handling this already via HTTP headers?

See:
- https://support.google.com/webmasters/answer/189077
-
https://webmasters.googleblog.com/2011/12/new-markup-for-multilingual-content...

[juliandoucette, 2017/06/22 18:27:43]

In Rietveld only individual people make sense. But don't hesitate to
include anyone you consider suitable or necessary or potentially
useful or similar
No.

[ire, 2017/07/04 09:03:00]

Should the html5shiv and other IE-related scripts be included here as well?

[juliandoucette, 2017/07/04 10:05:27]

- I think it's a best practice to group link and script tags at the bottom of
the head (if not the bottom of the body)?
- I think that poly/pony fills don't have to be part of the minimum meta data on
all websites

Therefore I think that they belong in a separate meta include.

There is a lot of "think" in this opinion :D - what do you think?

[ire, 2017/07/04 13:27:50]

I think (:P) you're right. I didn't necessarily mean they needed to go in this
file, I just meant as a website-defaults meta.

[juliandoucette, 2017/07/04 14:49:29]

In that case: Yes.