CMS, editorial portals, document formats and knowledge management.
Luhmann's ninety thousand slips sit in two boxes and include the bibliography and the index. The criticism of the method predates the book that made it popular by eight years. And in 2026 several tools promising local notes plus AI stopped or split in two: Reor archived, Khoj Cloud shut down, Logseq separated into two versions.
Read moreHugo 0.9.0 builds a static site from Markdown with no external runtime: a single Go binary, the Blackfriday engine, html/template, indexes for taxonomies. Technical notes from a hands-on trial.
Read moreWhy digitising an editorial catalogue is mainly a problem of metadata and content typing, not of storage alone: the role of CMIS, SKOS, DITA and EPUB on top of an Alfresco core.
Read moreDoing knowledge management in a risk-analysis setting means indexing heterogeneous, versioned documents. What the open-source stack offers in 2009: semantic wikis, Lucene, Solr.
Read moreTechnical notes on building, in 2009, the website for a bimonthly magazine: an open-source CMS, RSS/Atom feeds, PDF distribution, and the problem of keeping the conversation alive between one issue and the next.
Read moreSince June 2005 there has been a standard Java API for reading from and writing to a content repository. What changes for open-source document management, and why repository portability weighs more than any single product.
Read moreShipping training material offline on a CD-ROM forces a format decision: a proprietary authoring tool tied to one platform, or XHTML/CSS files read locally by a browser. The second path outlives the vendor.
Read morepapiNet and ebXML (ISO/TS 15000) give B2B exchanges in the paper supply chain a shared vocabulary. Technical notes on schemas, messaging and transport, from the point of view of someone building portals for the sector.
Read moreAn industrial research project on a CMS can prototype on one Open Source stack and ship the definitive platform on another. When the two phases diverge, the verifiable legacy is the analysis and the modular design, more than the prototype's code.
Read moreTechnical notes on what keeps a high-traffic music portal standing in 2004: server farm, load balancing, the CMS, and the community services (chat, forum, webmail) that produce most of the requests.
Read moreAn application server with an object database and a content management framework keep content, presentation and workflow separate. Technical notes on Zope and the CMF, and on why the Open Source approach holds up against enterprise products.
Read moreWhy a content management platform should treat multi-channel publishing as a chain of XML transformations, and what it actually takes to get there in 2002.
Read moreAn editorial archive with several editors needs explicit publication states and per-transition permissions. DCWorkflow, in Zope CMF, models this as a state machine, kept out of the content type code.
Read moreWhat it takes to serve a high-traffic editorial site on a fully open-source stack: object database, acquisition, page templates and scaling with ZEO.
Read more
