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.
Today, we are finally starting to share our Techradar publicly. What is a Techradar?
The Techradar gives us an objective assessment of our technology portfolio which includes 4 key focus areas: Languages & Frameworks, Methods & Patterns, Tools, and Platforms & Operations.
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.
It's been a few months sine we migrated from Silverstripe to Docusaurus for our blog. Quite a few blog posts have been published since then via the CI pipeline we've set up. This blog post covers how we do things.
Since 2013 we have been using Silverstripe and the Silverstripe blog module as our blogging engine. After all those years, it is time to revisit and improve our toolchain as our requirements have changed over the years.
We decided to settle with Docusaurus for now. We'll share the "why" in one of our next blog posts, so stay tuned ;)
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:
Vom 24.02.2014 bis zum 28.02.2014 findet in Montreal die ConFoo 2014 Konferenz statt. Ich bin dieses Mal wieder dabei und kann zwei neue Vorträge präsentieren: Im Vortrag "The seven deadly sins of Dependency Injection" möchte ich darstellen welche Fehler man bei der Verwendung des Dependency Injection Patterns nicht machen sollte. Der Vortrag "The Setup: Composer, Phing, Vagrant, Jenkins" beleuchtet unsere Arbeitsweise mit den genannten Tools soll aufzeigen wie man mit den Tools arbeiten kann (aber nicht muss).
Vom 21.02.2014 bis zum 22.02.2014 findet in London die PHP UK 2014 conference statt. Ich freue mich als Sprecher dabei sein zu können und meinem Vortrag "The seven deadly sins of Dependency Injection" präsentieren zu können.
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 ;)