Technology Stacks
Incumbent: Haunt
https://dthompson.us/projects/haunt.html
Its used by the Guix website for instance (which I have looked under the hood).
(Like Christine Lemmer-Webber, Im a Lisper and in the Guix community)
(Its a very rare situation where Im ever the one with an incumbent stack :s )
Id prefer it if it gets stated explicitly what technical features are needed to justify moving off any stack
(as somebody who normally is the one suggesting alternative approaches Id expect this reciprocated).
Stay on Haunt until full consensus emerges.
Nothing is worse than things being chucked out while somebody is working on the next big thing.
Formats
Haunt has a couple of additional formats it can read:
- sxml
- html
- texinfo
- commonmark
- skribe
Fwiw, Christine is using the Skribe format
i18n
This is pertinent given Guixâs own work with translatable content.
Heres a video regarding this:
https://10years.guix.gnu.org/program/#let-s-translate-guix-together-
If we stay on Haunt Id be happy to liaise with the developer community to ensure that the portal can handle multilingualism - as well as us pooling translatable content.
(the format PO comes to mind, not sure)
Their approach is to use a very GUI friendly translation tool.
And this is Guixâs i18n guide:
It is worth noting that Guixâs website is run using the SXML variant using a GNU orientated stack.
As such, it is operating with better technical solutions which may exclude some volunteers
(no doubt we need to focus on throughput).
Alternative: Vitejs/Astro
This tool for static sites has been very well recommended in multiple website builder threads recently:
I suspect that Astro will fulfill the criteria of most, though I would like to emphasize the benefits of minimal technology stacks.
i18n
This is Astroâs i18n guide:
Localisation is a win for me, and you have suggested something based upon Vite so I cant feel too aggrieved
(my nostrils were flaring thinking Lisp could still be in playâŠ)
General Points about i18n
One way or another we should feed off already translated content, which both silos can help with.
FWIW, its worth noticing that despite enough views, my appeal for widening diversity for the SH steering group we have come to nothing:
Perhaps there are more people out there who are keen on demonstrating the value of ActivityPub across different linguistic groupsâŠ
Forges
Although, no doubt Codebergâs page serving stack is low hanging fruit:
https://docs.codeberg.org/ci/
https://codeberg.page/
I did something equivalent for SourceHut - which was so simple it felt dastardly:
https://sr.ht/~sircmpwn/sourcehut/
IMHO, either Codeberg; Forgejo; or SourceHut are good initiatives.
Other (non HTML) Protocols
Any chance we can serve the ActivityPub Rocks Portalâs content for the protocol Gemini (in parallel)?
Once the technical structure is in place I dont mind doing the building for that.
Federated Technologies
In an ideal situation such a portal would be a living embodiment of federated technologies but I suspect this would require sustained commitment from multiple people for doing effectively.