Compliance with the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), is a mandatory legal obligation for covered businesses, with significantly increased financial and operational risks starting in 2025.

The Critical Risk: Escalating Fines and Penalties

As of January 1, 2025, the California Privacy Protection Agency (CPPA) increased monetary thresholds and fines to align with the Consumer Price Index.

Key Deadlines and New Requirements (2026–2028)

Regulators have moved from a passive to an active enforcement model, removing the mandatory “grace period” for fixing violations before penalties are applied.

Website CCPA Readiness Checklist

Does This Apply to My Business?

A for-profit business must comply if it does business in California and meets any of the following:

Operational Impact of Non-Compliance

Beyond fines, non-compliance can lead to court-ordered injunctions, mandatory regular audits, and the required deletion of valuable data assets. It also risks significant reputational damage and customer churn, as modern consumers increasingly prioritize data security when choosing where to spend.

Is your website ready for California’s evolving privacy standards? Non-compliance isn’t just a legal risk — it’s a business one that can result in millions in fines, mandatory audits, and lasting reputational damage. Our team helps organizations like yours navigate complex regulatory requirements with confidence, so you can focus on what matters most. Talk to our team today.

Selecting a content management system in healthcare is no longer a purely technical decision. In today’s environment, a CMS directly impacts compliance, accessibility, speed to publish, and ultimately, trust. Healthcare organizations are under growing pressure to deliver accurate, timely information across multiple digital channels, while meeting strict regulatory and accessibility requirements. The CMS at the center of that effort needs to support far more than page updates.

Why Healthcare CMS Decisions Are Uniquely Complex

Healthcare websites serve a wide range of audiences, from patients and caregivers to providers, partners, and regulators. Content must be clear, accurate, and easy to update—often by multiple teams—without introducing risk.

At the same time, healthcare organizations face constraints that many other industries don’t. Accessibility standards, privacy expectations, and governance requirements are non-negotiable.

A CMS that lacks flexibility or control quickly becomes a bottleneck.

“The healthcare content management system market is projected to grow to over $61 billion by 2031, underscoring how healthcare organizations are prioritizing modern, scalable digital platforms to support compliance, multi-channel delivery, and governance.”

According to Mordor Intelligence

What Healthcare Teams Should Prioritize

Flexibility Without Compromising Security

Healthcare organizations often rely on complex digital ecosystems, including EHRs, portals, analytics tools, and consent platforms. A modern CMS should integrate cleanly with these systems rather than trying to replace them.

Flexibility matters, but not at the expense of security. The right CMS supports modular integration while keeping sensitive data protected and clearly separated from content operations.

Planning For Change, Not Just Launch

CMS selection shouldn’t be based solely on current needs. Healthcare regulations, digital expectations, and technologies continue to evolve. The most effective platforms are designed to adapt without requiring frequent replatforming.

This means supporting incremental improvements, phased rollouts, and long-term scalability—so teams can modernize at a pace that aligns with organizational priorities.

The Role Of Modern, Composable CMS Platforms

Composable CMS platforms are gaining traction in healthcare because they treat content as structured data rather than static pages. This approach supports reuse, consistency, and omnichannel delivery while maintaining governance.

For healthcare teams, this translates into faster publishing, fewer bottlenecks, and greater confidence in content accuracy without sacrificing compliance.

What This Means For Healthcare Teams

Healthcare CMS selection is about more than choosing a tool. It’s about enabling teams to communicate clearly, operate efficiently, and adapt responsibly in a complex digital landscape.

Organizations that prioritize governance, accessibility, and flexibility position themselves to deliver trusted digital experiences today and in the years ahead.

Ready to Evaluate Your Healthcare CMS? Our team helps healthcare organizations navigate complex CMS decisions with a focus on governance, accessibility, and long-term scalability. Let’s talk about what the right platform looks like for your organization.

Contentful is no longer just an alternative CMS—it’s become a foundational platform for organizations navigating complexity, regulation, and rapid digital change. In 2026, the question isn’t what is Contentful? It’s why are so many organizations rebuilding their digital ecosystems around it? The answer lies in how digital experiences are built, managed, and scaled today.

Contentful Is Built for Systems, Not Pages

Traditional CMS platforms were designed around pages and templates. That model breaks down when content needs to move faster, live in more places, and remain consistent across teams and channels.

Contentful takes a different approach. It treats content as structured data, not static pages. That means teams create content once and deliver it anywhere—websites, apps, portals, email, or future channels that don’t yet exist.

In 2026, this isn’t a “nice to have.” It’s how modern digital platforms operate.

Composable Architecture Is Now the Default

Composable architecture has moved from trend to standard. Organizations want the freedom to choose best-in-class tools without being locked into monolithic platforms.

Contentful fits cleanly into this model. It integrates with design systems, analytics platforms, personalization tools, consent managers, and AI services through APIs—without forcing teams into rigid workflows.

This flexibility allows organizations to evolve their stack over time instead of rebuilding every few years.

AI Depends on Structured Content

AI-driven experiences are only as good as the content behind them. In 2026, organizations are using AI to support personalization, search, localization, content optimization, and automation.

Contentful’s structured content model makes this possible. Clean, well-defined content enables AI tools to understand, reuse, and adapt content accurately—without introducing risk or inconsistency.

For teams exploring AI responsibly, Contentful provides the infrastructure needed to scale with confidence.

Governance and Compliance Are Built In, Not Bolted On

For regulated and mission-driven organizations, governance isn’t optional. Publishing controls, audit trails, permissions, and review workflows are essential.

Contentful supports these needs at scale. Teams can define roles, control who edits or publishes content, and maintain visibility into changes across environments. This level of governance is critical in industries like healthcare, legal, finance, and the public sector.

In 2026, compliance isn’t something teams add later—it’s designed into the platform from day one.

Marketing and Development Work Better Together

One of Contentful’s biggest advantages is how it aligns marketing and engineering teams. Developers maintain design systems and integrations. Content teams manage content without breaking layouts or workflows.

This separation of concerns reduces friction, speeds up delivery, and minimizes production errors—especially as digital ecosystems grow more complex.

Ready to explore what Contentful could do for your organization? Whether you’re evaluating platforms, planning a migration, or looking to optimize your current setup, Oomph can help you build a content infrastructure designed for the long term. Let’s talk about your next move.

Why Organizations Move to Contentful Now

Organizations typically migrate to Contentful when legacy systems start holding them back. Common triggers include:

In 2026, Contentful isn’t chosen because it’s new. It’s chosen because it’s resilient.

For organizations new to the platform, getting started doesn’t have to mean a complete rebuild. Oomph’s Contentful Kickstart Package helps teams move from decision to deployment with a structured, low-risk approach—giving you the foundation to scale as your needs evolve.

