Countries around the world are investing millions of dollars in building data centers to meet the growing demand for generative artificial intelligence, while also storing data within their own borders....
Law student and activist Rodrigo Vallejos stands in front of Google's data center water storage tanks in the Quilicura district. The data center extracts water from the district's underground wells. Vallejos has been monitoring data centers in Santiago's metropolitan area for the past two years.
I’m new to Drupal and just getting started with it. I’ve mostly worked with other CMSs before, so Drupal feels a bit different and powerful at the same time.
I wanted to ask: what are the best things a beginner should focus on first? (modules, theming, configuration, etc.)
Any tips, learning resources, or common mistakes to Avoid would be really helpful.
As I’ve been exploring Drupal more and more, it has dawn on me that “Content Types” do not necessarily have to only be public facing things for a site - articles, posts, videos, etc. It occurred to me that I could manage my organization’s roster of members and students by making each its own content type and building Views to display them.
I would appreciate hearing from some of the experienced site builders here about some of the less conventional Content Types you’ve used.
I’m primarily a Laravel dev with a mix of React and Vue. I’ve been just barely dipped my toe into experimenting with Drupal since a lot of the things I build are really centered around content management.
My question is how much of an uphill battle down the road will it be to integrate very customized fields into the admin UI? I’m thinking things like maps, basic multimedia editing, niche drag-and-drop stuff. If there’s a library or I have the hours to build it out in React this is pretty straightforward in Laravel, but I haven’t found a ton on this in Drupal. I don’t believe in forcing systems to do things that aren’t a good fit, and I’m wondering if I’m trying to fit a square peg in a round hole by looking at Drupal for this kind of thing.
Dec 18, 22:34 UTC Resolved - Our Engineering has confirmed resolution of the issue. Users should no longer experience errors with attempting to deploy new static sites in NYC3 on App Platform.
If you experience any further problems or have any questions, please open a support ticket within your account.
Dec 18, 22:06 UTC Update - Our Engineering team has deployed a fix for the issue. Users should no longer experience errors when attempting to deploy new static sites now in NYC3 for App Platform.
We will post an update once we've confirmed that the issue is fully resolved.
Dec 18, 19:25 UTC Investigating - As of 17:45 UTC, our Engineering team is investigating reports of static site deployment failures in the NYC3 region on App Platform. Users may experience errors when attempting to deploy new static sites, resulting in failed deployments.
The existing static sites are still accessible and functioning normally.
Our team is actively working on identifying the root cause and implementing the fix.
We apologize for the inconvenience and will share an update once we have more information.
Dec 18, 21:34 UTC Resolved - Our Engineering team has confirmed full resolution of the issue. Users should no longer experience errors when making requests to the Cloud Control Panel or API.
If you experience any further problems or have any questions, please open a support ticket within your account.
Dec 18, 18:46 UTC Investigating - As of 17:47 UTC, our Engineering team is investigating reports of intermittent 504 errors when making requests to api.digitalocean.com and cloud.digitalocean.com. Users may experience sporadic errors, resulting in a 504 response code, when attempting to interact with our API or Cloud services.
At this point, the issue appears to be intermittent, and not all requests are being affected.
We apologize for the inconvenience and will share an update once we have more information.
Every evening, Keshev Dutt spends a couple of hours in his home in northern India, teaching small business owners in Bangladesh and Nepal how to use artificial intelligence. Not for...
I want to highlight a really useful module I’ve been exploring called Changelogify. If you manage Drupal sites where tracking and communicating what’s changed over time matters, this thing can be a serious quality-of-life boost. 
What It Is
Changelogify is a contributed Drupal module that helps you automatically collect changes happening on your site and publish them as a public changelog. It listens for various site events, groups them into releases, and then makes those changes visible in a structured way on your site. 
Why It’s Handy
Whether you’re maintaining a client site, building a product with frequent updates, or just want better visibility into what’s happened between deployments, this module lets you:
• Automatically capture tweaks and updates instead of manually jotting them down • Organize changes into releases so editors and users can see what changed and when • Surface a public changelog that keeps stakeholders informed and helps reduce support questions
It takes a lot of the manual bookkeeping out of tracking what’s happened during a sprint or over a release cycle. 
Who Might Like It
• Site builders who deliver regular feature updates • Teams with editors who want transparency into site revisions • Maintainers who want a lightweight way to publish update history without crafting change logs by hand
If you’ve ever wished Drupal could write its own release notes for you, Changelogify is worth checking out.
I noticed that the XML Sitemap generation stopped working a couple of weeks ago. When I go to rebuild the sitemap manually, we immediately get a 502 Bad Gateway error.
After much unsuccessful troubleshooting, we tried the Simple XML Sitemap module and surprisingly got the same error.
Disabling Cloudflare fixes the issue but since we need Cloudflare to be active, we need to find out the cause.
Using Cloudflare Free Tier
Some /batch functions cause a 502 error
Pausing Cloudflare fixes the issue
We tried creating a rule to bypass caching for the /batch path (no change in the error)
The issue occurs with XML Sitemap, and Simple XML Sitemap. However, other batch operations, like rebuilding the permissions work as expected
Sitemap generation worked correctly for years, until a couple of weeks ago
I'm hoping for any insight as to what may be causing the failure.
One morning in October, Luciano Galfione walked through his family’s textile factory in Buenos Aires, a cavernous warehouse where some of the more than 100 employees spin, knit, and dye...
With AI, headless CMS, and composable architectures growing fast, where do you see Drupal developers fitting in by 2026? What skills do you think will matter most?
I'm trying to migrate content from a WordPress site to a fresh Drupal 11 installation using the contributed wordpress_migrate module (the UI/GUI process).
I'm running into an issue where the module's setup UI fails to detect my destination fields, likely because my Drupal structure uses modern, non-standard field types (Media Entity Reference) and custom machine names, while the module expects the old default settings.
I need advice on the correct YAML configuration to manually map these fields.
1. 📝 Body Field Issue
The WordPress content body (content:encoded) is not being recognized for import.
Drupal Destination Field Name:field_content
Drupal Field Type:Text (formatted, long)
Expected Field Type (by Module): Likely the standard body field with type Text (formatted, long, with summary).
Goal: How should I structure the process: section in my migrate.migration.wordpress_post.yml to map content:encoded to my existing field field_content?
2. 🖼 Featured Image Issue (Crucial: Media Entity)
I cannot map the WordPress Featured Image because my Drupal setup uses the modern Media Entity reference approach.
Drupal Destination Field Name:field_featured_image
Drupal Field Type:Entity reference (Referencing Media Entity of type Image).
Expected Field Type (by Module): Likely a basic Image file field type.
Goal: What is the recommended multi-step process: pipeline (using file_copy, entity_generate, or migration_lookup) to take the WordPress image URL, create a Media Entity in Drupal, and reference it in my field_featured_image field? Working YAML examples for migrating WXR attachments to Media Entities would be highly appreciated!
3. 💬 Comments Migration
The WXR file contains comment data. Is there any hope to migrate comments (users, body, timestamps) to the native Drupal comments using the wordpress_migrate module or does this typically require another separate migration definition?
The Covid-19-era bubble had not yet burst when the CEO sat down to write an email, hoping to woo Tiger Global. It was early on in the pandemic, and he...
Login
