Since mid of 2022, we've been using Docusaurus as blogging platform. In general, we are happy Docusaurus users, although it comes with a few limitations due to the nature of a static site generator.
When we migrated to Docusaurus in 2022, we were looking for options what consent management tool to use and how to integrate it into our Docusaurus setup.
I can't really recall when we started blogging initially, but we rebooted the bitExpert back in October of 2006, and ever since we migrated all content to newer blogging platforms. Back in the days we used b2evolution as blogging platform, moved to Wordpress, moved to Silverstripe Blog, and finally last year transitioned to Docusaurus.
Last week Docusaurus released version 3.0.0 and we managed to upgrade our blog without many issues.
As said before, we are still happy with Docusaurus as our blogging platform. However, Docusaurus being a static page generator, it comes with a few challenges in regard to scheduling and publishing blog posts.
One year ago, we switched from our homegrown Sliverstripe blog solution to Docusaurus. Time to look back and see if the move was worth it.
While improving the page indexing of our blog, I realized that Google still had old urls stored that aren't valid anymore. The challenge in this case: The urls in question could only be identified via specific get parameters.
Tech changes, quite rapidly. Coming across a blog post that covers outdated information happens frequently to me. Years ago, I came across a blog that displayed a "This blog post might be outdated banner" and I liked that approach.
We've covered the basics of our Docusaurus CI setup already in another blog post. In this blog post, we'll show you how to the build pipeline to lint the nginx configuration used in our Docusaurus setup.