The Takeaway

Contentful has evolved alongside the modern digital landscape. It’s not just a CMS—it’s a content platform designed for scale, governance, and change.

For organizations planning beyond their next website launch and toward long-term digital maturity, Contentful provides the flexibility and confidence needed to move forward.

Ready to explore what Contentful could do for your organization? Whether you’re evaluating platforms, planning a migration, or looking to optimize your current setup, Oomph can help you build a content infrastructure designed for the long term. Let’s talk about your next move.

For many organizations, privacy regulations like GDPR and CCPA seem like distant legal concerns rather than operational priorities. In practice, however, websites serve as the primary point of data collection—making compliance far more relevant than most teams assume. If your site collects user data in any form, privacy compliance isn’t optional.

Understanding When GDPR and CCPA Apply

GDPR governs the collection of personal data from users in the European Union, while CCPA applies to personal data collected from California residents.

Crucially, these regulations are triggered by user location, not company headquarters. A U.S.-based organization serving a global audience may be subject to both frameworks.

Why Websites Are at the Center of Compliance

Most modern websites collect data through multiple channels:

Each of these collection points creates compliance obligations around consent, transparency, and user control.

Moving Beyond Cookie Banners

Meaningful compliance extends well beyond footer disclaimers. Effective privacy management requires:

Legacy CMS platforms frequently lack the flexibility and governance capabilities needed to meet these requirements.

The Role of Your CMS in Privacy Compliance

Your content management system is instrumental in supporting privacy obligations. A modern, composable CMS enables organizations to:

For regulated and mission-driven organizations, CMS limitations can translate directly into compliance vulnerabilities.

The Cost of Non-Compliance

While regulatory penalties are a concern, the greater risk lies in eroding user trust.

Today’s users expect transparency and control over their personal information. Organizations unable to deliver on these expectations risk damaging their reputation with customers, donors, and partners.

Final Thoughts

GDPR and CCPA represent more than legal obligations—they present fundamental digital experience challenges. Websites built on flexible, compliance-ready platforms are better positioned to adapt as privacy expectations continue to evolve.

In today’s environment, privacy compliance shouldn’t be viewed as a constraint. It’s an essential component of delivering a modern, trustworthy digital experience.

Need help ensuring your website meets modern privacy standards? Our team specializes in building compliance-ready digital platforms that protect your users and your organization. Let’s discuss your requirements.

When you’re responsible for your organization’s digital presence, it’s natural to focus on what’s visible: the design, the content, the user experience. But beneath every modern website lies a complex ecosystem of technologies, integrations, and workflows that can either accelerate your team’s success or create hidden friction that slows everything down.

That’s where a technical audit becomes invaluable. It’s not just a diagnostic tool—it’s a strategic opportunity to understand the foundation of your platform and make informed decisions about your digital future.

It’s Like a Home Inspection for Your Website

Think about buying a house. You walk through focusing on the big picture—does the kitchen work for your family? Is there enough space? But a good home inspector looks deeper, checking the foundation, examining the electrical system, and spotting that small leak under the bathroom sink that could become a major problem later.

A technical audit takes the same comprehensive approach to your digital platform. We examine not just what’s working today, but what might impact your team’s ability to execute tomorrow. The goal isn’t to find problems for the sake of finding them—it’s to give you the complete picture you need to plan strategically.

Creating Shared Understanding Across Your Entire Team

One of the most powerful outcomes of a technical audit is alignment. Whether you’re managing internal developers, partnering with an agency, or preparing to issue an RFP, having a clear baseline allows everyone to ask better questions and make more accurate decisions.

A strategic technical audit delivers:

Proactive Problem-Solving: Surface technical issues before they become roadblocks to important campaigns or launches.

Performance Optimization: Identify specific improvements that will measurably enhance user experience and conversion rates.

Workflow Enhancement: Reveal friction points that slow down content updates, campaign launches, or day-to-day management tasks.

Vendor Enablement: Provide partners and potential vendors with the context they need to scope work accurately and ask intelligent questions.

Strategic Planning: Create a foundation for long-term digital strategy decisions, from infrastructure investments to editorial tooling.

The organizations we work with often tell us that a technical audit helped them transition from reactive maintenance to proactive digital platform management—a shift that pays dividends across every initiative.

What We Typically Discover

While every platform is unique, certain patterns emerge across industries and organization types. Technical audits frequently reveal:

Security and Maintenance Opportunities: Outdated software, plugins requiring updates, or access configurations that can be strengthened with minimal effort. This often includes ensuring accessibility compliance meets current standards.

Performance Enhancements: Specific optimizations in areas like image compression, caching strategies, or database queries that directly impact user experience. Modern audits also examine search visibility and performance optimization.

Scalability Considerations: Code or architectural decisions that work fine today but could limit growth or flexibility as your needs evolve. This includes evaluating search infrastructure and international expansion capabilities.

Process Improvements: Gaps in version control, deployment workflows, or change management that create unnecessary risk or slow down development cycles.

Editorial Workflow Optimization: Content management processes that feel cumbersome or inconsistent, often because they evolved organically rather than being designed strategically. For global organizations, this includes reviewing translation and localization systems.

Many of these findings aren’t urgent fixes—they’re strategic insights that become incredibly valuable when you’re planning a redesign, launching a major campaign, or evaluating new partnerships.

When a Technical Audit Delivers Maximum Value

You don’t need to wait for problems to emerge. Technical audits are particularly valuable when:

Taking Over Digital Responsibility: You’ve inherited a platform and need a comprehensive understanding of what you’re working with and where the opportunities lie.

Planning Major Initiatives: Before investing in a redesign, platform migration, or significant feature development, understanding your current foundation prevents costly surprises.

Preparing for Vendor Selection: Whether you’re issuing an RFP or evaluating agencies, giving potential partners accurate technical context leads to better proposals and more realistic timelines.

Developing Digital Strategy: When you’re ready to create a roadmap for digital growth, grounding decisions in technical reality rather than assumptions leads to better outcomes. This is especially important when considering AI integration or generative engine optimization strategies.

Our Approach to Technical Audits

We design our audits to build clarity and confidence, not overwhelm you with technical jargon. Rather than simply delivering a report, we walk through findings with your team, prioritize recommendations based on your specific goals, and translate technical insights into actionable business language you can share with stakeholders.

Our methodology goes beyond code analysis. We examine how your platform supports your current workflows, aligns with your organizational objectives, and positions you for future growth. This combination of technical depth and strategic perspective ensures you get insights that drive real business outcomes.

The audit process focuses on partnership, not judgment.

