Autor: Tim Strehle

[Sorry for the German blog post – I’ll publish an English version soon.] Ich arbeite für Digital Collections, einen Hersteller von DAM-Systemen (und mehr) mit Kunden hauptsächlich aus der Verlagsbranche. Deren Umbruch beobachten wir aus der Nähe und machen uns Gedanken darüber… Hier zwei Ideen, die ich aus meiner Perspektive als Software-Entwickler und Dokumentar für…

IndieWebCamp – Principles: “Own your data. Use visible data for humans first, machines second. […] Whatever you build should be for yourself. If you aren’t depending on it, why should anybody else? […] The more your code is modular and composed of pieces you can swap out, the less dependent you are on a particular…

Teresa Amabile and Steven Kramer for McKinsey – How leaders kill meaning at work: “Trap 1: Mediocrity signals […] Many of the other 65 Karpenter professionals in our study felt that they were doing mediocre work for a mediocre company—one for which they had previously felt fierce pride. By the end of our time collecting…

Facebook, Google+, Twitter, LinkedIn: Semi-closed networks have grown to capture most “social” interactions on the Web as well as a lot of content, and they own many people’s online identities. There’s an emerging trend in the software developer community to move out of these “walled gardens” or “silos” – for lots of good reasons (see…

David Diamond – DAM Beauty and Usability: “Beauty and usability are typically not words associated with digital asset management software, and for good reason. Have you seen the user interfaces of most DAMs? […] DAMs should be as close to invisible as possible. No one learns to create digital content just to spend time in…

I’m trying to find a good “elevator pitch” for building hypermedia APIs with HTML. How about this: Don’t build an API – publish your data instead: easy to read for both humans (not just developers) and software, and easy to link to. After providing read access, the next step is to enable others to modify…

One year ago, I wrote on Twitter that “my next API will be semantic XHTML”. Since then, I’ve been thinking a lot about Hypermedia APIs with HTML (and have done some prototyping). My dream API would use XHTML with RDFa, link to Atom feeds and offer an alternative JSON-LD representation. Here’s a few articles on…

The Typo3 Neos 2017 WCM Forecast has experts predict the future of Web content management, with some great quotes. Karen McGrane: “First, organizations will realize that WCMS doesn’t always support true multi-channel publishing. They will need to invest in new systems to decouple the authoring and storage layer from the presentation and publishing layer. This…