Nobody sold them Drupal: the CMS quietly beating the vendors built for government
You have probably sat through the pitch, or a version of it. A vendor stands up, says they build for government and only government, that they understand civic web in a way no generalist ever could, and then the price reflects exactly how special that understanding is. It sounds obviously right. The people who do one thing all day ought to be the best at that thing. So here is a result I genuinely did not expect when we started fingerprinting government websites. In American local government, the platforms sold specifically to government, by companies whose whole reason for existing is civic web, are being quietly and comprehensively out-built by a general-purpose open-source CMS that no salesperson ever walked into a town hall to recommend. Nobody demoed Drupal to anyone. It is still winning. The numbers, before anyone accuses me of cheerleading We fingerprinted the platform behind…
Cómo auditar el enlazado interno y las trampas de rastreo en Drupal con Entity Mesh
How to audit internal linking and crawl traps in Drupal with Entity Mesh
Entity Mesh is a Metadrop Drupal module that makes a site's internal link structure visible. It audits every node the way an anonymous crawler sees it, then aggregates the result into one exportable picture: where navigation breaks, where crawl budget leaks, and where language versions fall out of step. For a content-heavy or multilingual Drupal site, that turns internal linking from an invisible assumption into a measurable part of Technical SEO.
Every link is a navigation intentionStructuring content well starts with knowing how the site actually connects. Few Drupal modules give aggregated, site-wide information about content and its connections, so that picture is usually missing when decisions get made.
Entity Mesh was built to answer a specific question: how do nodes interconnect, and does the navigation they create match the one that was intended? If the goal is for a visitor to buy a product, the path from a landing page should lead to the product, not to the contact form. If the goal is a donation, the path should not end at the newsletter signup.
That makes internal linking more than a UX concern. It is also part of Technical SEO, because search engines follow internal links to discover content and to judge which…
How to automate WordPress-to-Drupal content migration with WordPress Migrate SQL
Some WordPress sites reach a point where the content model no longer fits the organization's needs. Custom content types, custom entities, and custom fields become necessary to represent internal data precisely, and Drupal supports all three, shaping that data with full flexibility.
Other sites reach that point because of AI. Drupal has built a strong AI ecosystem over recent years, enabling integrations of every needed type: content creation, accessibility checks, RAGs, among others. These are the two situations behind most WordPress-to-Drupal migrations: an architecture the site has outgrown, or an AI integration WordPress cannot support natively.
The challenge of migrating WordPress content to DrupalThe core challenge in a WordPress-to-Drupal migration is migrating the content itself. WordPress sites may host thousands of pieces of content that need to be moved to the Drupal site.
A full migration project runs through several phases: redesigning the site if needed, building the new architecture, and creating a Drupal node for every WordPress post or page. Creating the content is where the real work concentrates, since every image, every user, and every translation has to make it across, on top of adapting content to a different format defined by the new architecture.
A manual content migration is not viable due to its high costs and risks. Handled by hand, this work is prone to human error. A single error is easy to fix, but a…
Responsibility follows control
An AI model does not decide what data it can access, which tools it can use, or whether it can act without approval. People make those decisions at different points. Upstream, a model developer trains and tests the model and decides whether and how to release it. Downstream, a developer builds the model into a system, connects that system to data and tools, and decides whether a person must review its proposed actions before they take effect.
Those choices determine whether harm is possible at all. So when harm occurs, responsibility should fall on those who controlled the relevant choices. That responsibility may be shared: model developers control training and release, product builders control permissions and deployment, and users control deliberate misuse.
Responsibility should follow meaningful control.
That principle is missing from much of the debate over open-weight AI models, which often treats the decision to release a model as the only one that counts.
Axios recently reported that United States officials had considered measures that could restrict American companies from using Chinese open-weight models. Open-weight models make their trained parameters available for others to download, modify, and run on their own infrastructure, without going through the company that built them.
What’s the Deal with Schema
It’s not new and it’s not sexy, but Schema.org is getting a lot more attention these days. The reason is AI.
You’ve probably heard that Schema improves your AI search results — apply it to your site and voilà, better results. But what is it? How does it help with AI? And, more controversially, does it actually help at all?
World Wide Web Day: The Birth of the Web, And How Drupal Supports its Values
If you’re reading this article online, you’ve already experienced the impact of one of history’s most influential inventions. Chances are you’ve also visited several websites today to check the news, compare products, or fill out an online form.
Why We Contribute: The Philosophy Behind 1xINTERNET's Top-Tier Drupal Status
This is a guest post from the incredible team at 1xINTERNET, a Top-Tier Drupal contributor and digital agency headquartered in Frankfurt, Germany.
When the Drupal Association announced that 1xINTERNET had become one of the world's Top-Tier Drupal Contributors, it was a proud moment for the company. Reaching the highest level of contribution recognition places 1xINTERNET among a select group of organisations helping shape the future of one of the world's leading open-source content management systems.
Yet, ask anyone inside the company about the achievement, and you'll hear the same response: becoming a Top-Tier Contributor was never the ultimate goal.
Instead, it is the natural outcome of more than a decade of believing that if you build your business on open source, you should help build open source itself.
For over thirteen years, 1xINTERNET has invested in the Drupal ecosystem, not only by delivering digital platforms for clients, but by contributing code, maintaining projects, sponsoring community events, supporting governance, leading strategic initiatives and encouraging employees to actively participate in the community.
Today, the company sponsors more than 500 hours of Drupal contribution every month, actively supports more than 85 Drupal projects, has sponsored over 50 Drupal events, and has contributed to hundreds of issues across the Drupal ecosystem. Those numbers tell one story. The people behind them tell another.