CS

CMS

A content management system built to grow with your site

Content Management Systems designed for managing, publishing, and organizing large-scale web content and user roles.

Critical External Dependency: When a Vendor Becomes a Risk

Every company today depends on external technologies and vendors. We use cloud, SaaS services, payment gateways, accounting systems, hosting, or external developers. That is not a problem in itself. The problem starts the moment we cannot function without one particular vendor. That is called a critical external dependency. When does it become a problem? Picture an e-shop that has been running on a single platform for several years. It holds the website, the products, the orders, the stock, and the link to accounting.

Drupal Development

For 15 years I have worked with Drupal for Czech and international clients — mostly where the point-and-click admin stops being enough. I write the custom backend, connect Drupal to the rest of your systems, bring AI into it, and run it on infrastructure you control: your own VPS or cloud. Projects usually start with a technical workshop and a review of the current setup. Based on that I propose the architecture, scope, and timeline. I focus on clean code, security, testability, and easy maintenance.

Drupal Maintenance, Audit and Security

A Drupal site is not finished on launch day. Security releases come out, modules age, PHP versions reach end of life and take support with them. I take over Drupal maintenance — whether I built the site or someone else did — and keep it up to date, secure, and safe to change. I have worked with Drupal for 15 years, so code written by someone before me is familiar ground.

Drupal & Hugo Development

15 years of experience in developing professional web solutions – on both Drupal and Hugo. I help clients choose technology based on business goals, traffic, content structure, and operations. Both platforms run in production in my projects, and I can combine them in hybrid setups. Drupal vs. Hugo Comparison Criterion Drupal Hugo Project type Corporate portals, e-commerce, knowledge bases Presentations, landing pages, blogs, documentation Content management Structured, workflows, roles, and permissions Markdown in Git, simple editing Performance Scales with caching and infrastructure Extremely fast static files, excellent Core Web Vitals Security Regular updates, granular permissions Minimal attack surface, no database Integrations REST/JSON:API, CRM, ERP, AI, MCP Static generators, API at build time, CDN Operations Docker, VPS, AWS, DDEV, monitoring CI/CD, CDN, no server-side runtime Maintenance cost Higher – updates, modules, security Lower – Git, build, deploy When to Choose Drupal Drupal is the right choice when you need:

A Knowledge Base for AI in Drupal: RAG and MCP in Practice

A Drupal knowledge base is where a company maintains, approves, and keeps its knowledge current. An AI assistant built on it answers from content somebody stands behind, rather than from a pile of documents. In Which Open-Source CMS Should You Choose for an AI Knowledge Base? I compare five systems. This article goes deeper into one of them: how to design a knowledge base in Drupal and connect it to AI through an API, RAG, and MCP.

Which Open-Source CMS Should You Choose for an AI Knowledge Base?

Most companies introducing an AI assistant over internal knowledge start with technology: which model, framework, or vector database to use. Those layers can be changed when needed. A knowledge base and CMS give an AI project a stable foundation: they determine where company knowledge is created, who maintains it, and how it stays current and approved. AI then works with information the company can trust. A CMS as a knowledge base, not only a website In an AI project, a CMS has a different role than on a website. It is where knowledge is created, structured, approved, and maintained, and where AI retrieves it. The selection criteria therefore differ: