Issue 5442 - Add logo microdata to eyeo websites

pages/index.html

 title=About Us
 description=Founded in 2011, eyeo is the company behind Adblock Plus, Adblock Browser and Flattr. We build products that millions of people use everyday to improve their online experience.
 
 <? include index/style ?>
 
 <div id="home-image-container">
   <img alt="eyeo office" src="/images/eyeo-home-1x.png" />
 </div>
 
 <div id="who-we-are" class="content-block columns-container two-columns">
@@ skipping 26 matching lines @@
       <div class="column">
         <? include index/ourwork-opensource ?>
       </div>
     </div>
   </div>
 </div>
 
 <div id="media" class="content-block">
   <? include index/media ?>
 </div>
+
+<script type="application/ld+json">

[juliandoucette, 2017/12/18 13:21:59]

See first comment in default.tmpl

[ire, 2017/12/20 08:25:59]

Acknowledged.

+  {
+    "@context": "http://schema.org",
+    "@type": "Organization",

[juliandoucette, 2017/12/18 13:21:59]

TOL: Now that we are defining Organization meta data, it seems like things are
obviously missing e.g. "name". This is ok, and we can add anything that we want
separately, as long as defining this script block doesn't override other forms
of macro data collection (as long as it's not one format or the other).

[juliandoucette, 2017/12/18 13:21:59]

TOL: We could define this in python (e.g. meta data, global, or include) and
then use a global/filter to output it in JSON

[ire, 2017/12/20 08:25:59]

- Yes there are already other issues for adding more microdata information
- I don't think it's "one format or the other", I think we can supplement the
markup microdata. But we can also just add the additional microdata here, this
JSON format is the preferred version according to the docs

[ire, 2017/12/20 08:25:59]

Sorry, I don't quite understand. Since the data will be different for each page,
what exactly should we define in a python global? Just this line that specifies
the @type?

[juliandoucette, 2017/12/20 11:50:16]

We could define a global macrodata object, extend it in pages and includes,
output it in json in a template.

Yes, @context, @type, anything else that is not page specific.

We should probably do this separately when we extend the macrodata in the
future.

[ire, 2018/01/03 14:01:18]

Ack. Agreed. 

+    "url": "{{ config.get("general", "siteurl") }}",
+    "logo": "{{ config.get("general", "siteurl") }}/images/logo-3x.png"
+  }
+</script>