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.
Projects and articles tagged "Development".
Articles
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 2.0 makes starting with Drupal easier, but it does not remove the need for architecture, maintenance and responsibility.
Component-based development is not just a frontend trend — in Drupal it is a concrete architectural choice that affects both editorial workflow and long-term maintenance costs.
reCAPTCHA works, but it loads scripts from Google, tracks users and requires GDPR consent. Here is an alternative you can manage yourself.
Headless Drupal is a powerful architectural choice — but not for every project. Here is when it genuinely helps and when it simply adds complexity.
Drupal website cost is not mainly about design. The largest share of cost typically comes from functionality, integrations and ongoing maintenance.
An AI tool builds your site and puts it live. But when it breaks at 11pm, data leaks, or a client calls in a panic — who do you turn to?
Drupal multisite suits organisations managing multiple sites who want shared modules, updates and maintenance processes.
A website must do more than work. It must be secure, fast, privacy-compliant, accessible and readable by machines. Some of these are recommendations — others are legal requirements.
A modern website requires far more than one developer. Every requirement — security, performance, accessibility, GDPR, content — needs its own set of skills.
The WebPro website is a fully custom build, written with AI assistance. No Drupal, no ready-made framework. An honest account of the decisions, difficulties and outcome.
How AI helps build better workflows, tests and checklists when a developer stays in control.
AI can find useful signals, but code review must not become blindly accepted suggestions.
Automated workflows reduce manual work, make changes traceable and help avoid breaking the public website during development.
Going live is technical work, not only a button press. A good checklist reduces downtime and hidden errors.
A cheap website quote often leaves out work the client still has to pay for later.
A good contract describes not only the result, but also responsibility, testing and handover.
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.
Technical debt does not come from carelessness — it comes from decisions that were reasonable at the time. The problem is that it is not measured or managed.
If the old solution blocks every change, a version upgrade alone may not solve the problem.
Drupal Core search works for a small site. When content volume is high and search needs to be fast and accurate, Search API + Solr is the standard solution.
Paragraphs is one of the most widely used Drupal modules. It gives editors a flexible content builder without needing a developer for every change.
Layout Builder is built into Drupal core, Paragraphs is a module. Both let editors control page structure — but the right choice depends on your project's needs.
Views lets you display, filter and sort Drupal content without writing code. But in more complex scenarios it hits its limits. Here is when.
Migrate API is Drupal's built-in migration framework. It lets you map, transform and import content from practically any source.
Without config sync, Drupal configuration lives only in the database — invisible, unversioned, unrecoverable. Config sync makes it visible.
A custom module is the answer when existing modules do not cover the need. Here is when it is the sensible choice and what to budget for.
"3 months" is a common answer — but is it realistic? Here are honest timelines for different Drupal projects and what actually drives the schedule.
Both pricing models are valid — but for different types of projects. Here is what to watch out for with each.
Most projects do not stall because of bad code. They stall because of poor communication, unclear requirements, and unmet expectations.
Kaido Toomingas WebPro Company OÜIf the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.
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 WebPro Company OÜ