In our attempt to migrate from our Silverstripe powered blog to Docusaurus, we did not want to lose our old blog posts and thus needed to migrate them somehow. A manual migration was not an option for the roughly 320 blog posts we have written in the last 17 years.
We are currently experimenting with Bookdown to generate the documentation for our open-source components in one central location. Obviously the generated site should have a similar look
nfeel as this blog or our website. Since both instances are powered by Silverstripe and share a theme I was curious if it is possible to use this theme within Bookdown. As it turns out, it is not that difficult ;)
As I have written before we moved from Wordpress to Silverstripe. The Silverstripe blog module has all the functionally needed to be used on a daily basis. However I was missing one particular feature of Wordpress: I want to be able to automatically publish blog posts via Cron. After some research it turned out that Silverstripe supports so-called BuildTasks which can be called from command line or via an url call. After some more research I came up with the following task that will run on a daily basis and publish all blog posts that have been scheduled for the current day:
A couple of weeks ago we relaunched our new website. In addition to that we decided to relaunch our blog as well. Since we wanted to use Silverstripe as CMS for our main website it made sense to use Silverstripe as a basis for our blog as well. Luckily there exists a blog module for Silverstripe which made it pretty easy to set-up this blog. The migration was no-brainer: Export the existing Wordpress content as XML file and import the XML file into Silverstripe via the wordpressimport module. The documentation of the wordpressimport module said it would be enough to add the following RewriteRule to the .htacess file:
Seit wenigen Tagen sind wir nun mit unserer überarbeiteten bitExpert Webseite und dem überarbeitenden Blog online. Statt Contenido und Wordpress nutzen wir nun Silverstripe als Basis für beide Auftritte. Dies hat den Vorteil dass wir die Templates nur einmal bauen mussten und in beiden Auftritten verwenden konnten. Dank Composer war das Dependency Management der verwendeten Pakete ein Kinderspiel. Wiederverwendung at it's best ;)