Hello @Mike_Rogers, I’ve been planning to change how guides.rubyonrails.org and api.rubyonrails.org are built.
Currently they are being hosted on a private DigitalOcean droplet, and are being generated by a legacy set of scripts.
My goal is that the documentation is generated automatically during CI, and can be uploaded to some static host (like netlify) or other CDN.
The benefit of using CI is that people changing Rails and it’s documentation will get feedback when the docs break, ensuring only well-built documentation makes it to the public. The second benefit is that it’s entirely automated and transparent as to how and when it works. There was a recent incident with the old documentation server, and having to SSH in and regenerate docs by hand was unfortunate. Lastly, as you put – being able to push the docs to some CDN would greatly benefit folks reading them from around the world.
I think migrating guides and API (rdoc) this way should be trivial, the problem is contributors.rubyonrails.org is still served on this old DigitalOcean server as a (non-static) Rails application. So non-trivial to migrate to some static CDN. – but that is arguably less of a priority to Rails devs who just want to read the docs and learn.