content is coupled to the code
Similarily to https://lab.allmende.io/ecobytes/lab/documentation/issues/12, after getting !4 (merged) merged, we can get back to the development and editorial workflows around the website.
Unfortunately the content is coupled to the code, which renders this repositories issue tracker https://lab.allmende.io/ecobytes/lab/website/issues into a list of technical and content related points. Separating the concerns of both different workflows will aid progressing more clearly with each.