We’re not looking for flaws to criticize—we’re identifying opportunities to help you and your partners make smarter decisions. The result is visibility into the hidden layers of your digital platform and a foundation for more strategic planning, better technology investments, and sustainable long-term success.

Ready to understand what’s really happening under the hood of your digital platform? Let’s talk about how a technical audit could support your goals and strengthen your team’s ability to execute on your digital vision.

If your Drupal site relies on Acquia Search leveraging Solr, you’re likely facing a migration from Acquia Search to SearchStax. We’ve guided numerous organizations through this transition and want to share our proven approach to help you navigate this change successfully.

Before diving into the migration process, this transition presents an excellent opportunity to reassess your search strategy entirely. While Solr remains a powerful and robust solution, the search landscape has evolved significantly with innovative alternatives now available. For organizations considering broader platform transitions, this moment offers strategic value beyond search improvements. Modern React-based solutions can deliver dramatically faster user experiences. Our recent work with ONS demonstrates this potential—by replacing their Solr solution with Algolia Instant Search, we helped them achieve a 40% improvement in search response times while creating a more intuitive experience for their members.

Why the Move to SearchStax?

Acquia announced earlier this year that they’re sunsetting their Acquia Search offering in 2026, positioning SearchStax as the recommended migration path through their new partnership. This transition offers enhanced search capabilities and more direct control over your search environment through SearchStax’s comprehensive dashboard, providing visibility into Solr server performance, data analysis tools, search preview functionality, and advanced configuration options.

The architectural similarity ensures a seamless end-user experience—Solr remains the foundation, requiring no front-end changes for this migration path while delivering improved administrative control.

Our Proven Migration Framework

Through multiple successful migrations, we’ve developed a structured approach that minimizes risk and ensures smooth transitions. Here’s our step-by-step framework:

Phase 1: Foundation Setup

Phase 2: Testing and Validation

Phase 3: Production Implementation

Phase 4: Configuration Management

Phase 5: Transition Management

Addressing Technical Challenges

Our experience across multiple migrations has revealed common technical hurdles that require proactive attention. Configuration issues with Boost by Date Processor settings, Highlighted Fields errors during index rebuilding, and Facet configuration mismatches between environments are frequent challenges. The key to success lies in early identification during lower environment testing and leveraging Acquia support resources to resolve issues before they impact production.

Each migration presents unique challenges based on your specific configuration and content structure. Our approach prioritizes thorough testing and validation to surface these issues early, ensuring smooth production deployment.

Strategic Search Optimization

Successful migration extends beyond technical implementation. Understanding your content architecture, user behavior patterns, and business objectives enables you to optimize search effectiveness during the transition. This migration provides an ideal opportunity to evaluate search performance metrics, refine content indexing strategies, and enhance user experience design.

By following this proven framework and preparing for potential challenges, your organization can successfully transition to SearchStax while improving both administrative capabilities and user search experience. The result is a more robust, manageable search solution that positions your site for future growth and enhanced user engagement.

Our comprehensive migration expertise extends beyond search implementations to complete platform transformations, ensuring your digital infrastructure supports your long-term strategic objectives.

Ready to begin your SearchStax migration? Don’t wait until the 2026 deadline creates a migration rush. Our fixed-price SearchStax migration service ($2,500) provides the structured, proven approach outlined in this guide—from foundation setup through transition management. Get started with your SearchStax migration today.

The U.S. is one of the most linguistically diverse countries in the world. While English may be our official language, the number of people who speak a language other than English at home has actually tripled over the past three decades. 

Statistically speaking, the people you serve are probably among them. 

You might even know they are. Maybe you’ve noticed an uptick in inquiries from non-English speaking people or tracked demographic changes in your analytics. Either way, chances are good that organizations of all kinds will see more, not less, need for translation — especially those in highly regulated and far-reaching industries, like higher education and healthcare.

So, what do you do when translation becomes a top priority for your organization? Here, we explain how to get started.

3 Solutions for Translating Your Website

Many organizations have an a-ha moment when it comes to translations. For our client Lifespan, that moment came during its rebrand to Brown Health University and a growing audience of non-English speaking people. For another client, Visit California, that moment came when developing their marketing strategies for key global audiences. 

Or maybe you’re more like Leica Geosystems, a longtime Oomph client that prioritized translation from the start but needed the right technology to support it. 

Whenever the time comes, you have three main options: 

Manual translation and publishing

When most people think of translating, manual translation comes to mind. In this scenario, someone on your team or someone you hire translates content by hand and uploads the translation as a separate page to the content management system (CMS).

Translating manually will offer you higher quality and more direct control over the content. You’ll also be able to optimize translations for SEO; manual translation is one of the best ways to ensure the right pages are indexed and findable in every language you offer them. Manual translation also has fewer ongoing technical fees and long-term maintenance attached, especially if you use a CMS like Drupal which supports translations by default.

“Drupal comes multi-lingual out of the box, so it’s very easy for editors to publish translations of their site and metadata,” Oomph Senior UX Engineer Kyle Davis says. “Other platforms aren’t going to be as good at that.” 

While manual translation may sound like a winning formula, it can also come at a high cost, pushing it out of reach for smaller organizations or those who can’t allocate a large portion of their budget to translate their website and other materials. 

Integration with a real-time API

Ever seen a website with clickable international flags near the top of the page? That’s a translation API. These machine translation tools can translate content in the blink of an eye, helping users of many different languages access your site in their chosen language. 

“This is different than manual translation, because you aren’t optimizing your content in any way,” Oomph Senior UX Engineer John Cionci says. “You’re simply putting a widget on your page.” 

Despite their plug-and-play reputation, machine translation APIs can actually be fairly curated. Customization and localization options allow you to override certain phrases to make your translations appropriate for a native speaker. This functionality would serve you well if, like Visit California, you have a team to ensure the translation is just right. 

Though APIs are efficient, they also do not take SEO or user experience into account. You’re getting a direct real-time translation of your content, nothing more and nothing less. This might be enough if all you need is a default version of a page in a language other than English; by translating that page, you’re already making it more accessible. 

However, this won’t always cut it if your goal is to create more immersive, branded experiences — experiences your non-English-speaking audience deserves. Some translation API solutions also aren’t as easy to install and configure as they used to be. While the overall cost may be less than manual translation, you’ll also have an upfront development investment and ongoing maintenance to consider. 

Use Case: Visit California

Manual translation doesn’t have to be all or nothing. Visit California has international marketing teams in key markets skilled in their target audiences’ primary languages, enabling them to blend manual and machine translation. 

We worked with Visit California to implement machine translation (think Google Translate) to do the heavy lifting. After a translation is complete, their team comes in to verify that all translated content is accurate and represents their brand. Leveraging the glossary overrides feature of Google Cloud Translate V3, they can tailor the translations to their communication objectives for each region. In addition, their Drupal CMS still allows them to publish manual translations when needed. This hybrid approach has proven to be very effective.

