How WebPro built its website — custom build, AI-assisted, honest review
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.
Articles
Articles
Practical articles about Drupal development, testing, AI-assisted work and keeping websites healthy.
🎧 Listen to the blog like a podcast Every article read aloud — filter by topic, search, and resume where you left off.
All (92) Drupal (61) Development (31) Maintenance (18) Security (14) Audit (13) AI (10) Migration (10) WCAG (9) E-commerce (6) Performance (5) Testing (5) GDPR (4) UX (3)
Visual regression testing with Playwright in Drupal workflows
Not every defect is functional. Sometimes an update breaks layout while the form still technically works.
AI content generation for websites — where it helps and where it harms
AI generates content quickly, but speed does not mean quality. Repetitive phrases, inaccurate information and a missing voice are risks that need to be managed deliberately.
Drupal scanner: a public pre-check before maintenance or upgrades
The Drupal platform assessment gives an initial public-data-based view of whether a website may need maintenance, upgrades or a deeper audit.
EU cancel button: new requirement for online shops
From 19 June 2026, many online shops must provide a clear electronic way to withdraw from a contract.
Playwright tests for forms, menus and carts
The most useful UI tests cover the journeys the client immediately notices when they break.
Schema.org structured data — a practical guide for Drupal
Schema.org markup tells search engines whether a page describes a service, an article, an organisation or a product. Google uses it for rich results, AI agents for understanding content.
AI in Drupal development — code review, tests and migration risks
How AI helps build better workflows, tests and checklists when a developer stays in control.
AI in code review: benefits, limits and responsibility
AI can find useful signals, but code review must not become blindly accepted suggestions.
Why we automate Drupal work as much as possible
Automated workflows reduce manual work, make changes traceable and help avoid breaking the public website during development.
Automated tests do not need to start big
Which Playwright and PHP tests usually bring the fastest value in a Drupal project.
Drupal go-live checklist
Going live is technical work, not only a button press. A good checklist reduces downtime and hidden errors.
Core Web Vitals in Drupal — common problems and how to fix them
LCP, CLS and INP are Google's metrics that affect search ranking. Drupal sites have specific causes and specific solutions for each.
How AI helps plan a Drupal migration
AI can speed up analysis, but migration responsibility stays with the technical team.
Drupal 11 migration: plan before code
Why the first migration task is mapping risks and dependencies, not writing code.
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.
Website budget: work that is often missing
A cheap website quote often leaves out work the client still has to pay for later.
Website accessibility: why WCAG is not only a public-sector topic
Accessibility affects sales, service, reputation and compliance. A broken form or checkout can exclude part of the audience.
Drupal maintenance contract or one-off fix — how to decide
A one-off fix solves a known bug. A Drupal maintenance contract reduces the chance of future bugs, missed security updates and expensive emergency work.
GDPR on websites: why it also affects ordinary contact forms
GDPR is not only a legal document. Website forms, logs, cookies, accounts and online orders all involve personal data.
What to ask a web developer before signing
A good contract describes not only the result, but also responsibility, testing and handover.
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.
Why an old website can be a business risk
If a website works only as long as nobody changes it, it is already a business risk.
Technical debt in web projects — how it builds and what it costs
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.
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.