Visitar URL original
Migrate astropy.org to be hosted RTD · Issue #697 · astropy/astropy.github.com · GitHub
Skip to content

Migrate astropy.org to be hosted RTD #697

Description

@Cadair

This is a early warning / heads up issue.

As part of my Cycle 5 proposal to improve the unification of the astropy docs (https://github.com/astropy/astropy-project/blob/b04f81d10e268f700b4d6b9fe1fac5811daf155b/finance/proposal-calls/cycle5/aperio-documentation.md) it would be helpful to migrate astropy.org to be hosted on RTD.

The main motivation for this is that it allows the site to be indexed by the RTD server side search and to access that API without any tickery. This allows the unified search to work across the various projects and the homepage.

(It should also be noted that I'm in the process of migrating the site to be built with sphinx to enable all this as well)

Activity

  1. pllim commented on Jan 15, 2026

    @pllim
    Member

    But astropy.org itself would still work, right? If not, that is a huge headache.

  2. pllim commented on Jan 15, 2026

    @pllim
    Member

    Also... What about all the custom JS functions to scrape Affiliated packages?

  3. Cadair commented on Jan 15, 2026

    @Cadair
    MemberAuthor

    But astropy.org itself would still work, right? If not, that is a huge headache.

    Yes of course you can configure custom domains with RTD (docs.astropy.org for example also sunpy. org).

    Also arbitary JS, CSS and html are all perfectly possible with sphinx.

  4. pllim commented on Jan 15, 2026

    @pllim
    Member

    Possible, okay, but will it be easy?

  5. Cadair commented on Jan 15, 2026

    @Cadair
    MemberAuthor

    Yes it's easy, I'm already working on porting the website. The index page including the dynamic version number is done. You can also just include plain html pages in the output if you really want to.

    Some of the other JS can probably be replaced with build-time processing (think team.json) etc

    Can we leave technical issues and review till I have a functioning port?

  6. pllim commented on Jan 15, 2026

    @pllim
    Member

    I am thinking more of this

    fetch('https://raw.githubusercontent.com/pyOpenSci/pyopensci.github.io/main/_data/packages.yml')

  7. Cadair commented on Jan 15, 2026

    @Cadair
    MemberAuthor

    I haven't done that page yet, but it'll be fine.

  8. pllim commented on Feb 4, 2026

    @pllim
    Member
  9. Cadair commented on Feb 5, 2026

    @Cadair
    MemberAuthor

    @pllim can you add me to it so I can fiddle some settings?

  10. Cadair commented on Feb 9, 2026

    @Cadair
    MemberAuthor

    So after #696 caused issues elsewhere, I've done a little more research on the github pages setup.

    I think the main hurdle to overcome here is how we keep some astropy.org/<repo-name> URLs working where those repos want to be served from github pages and migrate astropy.org itself to RTD. data.astropy.org is one problematic case, but there may be others.

    It's possible on RTD to add redirects so we could add redirects to the /<repo-name> to either a plain github.io address or a specific subdomain configured for those repos to keep the /<repo-name> working.

    We could also choose to deploy the new theme to the GHP site as in interim solution even though it will mean the unified search can't search astropy.org (i.e. you could search all the docs from astropy.org but not astropy.org from the docs or astropy.org itself).

  11. pllim commented on May 11, 2026

    @pllim
    Member

    Can this be closed now?

  12. Cadair commented on May 12, 2026

    @Cadair
    MemberAuthor

    No, it's still not hosted on RTD.

  13. reopened this on May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions