Website that contains documentation

[markmandel]

Issue

Keeping our live documentation on github can be difficult when mixing documentation for features that are in development with features that are in the release.

Solution

We need a static site for Agones, that can be updated to the most recent version with each release, but also lets us review for each build.

Design

The site and documentation should remain in the Agones repo, so as to ensure that new features also are accompanied by documentation.

Risks

• There are redirect in place at agones.dev (running on app engine) that enable the canonical package of agones.dev, as well as redirects for our helm chart repo, etc. So we will need to take that into account with our eventual hosting option for the new site (App Engine, netlify, something else). We could possibly solve this by hosting the docs on a subdomain, or integrating the static site with the current codebase that is served at agones.dev via App Engine (but isn't currently open source - but could be).

Potential Solutions

• https://github.com/google/docsy-example

[markmandel]

Started pottering on this a bit: https://github.com/markmandel/agones/tree/feature/website

[markmandel]

Here's the live demo I'm working with at the moment, so people can keep track. https://agones-mark.appspot.com/site/

It needs some reorganising - but I'm going to try and get all the current documentation in it first, and then we can work on cleaning up the structure.

[markmandel]

/cc @thisisnotapril - figure you might be interested :wave: - work in progress, and all that.

[markmandel]

Website now has all the markdown content in it https://agones-mark.appspot.com/site/

Next steps:

1. [x] Remove all the broken links that currently exist
2. [x] Bring in the golang redirect logic for the canonical path and charts
3. [x] Give the landing page some kind of copy
4. [x] Integrate the link checker into the cloudbuild.yaml
5. [x] Integrate google analytics
6. [x] Integrate the search
7. [x] Add a starter blog post!
8. [x] Add a starter release post!
9. [x] Flesh out some of the blank sections - like contributing to the docs, etc.
10. [x] Delete the now duplicate markdown docs from the repo (or reduce their scope, and point to the new docs)
11. [x] Integrate with Cloud Build to run tests and create previews on each build
12. [x] Remove the :warning: blocks, and replace with date based published.

Anything else I'm missing?

Comments, reviews, feedback appreciated.