Third-party translation services

The adage “You get what you pay for” rings true for translation services. While third-party translation services cost more than APIs, they also come with higher quality — an investment that can be well worth it for organizations with large non-English-speaking audiences.

Most translation services will provide you with custom code, cutting down on implementation time. While you’ll have little to no technical debt, you will have to keep on top of recurring subscription fees.

What does that get you? If you use a proxy-based solution like MotionPoint, you can expect to have content pulled from your live site, then freshly translated and populated on a unique domain. 

“Because you can serve up content in different languages with unique domains, you get multilingual results indexed on Google and can be discovered,” Oomph Senior Digital Project Manager Julie Elman says. 

Solutions like Ray Enterprise Translation, on the other hand, combine an API with human translation, making it easier to manage, override, moderate, and store translations all within your CMS. 

Use Case: Leica Geosystems

Leica’s Drupal e-commerce store is active in multiple countries and languages, making it difficult to manage ever-changing products, content, and prices. Oomph helped Leica migrate to a single-site model during their migration from Drupal 7 to 8 back in 2019. 

“Oomph has been integral in providing a translation solution that can accommodate content generation in all languages available on our website,” says Jeannie Records Boyle, Leica’s e-Commerce Translation Manager. 

This meant all content had one place to live and could be translated into all supported languages using the Ray Enterprise Translation integration (formerly Lingotek). Authors could then choose which countries the content should be available in, making it easier to author engaging and accurate content that resonates around the world.  

“Whether we spin up a new blog or product page in English or Japanese, for example, we can then translate it to the many other languages we offer, including German, Spanish, Norwegian Bokmål, Dutch, Brazil Portuguese, Italian, and French,” Records Boyle says.

Taking a Strategic Approach to Translation

Translation can be as simple as the click of a button. However, effective translation that supports your business goals is more complex. It requires that you understand who your target audiences are, the languages they speak, and how to structure that content in relation to the English content you already have. 

The other truth about translation is that there is no one-size-fits-all option. The “right” solution depends on your budget, in-house skills, CMS, and myriad other factors — all of which can be tricky to weigh. 

Here at Oomph, we’ve helped many clients make their way through website translation projects big and small. We’re all about facilitating translations that work for your organization, your content admins, and your audience — because we believe in making the Web as accessible as possible for all. 

Want to see a few recent examples or dive deeper into your own website translation project? Let’s talk. 

Oomph has been quiet about our excitement for artificial intelligence (A.I.). While the tech world has exploded with new A.I. products, offerings, and add-ons to existing product suites, we have been formulating an approach to recommend A.I.-related services to our clients. 

One of the biggest reasons why we have been quiet is the complexity and the fast-pace of change in the landscape. Giant companies have been trying A.I. with some loud public failures. The investment and venture capitalist community is hyped on A.I. but has recently become cautious as productivity and profit have not been boosted. It is a familiar boom-then-bust of attention that we have seen before — most recently with AR/VR after the Apple Vision Pro five months ago and previously with the Metaverse, Blockchain/NFTs, and Bitcoin. 

There are many reasons to be optimistic about applications for A.I. in business. And there continue to be many reasons to be cautious as well. Just like any digital tool, A.I. has pros and cons and Oomph has carefully evaluated each. We are sharing our internal thoughts in the hopes that your business can use the same criteria when considering a potential investment in A.I. 

Using A.I.: Not If, but How

Most digital tools now have some kind of A.I. or machine-learning built into them. A.I. has become ubiquitous and embedded in many systems we use every day. Given investor hype for companies that are leveraging A.I., more and more tools are likely to incorporate A.I.

This is not a new phenomenon. Grammarly has been around since 2015 and by many measures, it is an A.I. tool — it is trained on human written language to provide contextual corrections and suggestions for improvements.

Recently, though, embedded A.I. has exploded across markets. Many of the tools Oomph team members use every day have A.I. embedded in them, across sales, design, engineering, and project management — from Google Suite and Zoom to Github and Figma.

The market has already decided that business customers want access to time-saving A.I. tools. Some welcome these options, and others will use them reluctantly.

Either way, the question has very quickly moved from should our business use A.I. to how can our business use A.I. tools responsibly?

The Risks that A.I. Pose

Every technological breakthrough comes with risks. Some pundits (both for and against A.I. advancements) have likened its emergence to the Industrial Revolution of the early 20th century. And a high-level of positive significance is possible, while the cultural, societal, and environmental repercussions could also follow a similar trajectory.

A.I. has its downsides. When evaluating A.I. tools as a solution to our client’s problems, we keep this list of drawbacks and negative effects handy, so that we may review it and think about how to mitigate their negative effects:

We have also found that our company values are a lens through which we can evaluate new technology and any proposed solutions. Oomph has three cultural values that form the center of our approach and our mission, and we add our stated 1% For the Planet commitment to that list as well: 

For each of A.I.’s drawbacks, we use the lens of our cultural values to guide our approach to evaluating and mitigating those potential ill effects. 

A.I. is built upon biased and flawed data

At its core, A.I. is built upon terabytes of data and billions, if not trillions, of individual pieces of content. Training data for Large Language Models (LLMs) like Chat GPT, Llama, and Claude encompass mostly public content as well as special subscriptions through relationships with data providers like the New York Times and Reddit. Image generation tools like Midjourney and Adobe Firefly require billions of images to train them and have skirted similar copyright issues while gobbling up as much free public data as they can find. 

Because LLMs require such a massive amount of data, it is impossible to curate those data sets to only what we may deem as “true” facts or the “perfect” images. Even if we were able to curate these training sets, who makes the determination of what to include or exclude?

The training data would need to be free of bias and free of sarcasm (a very human trait) for it to be reliable and useful. We’ve seen this play out with sometimes hilarious results. Google “A.I. Overviews” have told people to put glue on pizza to prevent the cheese from sliding off or to eat one rock a day for vitamins & minerals. Researchers and journalists traced these suggestions back to the training data from Reddit and The Onion.

Information architects have a saying: “All Data is Dirty.” It means no one creates “perfect” data, where every entry is reviewed, cross-checked for accuracy, and evaluated by a shared set of objective standards. Human bias and accidents always enter the data. Even the simple act of deciding what data to include (and therefore, which data is excluded) is bias. All data is dirty.

Bias & flawed data leads to the perpetuation of stereotypes

