Stories and campaigns your team publishes.
In WordPress, editors build alumni stories, campaign pages and event pages from approved blocks and see the result as they work, on the same brand as the university's main site.
Advancement CMS Comparison
Encompass, formerly iModules, runs alumni sites, email, events and giving in one platform, and in 2026 it changed owners. If you are reviewing where your advancement site lives, compare it with WordPress: a site your team runs, connected to the giving and CRM tools you choose.
Where Advancement Teams Gain Leverage
Encompass puts many advancement tools in one place. WordPress gives your communications team a site it runs, and lets each tool around it be the best fit.
In WordPress, editors build alumni stories, campaign pages and event pages from approved blocks and see the result as they work, on the same brand as the university's main site.
WordPress is open source. Anthology filed for Chapter 11 in September 2025, and since February 2026 Encompass belongs to Encoura. With WordPress, your site's roadmap is not tied to who owns one vendor.
Giving, events, email and your CRM can stay where they are or move to the tools that fit, and connect to the site. You decide each one, instead of buying them as one bundle.
Deep Dive
| WordPress | Anthology Encompass | |
|---|---|---|
|
Platform
|
||
|
Owner
Who controls the product.
|
Open source (GPL)
|
Encoura, since February 2026
|
|
Scope
What the platform covers.
|
Website, connected to your other tools
|
Website, email, events, giving in one suite
|
|
License
What you pay to run the software.
|
No license fee
|
Suite license, per vendor terms
|
|
Editorial experience
|
||
|
Page building
How a new page gets made.
|
Editors assemble approved blocks
|
Templates and content blocks in the suite
|
|
Brand fit
Matching the university’s main site.
|
Same design system as the main site
|
Within the suite’s templates
|
|
Editing interface
What editors work in.
|
Visual block editor
|
Suite editor with Blueprints templates
|
|
Editorial roles
Who can edit and publish each section.
|
|
Suite permissions
|
|
Ecosystem
|
||
|
Giving and events
Forms people pay or register with.
|
The tools you choose, connected
|
Built in
|
|
CRM connection
Sync with Raiser’s Edge, Salesforce and others.
|
Through the tool you choose
|
Built-in integrations
|
|
Talent availability
Hiring and partner options.
|
Largest pool (39.5% of websites, W3Techs)
|
Specialist pool
|
|
Cost of ownership
|
||
|
Changing one tool
What happens when a piece stops fitting.
|
Replace that tool only
|
Within what the suite supports
|
|
Structured data for AI
Content AI assistants can read and cite.
|
Schema in the content model
|
Depends on the templates
|
Chosen by Teams That Need Autonomy
40Q implements enterprise WordPress so communications teams publish on their own, governance holds, and the platform keeps up with the institution.
Higher education example
Northeastern University School of Law ran its sites on different frameworks, and every campaign waited on engineering.
40Q rebuilt the university’s own UI framework as a WordPress theme, so the communications team now launches on-brand pages on its own.
What Changes After the Switch
Alumni stories, campaign pages and event pages go live when the communications team is ready, without waiting on a vendor or a developer.
Alumni stories, campaign pages and event pages go live when the communications team is ready, without waiting on a vendor or a developer.
Leaving iModules
Three steps: a full crawl, content inventory and URL map first, a parallel build while Encompass stays live, then cutover with rollback ready.
Decision Clarity
Moving an advancement site affects your communications team, your giving pages and your search traffic. These are the questions teams ask before deciding.
Reviewing your advancement platform?
In 30 minutes an engineer looks at your Encompass site and tells you what moving it would involve, and what can stay where it is.