Site and spec revamp before 3.2 about ircv3-specifications HOT 3 CLOSED

Moving stuff to GitHub pages might also be a good idea as it will mean we can have automatic page updates.

from ircv3-specifications.

I will handle this as soon as sasl-reauth is finished (#103).

from ircv3-specifications.

Alright, so for the spec documents to play nicely with Jekyll (Github pages generator), we'll also need to have some standard YAML front-matter on them, if we just want the website to use git submodule to pull this whole repo in as a submodule (which is the easiest way in terms of keeping specs on the website up-to-date).

An example of the required front matter would be something like this:

---
title: IRCv3.2 Metadata
layout: spec
---

Purely as an example, this repo being submodule'd in the ircv3.github.io repo as spec would produce URLs like:

• ircv3.org/spec/extensions/account-tag-3.2.html
• ircv3.org/spec/specification/metadata-3.2.html

Which is a bit ugly due to the spec/specification, but I'm not sure what else we could name the submodule while still being sorta sane in URLs (maybe git?). Otherwise, could maybe rename the specification folder in this repo to core.

from ircv3-specifications.