This is inspired from responses in #303
I do think that "running it in parallel to .page, and let the user choose what URL to give out" is a great usage for this domain name.
Regarding the main site www.codeberg.eu my suggestion is to use the site as aggregator for general FOSS information, think many Creative Commons texts (including some great books on the subject). Assembling the different knowledge from CC and GFDL texts in one place, like codeberg docs just broader.
Since Codeberg e.V is "gemeinnütziger Verein" even text with CC non-commercial can be included, adopted and expanded.
This type of knowledge base if done in formal and friendly way can be a gateway for new contributors.
What I'm suggesting is not a second arch-wiki but a curated general information site for anyone curious of what FOSS is about.
Books that I'd say worth basing this on are:
-Producing Open Source Software by Karl Fogel
-Ten Steps for Linux Survival by Jim Lehmer
-Two Bits, the Cultural Significans of Free Software by Christopher M. Kelty
For general topics texts like SUSE GNOME guide and Debian Handbook could also provide guidance on where to read about those things.
There are much more books, tutorial and blogs and writings online with suitable licenses to be adopted from.
Essentially we need a distillery of usefull FOSS information!
I'm suggesting www.codeberg.eu to be that.
Even books like https://assets.digitalocean.com/books/how-to-code-in-go.pdf can be good for some parts of the site when Go is talked about.
There are some books on FOSS that are great but has become outdated so they provide good scaffolding for the topics and ability for improvements and factual updates.
I don't think that dumping a bunch of text is a good idea, there needs to be some editorial oversight.
Arguing about if it should be FOSS or FLOSS is bikeshedding.
About the software, I know that static site generators are the what all the cool kids are using so I would suggest mdBook.
It has the ability to reuse parts of the text of one page in another (using // ANCHOR: comments magic word) the so called includes. This is important if separate parts would be referenced to different original texts (to give a proper credit).
edit: forgot to mention https://linuxjourney.com/ brilliant CC-BY-SA website but is somewhat outdated now. I'm sure there are a bunch more like that.