Many of the drawbacks of A.I. are interrelated — All data is dirty is related to D.E.I. Gender and racial biases surface in the answers A.I. provides. A.I. will perpetuate the harms that these biases produce as they become easier and easier to use and more and more prevalent. These harms are ones which society is only recently grappling with in a deep and meaningful way, and A.I. could roll back much of our progress.

We’ve seen this start to happen. Early reports from image creation tools discuss a European white male bias inherent in these tools — ask it to generate an image of someone in a specific occupation, and receive many white males in the results, unless that occupation is stereotypically “women’s work.” When AI is used to perform HR tasks, the software often advances those it perceives as males more quickly, and penalizes applications that contain female names and pronouns.

The bias is in the data and very, very difficult to remove. The entirety of digital written language over-indexes privileged white Europeans who can afford the tools to become authors. This comparably small pool of participants is also dominantly male, and the content they have created emphasizes white male perspectives. To curate bias out of the training data and create an equally representative pool is nearly impossible, especially when you consider the exponentially larger and larger sets of data new LLM models require for training.

Further, D.E.I. overflows into environmental impact. Last fall, the Fifth National Climate Assessment outlined the country’s climate status. Not only is the U.S. warming faster than the rest of the world, but they directly linked reductions in greenhouse gas emissions with reducing racial disparities. Climate impacts are felt most heavily in communities of color and low incomes, therefore, climate justice and racial justice are directly related.

Flawed data leads to “Hallucinations” & harms Brands

“Brand Safety” and How A.I. can harm Brands

Brand safety is the practice of protecting a company’s brand and reputation by monitoring online content related to the brand. This includes content the brand is directly responsible for creating about itself as well as the content created by authorized agents (most typically customer service reps, but now AI systems as well).

The data that comes out of A.I. agents will reflect on the brand employing the agent. A real life example is Air Canada. The A.I. chatbot gave a customer an answer that contradicted the information in the URL it provided. The customer chose to believe the A.I. answer, while the company tried to say that it could not be responsible if the customer didn’t follow the URL to the more authoritative information. In court, the customer won and Air Canada lost, resulting in bad publicity for the company.

Brand safety can also be compromised when a 3rd party feeds A.I. tools proprietary client data. Some terms and condition statements for A.I. tools are murky while others are direct. Midjourney’s terms state,

“By using the Services, You grant to Midjourney […] a perpetual, worldwide, non-exclusive, sublicensable no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute text and image prompts You input into the Services” 

Midjourney’s Terms of Service Statement

That makes it pretty clear that by using Midjourney, you implicitly agree that your data will become part of their system.

The implication that our client’s data might become available to everyone is a huge professional risk that Oomph avoids. Even using ChatGPT to provide content summaries on NDA data can open hidden risks.

What are “Hallucinations” and why do they happen?

It’s important to remember how current A.I. chatbots work. Like a smartphone’s predictive text tool, LLMs form statements by stitching together words, characters, and numbers based on the probability of each unit succeeding the previously generated units. The predictions can be very complex, adhering to grammatical structure and situational context as well as the initial prompt. Given this, they do not truly understand language or context. 

At best, A.I. chatbots are a mirror that reflects how humans sound without a deep understanding of what any of the words mean. 

A.I. systems are trying its best to provide an accurate and truthful answer without a complete understanding of the words it is using. A “hallucination” can occur for a variety of reasons and it is not always possible to trace their origins or reverse-engineer them out of a system. 

As many recent news stories state, hallucinations are a huge problem with A.I. Companies like IBM and McDonald’s can’t get hallucinations under control and have pulled A.I. from their stores because of the headaches they cause. If they can’t make their investments in A.I. pay off, it makes us wonder about the usefulness of A.I. for consumer applications in general. And all of these gaffes hurt consumer’s perception of the brands and the services they provide.

Poor A.I. answers erode Consumer Trust

The aforementioned problems with A.I. are well-known in the tech industry. In the consumer sphere, A.I. has only just started to break into the public consciousness. Consumers are outcome-driven. If A.I. is a tool that can reliably save them time and reduce work, they don’t care how it works, but they do care about its accuracy. 

Consumers are also misinformed or have a very surface level understanding of how A.I. works. In one study, only 30% of people correctly identified six different applications of A.I. People don’t have a complete picture of how pervasive A.I.-powered services already are.

The news media loves a good fail story, and A.I. has been providing plenty of those. With most of the media coverage of A.I. being either fear-mongering (“A.I. will take your job!”) or about hilarious hallucinations (“A.I. suggests you eat rocks!”), consumers will be conditioned to mistrust products and tools labeled “A.I.” 

And for those who have had a first-hand experience with an A.I. tool, a poor A.I. experience makes all A.I. seem poor. 

A.I.’s appetite for electricity is unsustainable

The environmental impact of our digital lives is invisible. Cloud services that store our lifetime of photographs sound like featherly, lightweight repositories that are actually giant, electricity-guzzling warehouses full of heat-producing servers. Cooling these data factories and providing the electricity to run them are a major infrastructure issue cities around the country face. And then A.I. came along.

While difficult to quantify, there are some scientists and journalists studying this issue, and they have found some alarming statistics: 

While the consumption needs are troubling, quickly creating more infrastructure to support these needs is not possible. New energy grids take multiple years and millions if not billions of dollars of investment. Parts of the country are already straining under the weight of our current energy needs and will continue to do so — peak summer demand is projected to grow by 38,000 megawatts nationwide in the next five years. 

While a data center can be built in about a year, it can take five years or longer to connect renewable energy projects to the grid. While most new power projects built in 2024 are clean energy (solar, wind, hydro), they are not being built fast enough. And utilities note that data centers need power 24 hours a day, something most clean sources can’t provide. It should be heartbreaking that carbon-producing fuels like coal and gas are being kept online to support our data needs.

Oomph’s commitment to 1% for the Planet means that we want to design specific uses for A.I. instead of very broad ones. The environmental impact of A.I.’s energy demands is a major factor we consider when deciding how and when to use A.I.

Using our Values to Guide the Evaluation of A.I.

As we previously stated, our company values provide a lens through which we can evaluate A.I. and look to mitigate its negative effects. Many of the solutions cross over and mitigate more than one effect and represent a shared commitment to extracting the best results from any tool in our set

Smart

Driven

Personal

1% for the Planet

In Summary

While this article feels like we are strongly anti-A.I., we still have optimism and excitement about how A.I. systems can be used to augment and support human effort. Tools created with A.I. can make tasks and interactions more efficient, can help non-creatives jumpstart their creativity, and can eventually become agents that assist with complex tasks that are draining and unfulfilling for humans to perform. 

For consumers or our clients to trust A.I., however, we need to provide ethical evaluation criteria. We can not use A.I. as a solve-all tool when it has clearly displayed limitations. We aim to continue to learn from others, experiment ourselves, and evaluate appropriate uses for A.I. with a clear set of criteria that align with our company culture. 

