a quick interest check: I kind of want to use our deployment’s spare capacity to host an invite-only WriteFreely instance where our regulars can host longer form articles

…but WriteFreely’s UI is so sub-optimal the official instance (write.as) runs a proprietary fork with a lot of the jank removed, and I don’t really consider WF to be production ready out of the box.

we can point the WF backend at arbitrary directories for its templates, page definitions, and static assets though, so maybe I could host those on codeberg and do a CI job that’d pull main every time it updates so we could collaboratively improve WF’s frontend? it’s not a job I want to take on alone (our main instance needs to take priority), but a community-run WF instance would be pretty unique

the pros of doing this are that WriteFreely at least seems to have very slim resource requirements and it’ll at least reliably host long form Markdown on the web

the downsides are again, it’s janky as fuck (it only supports Mailgun of all things for email, but if you disable that the frontend will still claim it can send password reset emails… but it’ll check the config and display an error if you click the reset link??? but they could have just hidden the reset UI entirely with the same logic???? also I don’t like the editing experience), and it’s not really what I’d consider federated — it shoots an Article into ActivityPub whenever you post, but it’s one-way so replies, boosts, and favorites won’t show up from ActivityPub which makes it feel a bit pointless. there might be a frontend-only way to link a blog post to the Mastodon or Lemmy thread it’s associated with on another instance though, which would allow for a type of comment system? but I haven’t looked much into it. write.as just has a separate proprietary service for comments that nobody else can use.

this definitely won’t replace Wordpress but does it sound like an interesting project to take on?