Zum Inhalt springen

Archiv für "cms"

wget it on

Today the german hosting company "domainFactory" (dF) announced that they will stop supporting the old PHP Versions 4 and 5. dF is one of the last providers to do so.

So this comes as no surprise and I've been waiting for this moment for quite a while now: We have a couple of $clients that are running an old Version of the CMS "TYPO3" on hosting packages at domainFactory, and who won't update to a newer version, no matter how often we advised them. We have discussed, we pleaded, we stated more than once how important it ...


(The following is my translation of my blog post "KMUnverstand" which originally was published in German and seemed to resonate with quite a few people in my web dev bubble. It surely is full of grammar- and spelling-errors, but I hope the gist of it will come across anyway)

In our small web-studio we have our problems with advertising "hey, we've launched a new web site, look here, it's awesome!".

Because the launch is only a part of the ongoing process, the real work starts after the launch, even if many think that it is the finish line. But, especially with CMS-driven web sites, it needs some time and work by the editors to see if the ideas for the designed components really work as desired. Plus, even right after the launch one is already smarter than before and has many new ideas how to better solve some details than before. Despite the seemingly average life-span of web projects, our clients work with their sites way longer than five years. With the dynamic changes in the "web technology" field over the last five to ten years, this means that there needs to be constant team-work and a regulary exchange between us and our clients over possibilities and new or changed requirements.

Unfortunately, especially in the SME environment that we often deal with, "websites" are still seen as a fixed product. One "buys" this once, expecting it to work "as is" from that moment on until an internal decision in the distant future. So there is a great deal of ignorance and non-comprehension if ongoing maintenance and service shoud be considered and paid. The feeling of unwanted dependence is strong, especially because often open-source solutions seem to be initially "free". Because web packages for 5-10 EUR a month seem to work fine on first glance. If then a monthly support and maintenance package with at least 20 times the price is offered (a budget allowing for only 1-2 hours a month for work on the site), this totally seems over top and something that can be economized and saved. Why bother, the site works as is, right?


Wir in meiner Web-Butze tun uns ja immer etwas schwer mit "hey, neue Website gemacht, kuckt mal, voll toll!".

Weil, der Launch ist ja nur ein Teil, die eigentliche Arbeit geht ja erst danach los, auch wenn viele denken, damit wäre die Arbeit ja beendet. Aber, gerade bei CMS-angetriebenen Websites kommt erst im Laufe der Zeit, wenn die Redaktion damit arbeitet, Klarheit, ob und wie die angedachten Komponenten funktionieren. Dann ist man sowieso hinterher immer schlauer und hat schon wieder Ideen, wie man Dinge noch besser lösen kann. Entgegen der wohl marktüblichen "Haltbarkeit" von Webprojekten arbeiten unsere Kunden mit ihren Sites deutlich länger als fünf Jahre; und bei der Dynamik, die "Webtechnologie" in den letzten 5 bis 10 Jahren an den Tag legt, bedeutet das, dass man kontinuierlich gemeinsam und am Besten im regelmässigen und engen Austausch Veränderungen in Anspruch und Möglichkeiten abstimmt.

Leider sind, gerade im KMU Umfeld, mit dem wir es oft zu tun haben, "Websites" nach wie vor ein feststehendes Produkt. Man "kauft" sich das einmal, erwartet, dass es ab dann, bis zu einer internen Entscheidung in ferner Zukunft, "as is" funktioniert. Entsprechend verständnislos ist man dann, wenn eine laufende Wartung und Pflege bezahlt werden soll, das Gefühl von ungewollter Abhängigkeit steht schnell im Raum. Gerade weil oft Open-Source Lösungen erstmal scheinbar "kostenlos" sind. Weil Webpakete für 5-10 EUR im Monat ja auch erstmal zu funktionieren scheinen. Wenn dann eine monatliche Support und Wartungspauschale mit mindestens dem 20fachen Preis aufschlägt (wofür man sich wirtschaftlich gerechnet gerade einmal 1-2h pro Monat mit der Site beschäftigen kann), erscheint das erstmal als einsparbar. Läuft doch.

WordPress 4.9 - Tipton

This release features Customizer improvements, including the ability to save customization changes as drafts, schedule them to go live at a certain time, and letting other people preview the changes easier. To improve code editing in the admin we've introduced syntax highlighting and error checking to make things more robust and harder to break.

The Aesthetic Of Non-Opinionated Content Management: A Beginner’s Guide To ProcessWire – Francesco Schwarz

An great overview and introduction to my favorite CMS, by Francesco on Smashing Magazine:

I think what resonates with a lot of people is that ProcessWire is a system that goes from simple to complex, not the other way around. It doesn’t assume what you want to build, but instead lays a strong, non-opinionated foundation by offering you effective, powerful tools and leaving the rest to you. That conceptual aesthetic has, to me, a certain appeal to it.smashingmagazine.com

I like the term "non-opinionated content management" to describe how ProcessWire will not make any assumptions on how you ...