Migrate primary domain to wagtail.org

Wagtail currently uses the wagtail.io domain for almost everything. For the last few years, we have owned wagtail.org, too. There are “political reasons” why using the .io TLD may not be ideal, and .org is probably more appropriate for an open source org.

This issue tracks the work required to make that transition happen.

Services

For obvious reasons, we should probably do each of the below sections one at a time. There are no dependencies on eachother, and trying to do the whole thing at once will almost certainly end badly.

Docs (readthedocs)

The docs are hosted with readthedocs. We should ensure docs.wagtail.io redirects to the new location.

• Add a new domain to readthedocs, and corresponding DNS record
• Setup redirect from old domain to new domain
• https://github.com/wagtail/wagtail/pull/7846
• https://github.com/wagtail/wagtail.io/pull/124

Email

This is mostly used for the security@ address. Whilst [e-mail] should be the default, we should ensure (and test) [e-mail] still ends up with the correct people.

Email is hosted with Mailgun, and uses an email alias configured there to route email to the relevant security contacts.

• Add new domain to mailgun, and setup corresponding DNS records
• Setup required email addresses
  • security@
  • accessibility@
  • hello@
• Generate a PGP key for security@, and upload to key servers
• Update existing addresses to be aliases for new ones
• https://github.com/wagtail/wagtail/pull/7845

Release checks

The wagtail admin uses releases.wagtail.io to determine whether it is currently running the latest version.

This is handled using an AWS Cloudfront distribution, which backs onto an S3 bucket.

• Add new domain to existing Cloudfront distribution, add relevant DNS recors
• Setup redirect from old domain to new
• https://github.com/wagtail/wagtail/pull/7847

wagtail.io

The wagtail.io site is hosted on Heroku. We should again put a redirect in place from wagtail.io to the new domain.

In addition to the site, the media is hosted out of S3 at media.wagtail.io.

• Create media S3 bucket
• Add new domains to Heroku, setup relevant DNS records
• Update sites in Wagtail admin to use new domain
• Setup redirects from old domain to new
• https://github.com/wagtail/wagtail/pull/7848
• https://github.com/wagtail/wagtail.io/pull/125
• Rename repository

There are likely to be SEO ramifications with this. We should liaise with the TBX SEO team to make sure we’re doing everything necessary.

---

Misc

This section collects other places wagtail.io is referenced, which will need migrating. These can all be done after the primary services have been migrated, and don’t require the same level of coordination.

• GitHub organisation URL (including “verified” badge)
• wagtail/wagtail repository URL
• wagtail/wagtail.io repository URL
• wagtail/bakerydemo references (https://github.com/wagtail/bakerydemo/pull/313)
• Update monitoring to track new domains (@RealOrangeOne)
• GitHub explore (https://github.com/github/explore/pull/2865)
• Wikipedia

---

Some parts may be left over still referencing wagtail.io (repo names, Heroku apps etc). It might be nice to migrate these too, but as we’re not losing control of wagtail.io, these aren’t as required, and can easily be done after the fact if needed.

The next step is to decide the order of events, and get (separate) PRs open to update any references in the codebase.

I can do the majority of these changes, however most will require coordination / permissions from some core team members.

[thibaudcolas]

Here are a few misc things we should update:

• wagtail/wagtail.io repository name
• [e-mail] email
• [e-mail] (used in https://github.com/wagtail/wagtail-localize-git) - https://github.com/wagtail/wagtail-localize-git/issues/27
• GitHub Explore topic https://github.com/github/explore/tree/main/topics/wagtail
• Wikipedia page https://en.wikipedia.org/wiki/Wagtail_(CMS)

GitHub code search for all wagtail.io occurrences in the wagtail org: https://cs.github.com/?scope=org%3Awagtail&scopeName=wagtail&q=wagtail.io.

[Scotchester]

Another place that I notice it needs updating: The GitHub repository link that appears on the right of the repo homepage, below the description: