Articles

Articles

Short practical notes about Drupal development, testing, AI-assisted work and keeping websites healthy.

Why does Drupal get slower over time?

Drupal does not become slow simply because it gets older. Most performance problems come from years of accumulated content, configuration, modules, media, scripts and maintenance debt.

Drupal admin interface as an editorial workbench

Many Drupal problems do not start on the public website. They start in the admin interface, where editors work with unclear forms, long lists and workflows that no longer match the organisation.

Drupal CMS 1 to Drupal CMS 2 upgrade

Drupal CMS is not a classic product that is simply upgraded from version 1 to version 2. An existing site needs a technical review first.

UX rules and system consistency

Why consistency is not an aesthetic preference but a functional requirement — and how to achieve it in practice.

How much does a Drupal website cost?

Drupal website cost is not mainly about design. The largest share of cost typically comes from functionality, integrations and ongoing maintenance.

Drupal go-live checklist

Going live is technical work, not only a button press. A good checklist reduces downtime and hidden errors.

Multilingual Drupal website — how it works

Drupal supports multilingualism systematically — content, interface, configuration and URLs can all be language-specific. It requires planning, but the results are correct.

What a good web project brief contains

A poor brief leads to wrong pricing, surprises mid-project and disputes at the end. A good brief does not need to be long — it needs to be precise.

PHP version and Drupal hosting

Drupal maintenance is not only module updates. The server PHP version must also be supported and upgradeable.

Why Drupal suits the public sector

Public sector websites must be secure, accessible and maintainable for years. Drupal meets these requirements better than most alternative CMS platforms.

Kaido Toomingas Kaido Toomingas WebPro Company OÜ

Need Drupal help?

If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.

Contact

How can we help?

Briefly describe the website or system that needs support. If you do not know the exact service yet, describing the need is enough.

Quick contact

If the issue is urgent, you can call or email directly. The main next step is still to describe your needs in the form.

Kaido Toomingas Kaido Toomingas WebPro Company OÜ
+372 53 533 822
kaido@webpro.ee