I think along with an hypothetical version 1.0 (and maybe attracting new users and developers) we could clean/tidy a few other things as well, write some more developer documentation, where to look up how ActivityPub works, write down a few things from the video tour through the codebase as text, write some glossary about the terminology. Do a bit of cleanup work and delete old and unused CSS classes. Suppress the confusing exceptions in the maintenance task and fix the timeouts. Maybe gather stats from Celery and tie it into the admin interface.
I would absolutely love an easier way to deploy and more documentation on that process. I was able to get almost there but my system kept stopping working after docker compose up -d. It was more of a “see if I could do it” than anything else.
There’s quite a bit all over the place on the initial install. I think it should be two separate pages, one for containers and one for bare metal.
It looks like Rimu thinks the same - he’s created an Issue for himself here: https://codeberg.org/rimu/pyfedi/issues/411