The contents of the Zuul website
Go to file
James E. Blair dceec76b19 Add favicon
This adds the favicon (and associated variants and metatadata)
to the root of the site.

At this point, modern browsers do support serving most (if not all)
of this out of alternative paths.  The advantage of serving them
from the site root is:

* Subpages can get the favicon (and possibly some windows/apple
  desktop icons) without any added HTML.  This means our doc builds
  will automatically have favicons.

The disadvantages are:

* It's messy.
* The preview builds don't show the changes.
* If we ever change the icons, we may need to force refreshes in
  clients by adding more HTML tags anyway, including to the doc

The single advantage seems worth it to me at the moment, however.
I could easily be swayed the other way.

Change-Id: I1e6ca4e5e424540047265c194c6dba000aad195c
2018-05-10 14:25:21 -07:00
playbooks Add initial website content and jobs 2018-01-26 13:45:13 -08:00
roles Merge zuul-website-media when publishing site 2018-04-17 07:50:24 -07:00
www Add favicon 2018-05-10 14:25:21 -07:00
.gitignore Add simulation video 2018-04-17 14:59:17 -07:00
.gitreview Added .gitreview 2018-01-25 03:34:53 +00:00
.zuul.yaml Create a zuul-website gate queue 2018-04-24 12:31:18 -07:00
LICENSE.txt Convert Arcana files from DOS to UNIX line endings 2018-02-01 18:37:58 +00:00