Basic improvements to spec repo

[oskarth]

Problem

Current specs repository needs basic infrastructure and process improvements to better serve as a foundation for protocol standards.

Details

Core improvements needed:

• Dedicated website to render specifications properly
• Minor specification process improvements (e.g. no numbers for raw specs - see Vac RFC)
• Update README with clear contribution guidelines and templates (see proposal link in README)

Acceptance Criteria

• Working website that renders specs
• Minimally updated process documentation (bigger improvements out of scope)
• Improved README with guidelines

[oskarth]

Should also clarify scope a bit. E.g. focus on complementing and not competing (e.g. zkproofs.org work at lower level).

In general we want to make sure to interface with other existing specs, like:

• RFCs
• EIPs
• VC
• DIF
• zkproofs?
• POD?
• Etc

Two things to be mindful of:

• relying on external resources that haven’t existed for 10y+ and have proven longevity (guideline for EIPs, to protect against link rot etc)
• how to deal with things that aren’t well specified (eg circom/halo2/current pods)