To have a conversation about how your company might want to leverage A.I. responsibly, please contact us anytime.

Additional Reading List

If you’ve been following along, Drupal 11 was set to be released during one of two windows in 2024 — either in July or later in the year in December — and a stable Drupal 11 release was just tagged earlier on Friday. The buzz is real because this major milestone is the first indicator that the community is on track to set the groundwork for the monumental efforts the Drupal community is rallying around with Drupal Starshot.

What is it?

Drupal 11 builds upon the significant updates that shipped with version 10.3, brings optimizations and the removal of old code, and sets the stage for upcoming releases that will support Drupal Starshot initiatives.

Drupal 10.4 (yet to be released) is being positioned as a long-term support (LTS) release that will continue to be supported until mid-2026, so there’s no urgency to update to Drupal 11 immediately. While in the past, site owners felt some urgency to upgrade as soon as possible, this time around there’s a longer runway before that needs to happen. That being said, sites will need to be upgraded to 10.3 before being updated to Drupal 11, so if you’re not yet on the current version of Drupal 10, that should be your priority.

Chart that outlines the proposed release schedule for Drupal 10, 11, and 12

Slide shared at Drupalcon Portland outlining release plan for v10 support through mid-2026

Why is it important?

Over time software at all points in your technology stack will see updates — at least that is what we hope for! — which means that not only does Drupal get updated, but the technologies that Drupal is built to run on will see updates, too. One of the most important changes with Drupal 11 is the new platform requirements that include updating to PHP 8.3.

PHP 8.3 brings significant performance improvements that will result in a faster Drupal application as well as the opportunity for lower costs to run the application, which means less impact on the environment — a definite win in our book. 

Beyond updates to support the latest and greatest platform versions, other improvements include the removal of some lesser-used core modules and deprecated code—so, some code-level housekeeping. 

Most importantly, the introduction of official LTS releases means that site owners will have a more predictable roadmap for when updates need to happen without feeling like they need to be early adopters when contributed modules may be lagging behind the new core releases.

Why are we excited about it?

With Drupal 11 cementing changes that were introduced with Drupal 10.3.x, updating dependencies, and removing lesser-used features, this release lays the foundation for the Drupal Starshot initiative to build upon and includes Single Directory Components (this provides support for a component-based development approach) and (experimental) Recipes support, which is a Starshot initiative feature that will allow sites to add new complete features to a site through bundled configuration settings.

Oomph has been contributing to the Starshot initiative since it was announced at Drupalcon, and we’re really looking forward to what’s ahead! We’re also thrilled to see Drupal in a position to adopt newer versions of the libraries and packages it depends on because that means streamlined development support and the benefits of the updates and improvements that those communities are making to their software reach us as well.

Drupal 11 Release changes

Notable changes to Drupal 11 include:

See the release notes for full details.

Everyone’s been saying it (and, frankly, we tend to agree):  We are currently in unprecedented times. It may feel like a cliche. But truly, when you stop and look around right now, not since the advent of the first consumer-friendly smartphone in 2008 has the digital web design and development industry seen such vast technological advances.

A few of these innovations have been kicking around for decades, but they’ve only moved into the greater public consciousness in the past year. Versions of artificial intelligence (AI) and chatbots have been around since the 1960s and even virtual reality (VR)/augmented reality (AR) has been attempted with some success since the 1990s (That Starner). But now, these technologies have reached a tipping point as companies join the rush to create new products that leverage AI and VR/AR. 

What should we do with all this change? Let’s think about the immediate future for a moment (not the long-range future, because who knows what that holds). We at Oomph have been thinking about how we can start to use this new technology now — for ourselves and for our clients. Which ideas that seemed far-fetched only a year ago are now possible? 

For this article, we’ll take a closer look at VR/AR, two digital technologies that either layer on top of or fully replace our real world.

VR/AR and the Vision Pro

Apple’s much-anticipated launch into the headset game shipped in early February 2024. With it came much hype, most centered around the price tag and limited ecosystem (for now). But after all the dust has settled, what has this flagship device told us about the future? 

Meta, Oculus, Sony, and others have been in this space since 2017, but the Apple device has debuted a better experience in many respects. For one, Apple nailed the 3D visuals, using many cameras and low latency to reproduce a digital version of the real world around the wearer— in real time. All of this tells us that VR headsets are moving beyond gaming applications and becoming more mainstream for specific types of interactions and experiences, like virtually visiting the Eiffel Tower or watching the upcoming Summer Olympics.

What Is VR/AR Not Good At?

Comfort

Apple’s version of the device is large, uncomfortable, and too heavy to wear for long. And its competitors are not much better. The device will increasingly become smaller and more powerful, but for now, wearing one as an infinite virtual monitor for the entire workday is impossible.

Space

VR generally needs space for the wearer to move around. The Vision Pro is very good at overlaying virtual items into the physical world around the wearer, but for an application that requires the wearer to be fully immersed in a virtual world, it is a poor experience to pantomime moving through a confined space. Immersion is best when the movements required to interact are small or when the wearer has adequate space to participate.

Haptics

“Haptic”  feedback is the sense that physical objects provide. Think about turning a doorknob: You feel the surface, the warmth or coolness of the material, how the object can be rotated (as opposed to pulled like a lever), and the resistance from the springs. 

Phones provide small amounts of haptic feedback in the form of vibrations and sounds. Haptics are on the horizon for many VR platforms but have yet to be built into headset systems. For now, haptics are provided by add-on products like this haptic gaming chair.

What Is VR/AR Good For? 

Even without haptics and free spatial range, immersion and presence in VR is very effective. It turns out that the brain only requires sight and sound to create a believable sense of immersion. Have you tried a virtual roller coaster? If so, you know it doesn’t take much to feel a sense of presence in a virtual environment. 

Live Events

VR and AR’s most promising applications are with live in-person and televised events. In addition to a flat “screen” of the event, AR-generated spatial representations of the event and ways to interact with the event are expanding. A prototype video with Formula 1 racing is a great example of how this application can increase engagement with these events.

Imagine if your next virtual conference were available in VR and AR. How much more immersed would you feel? 

Museum and Cultural Institution Experiences

Similar to live events, AR can enhance museum experiences greatly. With AR, viewers can look at an object in its real space — for example, a sarcophagus would actually appear in a tomb — and access additional information about that object, like the time and place it was created and the artist.

Museums are already experimenting with experiences that leverage your phone’s camera or VR headsets. Some have experimented with virtually showing artwork by the same artist that other museums own to display a wider range of work within an exhibition. 

