I agree the initial creation of wiki pages from manifests is not that hard to code, you just need a unique identifier across manifests and the wiki to not start creating duplicates.hiran wrote: ↑Mon Apr 05, 2021 2:11 pmI thought of something like automatically generating wiki pages from expansions. This could be a small batch job that runs at regular intervals or maybe as part of the CI/CD pipeline.maik wrote: ↑Mon Apr 05, 2021 11:50 am I wonder how we could automate this. Long-term it is a pain to maintain things twice, and thus will not happen consistently (e.g. if an OXZ author updates the description for the extension manager the copy on the wiki would need an update, too). Couldn't we have one source for this data only, and have both generated from this?
- it starts off with a list of expansions - this could be the same source that the expansion manager[ uses. (see http://wiki.alioth.net/index.php/Expansions_Manager)
- From that list it uses the download links, then downloads and scans the OXPs, OXzs and whatever it can get hold of. Not sure here, currently I think reading the manifest could be sufficient, future versions could access more information.
- From this information we could then generate wiki pages, one or several if need be. Or filterable/sortable ones if that is possible.
Not that hard to code. It would more require some knowledge about the expansions and the source to read and the destination to write.
- Finally these pages get uploaded into the oolite wiki.
The more difficult bit comes when there are updates. One author might leave the manifest as is and just update the wiki page, another might update the manifest but does not like editing the wiki, and the third one is happy to keep both in sync
I believe we should have a complete strategy before we implement such automation. The risk to mess up the wiki is quite real
I can see if I can create a wiki playground again for testing when we get somewhat further.