You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently host our documentation on readthedocs, which is an instance of sphinxdocs.
#448 flags that some behaviours (ie redirections for older versions) throw up some error pages which may be confusing for some, and a workaround would be very convoluted on the current hosted platform. One way around this is to migrate away to a privately hosted sphinxdocs instance, with greater control over the plugins and environment.
We would need to consider:
initial migration
labour time to manage the server and software versioning
server costs of the infrastructure
Ensuring we can trigger builds via CI/CD processes like we do now
The text was updated successfully, but these errors were encountered:
We would also need to consider the cost associated with re-implementing RTD features, and/or maintaining a fork of RTD's open-source stack. A lot of work has gone into making RTD what it is!
And then, there's also the cost of implementing the new redirect mechanism, whatever that is.
Work on SEO and the issue of old versions of docs appearing in search results is something that we're looking into at the moment for IATI; we'll share whatever we find when we've got some ideas!
We currently host our documentation on readthedocs, which is an instance of sphinxdocs.
#448 flags that some behaviours (ie redirections for older versions) throw up some error pages which may be confusing for some, and a workaround would be very convoluted on the current hosted platform. One way around this is to migrate away to a privately hosted sphinxdocs instance, with greater control over the plugins and environment.
We would need to consider:
The text was updated successfully, but these errors were encountered: