I started learning Wagtail at the beginning of May 2024 and put up a website using the Wagtail Tutorial.
Then I invested in the Ultimate Wagtail Developers Course by Kalob Taulien, who is a great teacher, and managed to put together a site that I am still working on.
Setting up a multisite is part of this process.
I have a few websites that I want to host on my main site and I am going to use Wagtail Multi-site to do that.
There are two options:
Django Multi-Tenancy – which is great if I was offering website services to clients and I want them to have their own space and log in details.
Wagtail Multi-site – which works for someone like me who wants to host different sites all under one roof. It can also be used for one organisation who has many different sub-pages they need to keep. Or a news site that has different sites and they want to share the same article on more than one site.
Getting started with multi-site
I went searching for a tutorial or helpful information on how to create a Wagtail multisite and struggled. There was an article on Wagtail.org that was written in 2016 with a site on GitHub – but very little else.
I was a little annoyed because I had no way of knowing how to do this myself. That’s when it hit me. All of my learning has come from following videos. I have never had to sit and work out how to build something myself.
Luckily, with the help of ChatGPT, I didn’t have to figure it out all by myself. I started using Co-Pilot and Chat but the Co-Pilot results were so poor I stopped using it.
My multi-site on GitHub
I am going to add the multisite that I have built on to GitHub and then type up everything I did, to the best of my ability, because it was a lot.
I could just upload what I have to GitHub today but I prefer to add commits as I go along so I can read back over what I have worked on. If I add it now I will be adding the complete site.
So, despite not really wanting to, I am going to start again. Add the multisite to GitHub right at the start and add commits as I go, then I will write it all up in my README.
Just like my training taught me to 🙂