We’re a senior US-based product team building clean, scalable platforms for US and Canadian clients. We’re looking for a hybrid full-stack developer who can own features end-to-end — frontend to backend — and help us ship products the right way.

Our Vision

We’re building a tight, high-output team that creates modern, reliable software without bloated processes or corporate noise. The goal is simple: ship clean architecture, scalable systems, and products that clients can actually grow on. We move fast, think long-term, and care about quality.

What You’ll Bring

- Strong communication and independent execution

- Experience with React / Next.js

- Backend experience with Node.js or Django

- Solid understanding of APIs, databases, and scalable systems

- Ability to align with US time zones

If you want to build serious products with serious people, let’s talk.

When a content type has revisioning enabled, edits performed through the Drupal UI correctly create new revisions. However, updates made via the REST API (PATCH/PUT) modify the current revision in place and do not automatically create a new revision, unless explicitly programmed.

This behavior contradicts the intuitive and UI-based expectation that every content modification on a revision-enabled entity results in a new revision, regardless of the update channel.

What do you think, wouldn't the expected behaviour be to create a new revision for revision enabled content on Rest API PATCH request?

Hey folks, I’m a web dev and I built a tiny tool for collecting website feedback directly on the page (click somewhere → leave a comment pinned to that spot).

I’m posting because I’m too close to it and I need honest outside feedback. I’m not trying to market anything — I’m specifically looking for people who’ll try it for 5–10 minutes and tell me what sucks / what’s unclear / what would stop you from using it on a real project.

What I’m hoping to learn:

• Is the value obvious without me explaining it?
• Does it feel smooth or fiddly?
• What’s missing for real client reviews?
• Any trust/privacy red flags at first glance?

If you’re willing, comment “I’ll test” and I’ll DM you a link (or DM me).
And if this kind of post isn’t allowed here, tell me and I’ll remove it right away.

Upgrading to Drupal 2.0 helps organizations modernize their websites with improved performance, stronger security, and better scalability. Older Drupal versions often face compatibility and maintenance challenges, making upgrades necessary for long-term digital growth.

Drupal 2.0 introduces a more flexible architecture, faster loading speeds, and improved integration capabilities with modern applications and cloud environments. It also enhances the content editing experience, allowing teams to manage websites more efficiently.

How the Upgrade Works

• Assess the current Drupal website and modules
• Replace outdated or unsupported components
• Migrate content and configurations
• Update themes for modern UI compatibility
• Test performance and security before launch

Why It Matters

• Improved website performance
• Enhanced security standards
• Easier integrations with third-party systems
• Future-ready and scalable platform

Upgrading to Drupal 2.0 ensures your digital platform remains secure, efficient, and capable of supporting evolving business needs.

Hi folks,

I’m currently exploring Drupal CMS 2.0 and would like to understand how it compares with the standard Drupal setup.

If you’ve worked with CMS 2.0, could you please share:

• The key differences you noticed compared to standard Drupal
• Pros and cons of using CMS 2.0
• Any challenges or limitations you faced
• Scenarios where CMS 2.0 is a better fit (or not recommended)

I’m trying to evaluate whether CMS 2.0 is suitable for long-term projects, so your real-world experiences and suggestions would be really helpful.

Thanks in advance—looking forward to your thoughts!

I've been away from Drupal too long, sucked into WordPress. My company has an ongoing problem with the org chart - specifically it's advertising. I think I can use Drupal to manage this, but I have a lot of rust and haven't worked intensely with it in years (when 8 was current).

The Database I've sketched out uses a UUID approach to coordinate it's contents with outside databases it must stay in sync with, including the aforementioned WordPress site which I will be getting post information from. I'm trying to keep fields on only one table if feasible.

I'm going to go over some of the structure I designed without considering Drupal as the administrating program, so I am open to letting this change as long as I can get the same end result. Note also that this design is informed by schema.org entries for Medical Organizations - of which my company is one (and a fairly large one)

Everything is an Entity. This is the only table with an autoincrement field. Any entry created on any other table starts with an entity entry. For example, if I'm adding a provider the Entity table holds the mappings to the other databases, the entry name and a schema.org description, the person table contains information about the provider's name (given name, surname, which comes first since we have providers with Asian names, gender, etc), and the provider table contains information on whether they accepting new patients, the URL to their scheduler, their NPI (think social security number for medical professionals).

The provider table also cross-references with locations with additional information about which days the provider is at that location and which one is their primary. Another cross reference is which hospitals they have admission privileges to, and another maps which organizations they belong to. Yet another details their education, and their certifications, and the insurances they accept.

The UUID comes into play because hospitals also have insurance company contracts. So that table needs to be joinable with providers or hospitals.

So when I have an edit view of a provider I want the form to present this information cleanly without the user needing to go through multiple forms

I think Drupal can do this out of the box. If not out of the box I have written modules before, but in that event why use Drupal instead of just standing this up in Laravel or Symfony? I'm looking something that is resilient, but I don't want to spend more than a month on this if I can help it.

Hello,

Working a new Drupal site 11 site. And did some testing. When I embed more than 20 images from the media library in CKEditor field (full html).

All the embedded images are shown in CK editor.
But when I switch to the frontend only the fist 20 images are shown are shown. The other content (text) shows correct but images (after number 20) are stripped from the page (also from the html).

Switched the theme to Olivero (to test if this was theme related) but th same problem occurred. Played somewhat with the CKeditor setting (disabled/enabled html corrections).

Checked the logs (php/mysql/apache / console) but saw no error messages.

Any ideas/suggestions what can cause this?