{"id":6741,"date":"2026-08-06T16:01:24","date_gmt":"2026-08-06T14:01:24","guid":{"rendered":"https:\/\/kitech.ai\/web-cms\/"},"modified":"2026-08-08T17:47:50","modified_gmt":"2026-08-08T15:47:50","slug":"web-cms","status":"publish","type":"page","link":"https:\/\/kitech.ai\/en\/web-cms\/","title":{"rendered":"Web & CMS"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Web & CMS<\/h2>

Web presences and extensions that hold up in daily use.<\/em><\/p>

The problem<\/h3>

A website is quick to build. The difficult part comes afterwards: extensions that interfere with each other, updates that break something, and requirements for which there is no ready-made solution.<\/p>

What we do<\/h3>

We build websites on WordPress and develop the extensions that the standard does not include: as standalone modules, cleanly separated from the theme, so they survive updates.<\/p>

On top of that comes ongoing operation: updates, backups, monitoring, further development.<\/p>

We do not only build for clients. We also build for ourselves: with our own accounting solution, which we use in daily business. What we recommend, we generally use ourselves.<\/p>

How we proceed<\/h3>
  1. Ziel<\/strong> : What is the page for? Who should do what?<\/li>
  2. Structure<\/strong> : Page structure, navigation, content planning.<\/li>
  3. Implementation<\/strong> : Structure, extensions, connections.<\/li>
  4. Betrieb<\/strong> : Updates, backups, monitoring.<\/li><\/ol>

    Services in detail<\/h3>