Drupal and WordPress
Where it goes wrong
An organization picks a platform because a vendor prefers it, then spends years working around it. A small nonprofit ends up with a Drupal site nobody on staff can edit. An association ends up with a WordPress site held together by a dozen plugins that each update on their own schedule.
What we do
WordPress is enough for many organizations: a clear public site, news, a contact form, and editors who have used it before. Drupal is the better fit when permissions and records matter. A member sees a different price than a guest. A committee edits only its own section. A registration has to know who has already paid.
Leonardo's work at Aero Design included custom Drupal modules and themes and WordPress plugins. This site runs on Drupal 11. If you already run one of the two, our default is to stay on it unless the platform is the reason the work is stuck.
How it runs
The choice is written into the scope with the reason for it, so the next person who looks after the site knows why. A move from one platform to another is a migration, scoped on its own.