Pretty sure pages.sr.ht is the easiest way to deploy a static website period
Other nice thing about pages.sr.ht is that the backend is really scalable. We run about 4,000 user static websites plus the pages.sr.ht software on one server with 4 cores and 8G of RAM and honestly it's grossly over-provisioned for the task
(content storage is provisioned separately on ceph, though)
Update 2024-01-15 15:50 UTC: pages.sr.ht is now available for full service, albeit with degraded performance for publish operations.
pages.sr.ht: we know this one is important to you. Stand by for updates, we're working on this one but it has a number of special challenges to bring back into service.
We have an update regarding pages.sr.ht. All custom *sub*domains and *.srht.site should be coming up shortly in read-only mode, subject to DNS propagation delays.
Users running a website on an apex record (i.e. example.org rather than sub.example.org) can get back online with MANUAL INTERVENTION. For details, see the status update here:
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.