With the expansion of personal VR equipment like the Vision Pro, the next obvious step is to bring the museum to your living room, much like the National Gallery in London bringing its collection into public spaces (see bullet point #5).

Try Before You Buy (TBYB)

Using a version of AR with your phone to preview furniture in your home is not new. But what other experiences can benefit from an immersive “try before you buy” experience? 

What’s Possible With VR/AR?

The above examples of what VR/AR is good at are just a few ways the technology is already in use — each of which can be a jumping-off point for leveraging VR/AR for your own business.  

But what are some new frontiers that have yet to be fully explored? What else is possible? 

Continue the AR/VR Conversation

The Vision Pro hasn’t taken the world by storm, as Apple likely hoped. It may still be too early for the market to figure out what AR/VR is good for. But we think it won’t go away completely, either. With big investments like Apple’s, it is reasonable to assume the next version will find a stronger foothold in the market.

Here at Oomph, we’ll keep pondering and researching impactful ways that tomorrow’s technology can help solve today’s problems. We hope these ideas have inspired some of your own explorations, and if so, we’d love to hear more about them. 

Drop us a line and let’s chat about how VR/AR could engage your audience. 

A world without third-party cookies is fast approaching. Big-name browsers like Safari and Firefox already block them by default, and Google Chrome —  the biggest browser of them all —  is set to follow. 

First, a quick refresher: Websites use cookies to store data in your browser specific to that website and other sites. The question, though, is who the website is storing the data for. Third-party cookies store data that allows advertising services to track your behavior on any given site, while first-party cookies are those a website uses for its own purposes. 

Like most things, not all cookies are created equal. As browsers transition to these new defaults, some will make the grade, while others will be blocked for good. What does this mean for your website, and how can you get ahead of the change? We’ll walk you through it. 

Are Cookies Really Going Away? 

That depends on the type of cookies your site uses. Browsers are slowly blocking third-party cookies by default — those associated with cross-site tracking for ad networks like Facebook or LinkedIn — but first-site, or same-site, cookies will remain. 

That means that if retargeting is essential to your paid marketing strategy, you may need to rethink your approach. But any cookies you use to support your site features and functionality can keep on keeping on, assuming your users have agreed to the use of those cookies on your site. For example, you may be able to keep track of previously viewed content and use that information to suggest other relevant content to that user. So don’t say goodbye to your cookie consent services either; you still have to give users the chance to opt out of any first-party cookies. 

Why Now? Haven’t We Been Using Cookies Forever? 

While cookies have been a web-surfing staple for almost as long as we’ve been using the internet, that’s not necessarily a good thing. 

Legislation like GDPR in Europe, the California Consumer Privacy Act, and the New York Privacy Act are tightening restrictions on the use of consumer data, and rapidly increasing cybersecurity threats in recent years have illuminated the risks of large-scale data storage. Consumers have also begun to prize their privacy, realizing that their information is valuable and no organization should be looking over their shoulder as they browse. 

Ultimately, phasing out third-party cookies is about doing what’s best for your users. Making the move now can help instill trust in your website, since users know you aren’t capturing their data behind the scenes. Cookie consent forms also put the data you do use out in the open, showing users that your organization takes their privacy seriously and is prepared to protect it. 

How Will The End of Third-Party Cookies Impact My Industry? 

Not all organizations will feel the shift equally. We’ve seen some verticals get ahead of the curve, while others are naturally less reliant on third-party cookies. Here are some key industry-specific areas to consider. 

Healthcare

Strict privacy laws and regulations like the Health Insurance Portability and Accountability Act (HIPAA) have turned healthcare organizations into pioneers in this area. The Office of Civil Rights even published a bulletin warning organizations about third-party cookies. 

Many of the healthcare brands we support at Oomph are already focused on safeguarding user privacy because they’re used to doing it with medical records. One of our clients, for example, is already exploring adopting an in-house analytics tool hosted on their own server. If your healthcare organization is relying on third-party cookies for any marketing efforts, analytic insights, or other website features, start thinking now about the best way to phase them out. 

Higher Education

Many institutions we work with are using third-party cookies because of digital efforts to drive student enrollment. When implementing personalization cookies, be sure they are implemented with the proper “SameSite” attribute value. Then be sure to engage your vendors; we’ve encouraged many of our higher education clients to explore how their vendors are preparing for this transition.  

Nonprofits

Like higher education, nonprofits should review the vendors and larger ad networks they rely on to build their volunteer base or drive donations. Many nonprofits don’t use these services, but those that do should get ahead of the change, otherwise you may stand to lose an important fundraising channel. 

4 Steps To Prepare for the End of Third-Party Cookies

Cookies, analytics, and cross-site tracking might all sound like areas best left to the pros. But there’s a lot you can do to prepare your organization for the move away from cookies, as well as critical opportunities to pull in a vendor to maintain the functionality you need. 

Audit Your Site

A website audit should always be your first step. Taking stock of the cookies you use is the best way to get a handle on the changes you’ll need to make. Tapping your web partner is a great idea here, too. Your vendor should be able to identify existing third-party cookie warnings, which can help shape your audit. 

For example, while we were updating a client’s email marketing integration recently, Chrome notified our developer that our client’s vendor was sending third-party cookies. We then reached out to the vendor to continue the conversation, knowing that those cookies had to be addressed.

Identify Affected Cookies 

The goal of your audit is to identify all third-party cookies that won’t make the cut. Don’t stop by just listing the cookie, either. Review what function it serves and the role it plays in your organization’s digital footprint. You may have to get rid of the cookie, but that doesn’t mean you have to ditch the strategy it’s tied to. 

Reach Out to Your Vendors

Ask vendors about their plans to handle the transition away from third-party cookies, and feel out whether they’ll still be able to offer the service they currently provide. Consider it a red flag if the vendor is uninformed or unprepared; you might have to seek out alternatives if there’s even the slightest chance your current vendor will be defunct by the end of the year. 

Design Alternatives

The end of third-party cookies is daunting, but it’s also exciting. Take this opportunity to innovate on your users’ behalf. How can you design engaging new experiences that still exceed their expectations? That’s more than possible, so long as you have the right tools in place.

This could be a self-hosted analytics tool you build yourself or new local storage solutions to replace the role of cookies. You might also consider a fully authenticated experience for the users of your site. Lean on a trusted partner here, too. Vendors with website expertise can guide you toward the right solution for you and your users.

Cookies on the Brain? 

For many organizations, this is the most they’ve thought about cookies in years. Third-party cookies have become so essential to building a business online, and yet they’ve largely flown under our radar. But while this change may feel overwhelming, making the switch doesn’t have to be. 

Here at Oomph, we see this as a golden opportunity for organizations to put their users first, and we’re already taking steps to help our clients do just that. 

Need a hand bringing your website into a world beyond third-party cookies? Let’s talk about it.

High-quality content management systems (CMS) and digital experience platforms (DXP) are the backbone of modern websites, helping you deliver powerful, personalized user experiences. The catch? You have to pick your platform first. 

At Oomph, we have a lot of love for open-source platforms like Drupal and WordPress. Over the years, we’ve also built applications for our clients using headless CMS tools, like Contentful and CosmicJS. The marketplace for these solutions continues to grow exponentially, including major players like Adobe Experience Manager, Sitecore, and Optimizely.

With so many options, developers and non-developers with a project on the horizon typically start by asking themselves, “Which CMS or DXP is the best fit for my website or application?” While that is no doubt an excellent question to consider, I think it’s equally important to ask, “Who is going to implement the solution?” 

CMS/DXP Solutions Are More Alike Than You Might Think

I recently attended the annual Healthcare Internet Conference and spoke with quite a few healthcare marketers about their CMS tools. I noticed a common thread: Many people think their CMS (some of which I mentioned above) is hard to use and doesn’t serve them well. 

That may very well be the case. Not all CMS tools are created equal; some are better suited for specific applications. However, most modern CMS and DXP tools have many of the same features in common, they just come at different price points. So here’s the multi-million dollar question: If most of these products provide access to the same or similar tools, why are so many customers displeased with them? 

Common Challenges of CMS/DXP Implementation

Often, we find that CMS users get frustrated because the tool they chose wasn’t configured to meet their specific needs. That doesn’t necessarily mean that it was set up incorrectly. That’s the beauty of many of today’s CMS and DXP products: They don’t take a one-size-fits-all approach. Instead, they allow for flexibility and customization to ensure that each customer gets the most out of the product.

While enticing, that flexibility also burdens the user with ensuring that their system is implemented effectively for their specific use case. In our experience, implementation is the make-or-break of a website development project. These are just a handful of things that can derail the process:

  1. The implementation partner didn’t fully understand how their client works and configure features accordingly.
  2. The demands of user experience overshadowed the needs of content editors and admins. 
  3. Hefty licensing fees ate away at the budget, leaving behind funds that don’t quite cover a thorough implementation. 
  4. The project was rushed to meet a tight deadline. 
  5. The CMS introduces new features over time that add complexity to the admin or editing experience. 
  6. Old features get sunsetted as new capabilities take their place. 

Most of the work we do at Oomph is to help our clients implement new websites and applications using content management systems like Drupal. We have decades of combined experience helping our clients create the ideal user experience for their target audience while also crafting a thoughtful content editing and admin experience that is easy to use.

But what does that look like in practice? 

4 Steps for a Successful CMS Implementation

Implementation can be the black box of setting up your CMS: You don’t know what you don’t know. So, we like to get our clients into a demo environment as soon as possible to help them better understand what they need from their CMS. Here’s how we use it to navigate successful CMS implementation: 

  1. Assess the Capabilities of the CMS

The first step can be the most simple at face value. Consider what the CMS needs to do for you, then find a CMS that includes all of those features. Content modeling (more on that below) is a key part of that process, but so is auditing your team’s abilities. 

Some teams may be developer-savvy and can handle less templated content-authoring features. Others may need a much more drag-and-drop experience. Either use case is normal and acceptable, but what matters is that you identify your needs and find both a CMS and an implementation process that meets them. That leads us to the next point.

  1. Test-Drive the CMS Early and Often

You wouldn’t buy a car without test-driving it first. Yet we find that people are often more than willing to license a CMS without looking under the hood.

Stepping into the CMS for a test drive is a huge part of getting the content editing experience right. We’ve been designing and engineering websites and platforms using CMS tools for well over a decade, and we’ve learned a thing or two along the way about good content management and editing experiences. 

Even with out-of-the-box, vanilla Drupal, the sky’s the limit for how you can configure it. But that also means that nothing is configured, and it can be difficult to get a sense of how best to configure and use it. Rather than diving into the deep end, we work with our clients to test the waters. We immediately set up a project sandbox that offers pre-configured content types, allowing you to enter content and play with a suite of components within the sleek drag-and-drop interface.

  1. Align User Experience with Content Authoring

Beyond pre-configured content and components, our sandbox sites include a stylish, default theme. The idea is to give you a taste both of what your live site could look like and what your content authoring experience might be. Since so many teams struggle to balance those two priorities, this can be a helpful way to figure out how your CMS can give you both. 

  1. Finalize Your Features & Capabilities 

While a demo gives you a good idea of the features you’ll need, it might include features you don’t. But discovering where our pre-built options aren’t a good fit is a good thing — it helps us understand exactly what YOUR TEAM does and does not need.

Our goal is to give you something tangible to react to, whether that’s love at first type or a chance to uncover capabilities that would serve you better. We’ve found this interactive yet structured process is the CMS silver bullet that leads to a better outcome. 

Content Modeling

Another key part of our project workflow is what we call content modeling. During this phase, we work with you to identify the many content types you’ll have on your website or application. Then, we can visualize them in a mapping system to determine things like: 

With a solid content model in place, we can have a higher level of confidence that our CMS implementation will create the right content editing experience for your team. From there, we actually implement the content model in the CMS as soon as possible so that you can test it out and we can make refinements before getting too far along in the process.

Content Moderation & Governance

Many clients tell us they either have too much or too little control over their content. In some cases, their content management system is so templated or rigid that marketing teams can’t quickly spin up landing pages and instead have to rely on development teams to assist. Other teams have too much freedom, allowing employees to easily deploy content that hasn’t been approved by the appropriate team members or strays from company brand standards. 

Here at Oomph, our mantra is balance. A good content editing process needs both flexibility and governance, so teams can create content when they need to, but avoid publishing content that doesn’t meet company standards. Through discovery, we work with clients to determine which content types need flexibility and which ones don’t. 

If a content type needs to be flexible, we create a framework that allows for agility while still ensuring that users can only select approved colors, font types, and font sizes. We also identify which content needs to be held in moderation and approved before it can be published on the website. 

Taking the time to discuss governance in advance creates a CMS experience that strikes the right balance between marketing freedom and brand adherence. 

Implementation Turns a Good CMS Into a Great One

Modern CMS/DXP solutions have mind-blowing features, and they will only continue to get more complex over time. But the reality is that while picking a CMS that has the features you need is important, how it’s configured and implemented might matter even more. After all, how helpful is it to have a CMS with embedded artificial intelligence if making simple copy updates to your home page is a nightmare? 

Implementation is the “it” factor that makes the difference between a CMS you love and one you’d rather do your job without.

Interested in solving your CMS headaches with better implementation? Let’s talk.