Modernization Paths

Modernization Paths

Choosing the Right Path for Your System's Future

Every engagement ends on one of two paths: improve the system you have, or rebuild it on a new architecture. We choose the path together, based on what the audit found and where your organization is headed.


Path A — Essential Modernization

Path A fixes the foundations of your current site without replacing it: structure, semantics, accessibility, and performance.

Path A includes:

  • Clear page structure and correct semantic HTML
  • Accessibility fixes for the barriers found in the audit
  • Fast, responsive interactions (good INP)
  • Modern, maintainable CSS
  • Rebuilt components where the old ones can't be fixed: menus, forms, key templates
  • Correct routing, page titles, and metadata for search
  • Performance gains without a platform change
  • Deployment through a standard CI/CD workflow, on Netlify (recommended) or your existing host

Path A fits when:

  • Your platform is sound, and the problems are in how it was built
  • Search matters to you, but it isn't your main source of revenue or reach
  • Traffic is moderate
  • You run one site, not a network of sites or regions
  • You need results within a standard engagement

Path B — Sovereign Static Generated Architecture (SSGA)

Path B rebuilds your site on a new architecture, for organizations whose scale, visibility, or business model has outgrown their platform.

SSGA pre-renders every page to plain HTML at build time, using Angular CLI, Next.js (React), or Nuxt (Vue.js). Server rendering is used only where content must be live. Pages load fast, work before any JavaScript runs, and are fully readable by search engines and assistive technology.

Path B includes:

  • A full rebuild on Angular CLI, Next.js (React), or Nuxt (Vue.js), with TypeScript
  • A new routing, metadata, and rendering strategy
  • An accessible component library your team can reuse
  • A governance document: the rules that keep the site accessible, fast, and consistent as it grows
  • A roadmap that extends beyond the engagement

Path B fits when:

  • Your current platform can't meet accessibility or performance targets, however well it's patched
  • Traffic and visibility are high
  • Search is central to your mission or revenue
  • You run, or plan to run, several sites, chapters, or regions on one framework
  • Load speed and responsiveness directly affect donations, sign-ups, or sales

Path B costs nothing extra. It adds up to two weeks to your timeline.


At a Glance

Path A — Essential ModernizationPath B — SSGA
What changesYour current site, improvedA new architecture
PlatformStays the sameAngular CLI, Next.js (React), or Nuxt (Vue.js)
Content updatesYour current editor, or an Auralicode® retainer planAn Auralicode® retainer plan: send changes by email
Multi-site readyNoYes
PriceYour tier's fixed maximumYour tier's fixed maximum (no extra cost)
TimelineYour tier's estimateYour tier's estimate, plus up to two weeks

Both Paths, Every Service Tier

  • Web Foundations
  • Web Applications
  • Robust Web Apps
  • Enterprise‑Grade

The tier reflects the size of your system. The path reflects how deep the change needs to go.


How We Choose Your Path

After the audit, proposal, discovery, and prototype, we look at:

  • How large the system is, and how much traffic it carries
  • How much your organization depends on search
  • How mature the current architecture is
  • Your accessibility posture and performance bottlenecks
  • Your long-term goals

You don't choose your path alone.

We decide together, based on the evidence.