At the DrupalCon Chicago Nonprofit Summit in March, one breakout session stood out for its practicality: "Simple, Small-Site Features That Can Be Built in Drupal on a Dime."
The premise was simple: meaningful improvement doesn't always require a ground-up rebuild. Whether you're working with a modest budget or planning a larger investment in the future, you can start with small, thoughtful enhancements to the authoring experience to deliver outsized returns at any scale.
For nonprofits and cultural institutions, where teams are often lean, and content responsibilities are distributed, improving how content gets created, managed, and published can have an outsized impact.
Below are some of the standout Drupal modules discussed, along with how they can transform the day-to-day experience for content authors.
Content Governance, Control, and Confidence
Trash
What it does: Adds a "recycle bin" for content instead of permanent deletion.
Why it matters: Content editors are often hesitant to make changes because deletion feels final. It’s like pushing a big red button with no label. Trash introduces a safety net.
Authoring impact:
- Reduces fear of breaking things
- Enables cleaner content management
- Encourages editors to actively maintain content instead of letting it decay (we've all seen that "last updated: 2017" page)
Preview Link
What it does: Generates a shareable preview of unpublished content.
Why it matters: Review cycles can be painful without this. Especially for distributed teams or external stakeholders who somehow always reply, "Can you just send me a screenshot?"
Authoring impact:
- Easy stakeholder review without logins
- Faster approvals
- Less back-and-forth screenshots and PDFs
Access Unpublished
What it does: Allows specific users to view unpublished content.
Why it matters: Not everyone who needs to review content should have full CMS access. Giving everyone equal access is the digital equivalent of handing out master keys at a hotel.
Authoring impact:
- Cleaner permission structures
- More flexible collaboration
- Less over-permissioning of users
Visibility & Insight
Entity Usage
What it does: Shows where content is being used across the site.
Why it matters: One of the biggest fears for editors is: "If I change this, what breaks?" Entity Usage is basically a crystal ball, minus the mystical fog and vague prophecies.
Authoring impact:
- Clear visibility into content relationships
- Safer edits and updates
- Easier cleanup of outdated content
Editoria11y
What it does: Provides real-time accessibility feedback directly in the editing interface.
Why it matters: Accessibility is often treated as a QA step rather than part of authoring; it’s like checking whether the parachute works after you've already jumped.
Authoring impact:
- Empowers non-technical editors to create accessible content
- Reduces reliance on audits to catch issues
- Builds accessibility into everyday workflows
Workflow & Publishing Power
Workflow / Scheduler / Scheduled Transitions
What they do:
- Workflow: Enables structured editorial workflows (Draft → Review → Published, etc.)
- Scheduler: Allows content to be published/unpublished at specific times
- Scheduled Transitions: Automates state changes within workflows
Why they matter (together): These modules transform Drupal from a content repository into a true publishing platform. Think of them as the editorial dream team. Workflow sets the rules, Scheduler watches the clock, and Scheduled Transitions does the heavy lifting while you're asleep.
Authoring impact:
- Clear editorial processes
- Reduced manual publishing tasks
- Better coordination for campaigns, events, and announcements
ECA (Event, Condition, Action)
What it does: A no-code automation engine for Drupal.
Why it matters: Think "if this, then that" for your CMS. Or if you prefer: "if content editor does thing, then good stuff happens automatically, and nobody has to file a dev ticket."
Authoring impact:
- Automates repetitive tasks
- Reduces reliance on developers for small logic changes
- Enables powerful workflows without custom code
Content Modeling & Reuse
ECK (Entity Construction Kit)
What it does: Allows custom entity types without heavy development.
Why it matters: Not everything fits neatly into nodes. Reality is messy. ECK embraces that.
Authoring impact:
- More flexible content structures
- Better alignment with real-world content types
- Cleaner admin experiences for complex data
Domain Access
What it does: Supports multi-site management from a single Drupal install.
Why it matters: Managing multiple sites shouldn't mean duplicating work. One ring to rule them all, essentially, but for websites, and with far less dark magic.
Authoring impact:
- Centralized content management
- Easier governance across sites
- Streamlined editorial workflows
Permissions Without Pain
TAC Lite
What it does: Simple taxonomy-based access control.
Why it matters: Permissions in Drupal can get complicated fast if you’re not careful. TAC Lite is the bouncer that makes sure editors only get into the rooms they're supposed to be in.
Authoring impact:
- Editors only see what's relevant to them
- Cleaner, more intuitive admin experience
- Reduces accidental edits
Flexible Enhancements (Use with Care)
CSS Injector / JS Injector
What it does: Allows admins to add custom CSS or JS without deployment.
Why it matters: Quick fixes without waiting on dev cycles. Beautiful in theory, occasionally chaotic in practice.
Authoring impact:
- Faster iteration
- Immediate tweaks
Caution: As a wise uncle once told a certain web-slinging superhero, "With great power comes great responsibility." CSS/JS Injector is powerful, and if it’s ungoverned, it can turn into a Wild West of inline styles and rogue scripts. Set some ground rules before handing out the keys.
Forms & Engagement
Webform
What it does: Powerful form builder for everything from contact forms to grant applications.
Why it matters: Forms are mission-critical for nonprofits. Webform is the Swiss Army knife of the Drupal ecosystem, and it does everything short of making coffee.
Authoring impact:
- Non-technical users can build complex forms
- Reduces dev dependency
- Supports integrations and workflows
Development & Testing Helpers
Devel Generate
What it does: Generates dummy content.
Why it matters: Not directly for authors, but critical for building better authoring experiences. Someone has to fill those content fields with something other than "Lorem ipsum dolor sit amet" for the 400th time.
Authoring impact (indirect):
- Enables realistic testing environments
- Helps teams design better content structures
Drupal + CRM (Drupal CRM Initiative)
What it is: A growing initiative to improve CRM capabilities within Drupal.
Why it matters: Nonprofits rely heavily on constituent data, and right now, juggling your CMS and your CRM can feel like spinning plates while riding a unicycle.
Authoring impact:
- Potential for tighter integration between content and audience data
- More personalized content experiences
- Streamlined workflows across marketing and development teams
The Bigger Takeaway
What stood out most from this session wasn't just the modules themselves, but the mindset: Small improvements to authoring experiences drive massive downstream impact.
When authors:
- Feel confident editing content
- Understand how content is used
- Can collaborate easily
- Don't need a developer for every change
You get:
- Better content quality
- Faster publishing cycles
- Stronger governance
- More effective digital experiences
And honestly? Happier people. Turns out no one gets into nonprofit work because they love filing dev tickets. Who knew!?
Now, I know what you might be thinking, "Hanna, you just described a whole toolkit designed to make my life easier and reduce my reliance on agencies." Fair point. I did do that, but getting everything in its right place still takes some expertise, and that's exactly where we come in. Think of us less as gatekeepers and more as the people who hand you the keys to your kingdom and make sure all the locks actually work.
If you’re interested in learning more, I’d love to chat!
