WriteFreely VS pages-gem

Mastodon is a microblogging service, so not meant for large bodies of text. This is why the text entry box is small, the columns are somewhat narrow (especially in deck mode) etc.

Platforms like https://writefreely.org/ , which are designed to be for blogging and long-form writing, are the place to write this. Write Freely federates so one can follow accounts and interact with posts via Mastodon etc.

Write Freely, open source writing space

Docs - https://writefreely.org/

It's all about federation, in these federated networks all these servers talk to eachother and exchange messages about stuff going on on the servers. So it's easy to set up a hidden service for the webui of one of them, but it's sometimes quite obscure to try and set up the federation for one of them. It depends on what settings they honor and what other types of encryption and authentication they require and stuff. But, if you put some effort in ahead of time, you can make it really simple: I don't know how to do it in rust(lemmy is written in rust), but here's a neat example of how to do it in Go: https://github.com/writefreely/writefreely/pull/710 which requires no complicated configuration.

An alternative to Plume is WriteFreely, which is a pretty clean & simple experience. Just don't expect to much regarding customization.

I also wish write.as were more popular. It's like old Medium, but less popular but with a more reader-friendly business model and self-host-able (AGPL v3)

And since you've mentioned you want to write a blog, take a look at WriteFreely: https://writefreely.org/

It's super easy to publish a static site like the resume with GitHub Pages. Just check out the docs.

GitHub Pages: Host your static websites directly from your GitHub repository.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Ideal for open source projects, docs sites, and portfolios. GitHub Pages

Github Pages: Link to Github Pages

Once you have all the documentation worked out a place to host it will be necessary. Some documentation generation may have ties in with specific hosting sites. Read The Docs' support for Sphinx and other documentation tools is one example. GitHub pages can be useful for GitHub hosted projects as it integrates well with GitHub Actions CI/CD deployments.

If you use GitHub and need to host a static website, consider GitHub Pages. Free for one site Stored on a GitHub public respository Deploy via web interface, or Git 100GB/month free bandwidth

https://pages.github.com/ https://docs.github.com/en/pages https://docs.github.com/en/pages/quickstart https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll

There are plenty of other hosting options you could use instead, such as GitHub Pages.

Functionally github.io just presents whatever you throw into the repository as the root directory of a site, github themselves host a very good, basic outline of how to set up a site on github.io.