Render spec using Bikeshed (#186)
As discussed on Matrix, this PR merges the 3 specs into a single spec document. If anyone missed that piece and doesn't feel comfortable with a merge, comment below!
This PR also switches the spec from plain Pandoc Markdown into the format of [Bikeshed](https://tabatkins.github.io/bikeshed), a tool that generates pretty interlinked standard specifications.
Bikeshed files have a `.bs` extension. You can ask your text editor to highlight them as Markdown (the formats differ, but for highlighting purposes this works nicely).
The spec will now live in the `spec.bs` file, which is rendered into `html/spec/index.html` and thus will be accessible at `https://forgefed.org/spec`.
**I suspect this huge PR is difficult to review. Since there's low activity here, I'm asking for your trust, that this PR changes only the *layout* of the info, and doesn't change anything at all about the vocabulary or processes. I copied them as-is, only making formatting tweaks for Bikeshed to render them properly.**
Now (March 12) I'm finally taking it out of WIP status and I'm going to give it a while. If no strong concerns appear, I'll probably merge it in a week or two, and move forward to the NLNet-funded tasks and lots of exciting stuff waiting for us in 2023!
Other/missing stuff for separate PRs:
- Tweak the color scheme based on the ForgeFed website CSS?
- Custom tweak via Bikeshed to add light/dark theme switch?
Co-authored-by: fr33domlover <fr33domlover@riseup.net>
Reviewed-on: https://codeberg.org/ForgeFed/ForgeFed/pulls/186
Reviewed-by: Anthony Wang <xy@noreply.codeberg.org>
Co-authored-by: fr33domlover <fr33domlover@noreply.codeberg.org>
Co-committed-by: fr33domlover <fr33domlover@noreply.codeberg.org>