Towards 1.0

[loicteixeira]

Discussed in #81

^{Originally posted by loicteixeira March 13, 2023}
For the last release, @Stormheg asked if we wouldn't go 1.0, and I said not quite.
Once we merge #79 with Wagtail 4.2 support, we will probably do another release, but I still believe it's not quite ready for a 1.0 release.
However, it would be a good milestone to reach, so I'll try to list here was I think is needed (bottom line, it should support default Wagtail features)
Please comment on whether I'm missing something and/or we should drop some issues.

Supporting all Wagtail features

• Add SitemapBuildableView #37 (PR Add SitemapBuildableView #48)
• Support S3 server-side redirects #14 & Wagtail RedirectView #16
• Unicode characters in slugs #17 (PR fix #17 Unicode characters in slugs #80)
• Does it work with multilingual content?

Bugs

• Build command seems to ignore set language #15 & Build command is not localizing dates #40
• Build fails if using external storage (such as S3) #41

Nice to have?

• Prevent unnecessary admin/wagtail static files from building #4 (I have an idea to fix upstream)

Other

• Implement Wagtail Python Package Maintenance Guidelines #74 & Move to wagtail-nest #78

[neo37]

I have developed a script that automates the deployment and configuration of Wagtail on a fresh Ubuntu server 22.:

🔗 wagtail-auto-deploy

The script works (though there are some nuances), and I believe it could be useful for developers who want a quick and automated way to set up Wagtail. If you find it helpful and are interested in collaborating on its development, that would be fantastic!

Backlog & Future Plans
I am planning to extend the project with the following features:

Accepting a domain name as input and automatically configuring Nginx.
Creating a Docker-based version for easier deployment.
Setting up basic infrastructure for CI/CD after the initial installation.
If this aligns with your roadmap, I would love to hear your thoughts and any suggestions for improvement.

Looking forward to your feedback!

Best regards, Kiselev Vasilii

[Yemeni]

I can confirm that it works for multi lingual content,
I used to export the files for me in folders like en, de, zh-hans, ar, fr and it works fine

I am using wagtail-localize and created a sperate app for the export html files so that it has a special query for language specific records