{"id":7877,"date":"2026-05-29T00:00:16","date_gmt":"2026-05-28T18:30:16","guid":{"rendered":"https:\/\/www.changepond.com\/resources\/blog\/?p=7877"},"modified":"2026-05-29T16:28:16","modified_gmt":"2026-05-29T10:58:16","slug":"modular-qa-architecture","status":"publish","type":"post","link":"https:\/\/www.changepond.com\/resources\/blog\/modular-qa-architecture\/","title":{"rendered":"The Architecture Behind AI-Ready Enterprise QA"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The Architecture Behind Intelligent QA Operations<\/strong><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Senthil Rudrappa <\/span>– May 29,2026<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tLinkedin<\/span>\n\t\t\t\t\t\t<\/i>\t\t\t\t\t<\/a>\n\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tX-twitter<\/span>\n\t\t\t\t\t\t<\/i>\t\t\t\t\t<\/a>\n\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tFacebook<\/span>\n\t\t\t\t\t\t<\/i>\t\t\t\t\t<\/a>\n\t\t\t\t<\/span>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\r\n <\/i>\r\n Copied!<\/span>\r\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\"LinkedIn\"\t\t\t\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

60 Requirements.Became 18 Modules. One Big Shift in Enterprise QA Thinking.<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In the first article<\/a> of this series, we explored why fragmented validation has become one of the biggest operational bottlenecks in enterprise QA.<\/p>

The issue is no longer whether enterprises have enough testing tools. Most already do. The real challenge is how those tools, workflows, reports, validation layers, and release signals operate together across the software delivery lifecycle.<\/p>

This article moves from the problem to the architecture.<\/p>

If QA orchestration is the missing layer, what should the platform behind it look like?<\/p>

That question shaped the architecture behind ICE – Changepond\u2019s<\/span>\u00a0<\/span>internal approach to intelligent QA operations.<\/span><\/span> Before the platform became code, it was mapped through functional requirements, engineering boundaries, validation disciplines, intelligence layers, and enterprise infrastructure needs.<\/p>

The result was a modular architecture: 60 functional requirements organized into 18 Maven modules.<\/strong><\/p>

This was not just a technical structuring exercise. It was a way to turn a fragmented QA problem into a buildable platform architecture.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Why Architecture Matters In Enterprise QA<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Enterprise QA fragmentation cannot be solved by simply adding another testing tool. That only adds one more layer to an already complex environment.<\/p>

Modern QA platforms need to solve a deeper architecture problem: how to bring validation capabilities, intelligence workflows, integrations, configuration layers, reporting systems, and enterprise controls into one coherent operating model.<\/p>

That was the challenge behind ICE,the way QA is structured and executed within\u00a0<\/span>Changepond<\/span>.<\/span><\/p>

The platform needed to support multiple validation capabilities, including functional testing, accessibility validation, security analysis, API testing, network monitoring, performance validation, visual assurance, and cross-browser compatibility. But supporting many capabilities is not enough. Each needs a clear boundary, a defined responsibility, and a way to operate inside a unified platform without creating dependency chaos.<\/p>

This is where architecture becomes more than a technical decision. It becomes the operating model.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The Principle That Shaped The Platform<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The most important architecture decision was simple:<\/p>

One module. One concern. One clear responsibility.<\/p>

ICE was structured as a Maven multi-module project – not as one large monolith, and not as a complex microservices architecture with unnecessary deployment overhead. It was designed as a unified platform with modular internal boundaries.<\/p>

Each module has a defined purpose. Each can be developed, tested, and extended independently. Each contributes to the larger platform without taking ownership of responsibilities that belong elsewhere.<\/p>

That matters because enterprise QA platforms can easily collapse under their own ambition. A single \u201ctesting module\u201d can start owning execution, analytics, reporting, API validation, accessibility, configuration, and governance. Over time, blurred boundaries make the platform harder to maintain and scale.<\/p>

ICE avoids this by making responsibility visible in the architecture itself.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Industry Signal: AI In QA Needs Architecture to Scale<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

\u201cAccording to the World Quality Report 2025<\/strong> by OpenText, Capgemini, and Sogeti, nearly 90%<\/strong> of organizations are actively pursuing generative AI in quality engineering, but only 15%<\/strong> have achieved enterprise-scale deployment.\u201d<\/em> Source<\/strong>: Capgemini<\/a><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

That gap reinforces a critical point: AI in QA does not scale through isolated experiments. It needs the right architecture, governance, and operating model behind it.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

How 60 Requirements Became 18 Modules<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The 60 functional requirements were not distributed evenly across modules. That was intentional.<\/p>

Some modules own one major capability. Others own multiple related requirements. The architecture follows responsibility, not arithmetic.<\/p>
Architecture Layer<\/strong><\/td>Modules<\/strong><\/td>Purpose<\/strong><\/td><\/tr><\/thead>
Validation Capability Modules<\/strong><\/td>Accessibility, Security, API Testing, Network<\/td>Own specialized validation capabilities with distinct execution logic, scoring, reporting, and integration needs<\/td><\/tr>
Core Pipeline Modules<\/strong><\/td>Upload, LLM, Test Case, Journey, Git, Execution<\/td>Manage how artifacts enter, move through, and execute inside the platform<\/td><\/tr>
Intelligence Modules<\/strong><\/td>LLM Extensions, Agent, Validation<\/td>Support AI-assisted workflows, autonomous execution, validation gates, and quality intelligence<\/td><\/tr>
Platform Infrastructure Modules<\/strong><\/td>Analytics, Settings, Tenant, Core JAR, SDK<\/td>Provide reporting, configuration, tenant controls, shared utilities, governance, performance-related engines, and external integration capabilities<\/td><\/tr><\/tbody><\/table>

This structure gives the platform both breadth and control.<\/p>

ICE can support multiple QA capabilities without forcing every capability into one overloaded architecture layer.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

What This Architecture Solves For QA Teams<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In current projects, this architecture supports use cases such as test execution, coverage mapping, pipeline monitoring, data and test asset management, governance ownership, AI-assisted validation, reporting, defect tracking, and release gates.<\/span><\/span>\u00a0<\/span><\/p>

For enterprise QA leaders, modular architecture is not just an engineering detail. It solves practical delivery problems.<\/p>

When responsibilities are unclear, every change becomes risky. Teams need more coordination. Developers need more context. Dependencies multiply. Delivery slows down.<\/p>

When responsibilities are clear, teams can work in parallel without stepping on each other.<\/p>

Each module can carry its own entities, repositories, services, controllers, migrations, and test stubs. Developers can focus on a specific responsibility without needing to understand the entire platform before contributing.<\/p>

For enterprise teams, this creates four practical advantages:<\/p>

Value Area<\/strong><\/p><\/td>

What It Means<\/strong><\/p><\/td><\/tr><\/thead>

Faster Parallel Development<\/strong><\/p><\/td>

Teams can work across modules without waiting for every platform decision to be centralized<\/p><\/td><\/tr>

Lower Maintenance Complexity<\/strong><\/p><\/td>

Changes are easier to isolate when each module owns a defined responsibility<\/p><\/td><\/tr>

Better AI Readiness<\/strong><\/p><\/td>

LLM infrastructure, AI-assisted workflows, validation gates, and execution flows can be governed separately<\/p><\/td><\/tr>

Stronger Enterprise Governance<\/strong><\/p><\/td>

Tenant controls, settings, audit trails, analytics, security foundations, and integrations have a defined place<\/p><\/td><\/tr><\/tbody><\/table>

Clear module boundaries reduce dependency burden. They make the platform easier to build, govern, and extend.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Conclusion: Architecture Is the Operating Model<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Enterprise QA is entering a phase where platform architecture matters as much as testing capability.<\/p>

The goal is not just to organize code. It is to create a structure that can support modular ownership, parallel development, AI-assisted workflows, enterprise governance, and connected quality operations at scale.<\/p>

The 60 functional requirements defined what the platform needed to do. The 18 modules defined how the platform could actually be built.<\/p>

This article continues Changepond\u2019s Intelligent QA Operations series, moving from the orchestration crisis to the architecture decisions behind a unified QA platform.<\/p>

In the next article, we look at how functional requirements need to be written when AI becomes part of the development process. The focus shifts from platform architecture to requirement quality \u2014 and why clear, structured requirements now directly shape architecture, scaffolding, and engineering output.<\/p>

For more information, email us at info@changepond.com<\/strong><\/a> or visit www.changepond.com<\/strong><\/a><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

CTA See How Modular QA Architecture Supports Intelligent Orchestration.\n\u2192 \n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tTalk to Changepond\u2019s Intelligent QA Team<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Frequently Asked Questions<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

What is modular QA architecture?
<\/span><\/p>

Modular QA architecture separates testing, execution, intelligence, analytics, and infrastructure responsibilities into clearly defined modules. This reduces dependency complexity and supports scalable platform development.<\/p>

Why were 60 functional requirements organized into 18 modules?<\/span><\/p>

They were organized into 18 modules to create clear ownership boundaries across validation capabilities, pipeline workflows, AI-assisted features, and enterprise infrastructure capabilities.<\/p>

How does modular architecture reduce QA fragmentation?<\/span><\/p>

It gives each capability a defined responsibility inside a unified platform model, allowing testing, execution, analytics, governance, and intelligence workflows to operate through a connected architecture.<\/p>

How does AI fit into modular QA architecture? <\/span><\/p>

AI-assisted capabilities are organized through defined intelligence modules and LLM integration layers, allowing test generation, natural language import, exploratory discovery, validation checks, and agent workflows to operate as governed platform capabilities.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\"LinkedIn\"\t\t\t\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tLink<\/span>\n\t\t\t\t\t\t<\/i>\t\t\t\t\t<\/a>\n\t\t\t\t<\/span>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tShare\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tLinkedin<\/span>\n\t\t\t\t\t\t<\/i>\t\t\t\t\t<\/a>\n\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tX-twitter<\/span>\n\t\t\t\t\t\t<\/i>\t\t\t\t\t<\/a>\n\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\tFacebook<\/span>\n\t\t\t\t\t\t<\/i>\t\t\t\t\t<\/a>\n\t\t\t\t<\/span>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\r\n <\/i>\r\n Copied!<\/span>\r\n <\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

A behind-the-scenes look at how Changepond\u2019s QA engineering teams structured 60 requirements into 18 modules for scalable, governed quality operations.<\/p>\n","protected":false},"author":14,"featured_media":7907,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_titles_title":"Modular QA Architecture For AI-Ready Quality Engineering","_seopress_titles_desc":"See how Changepond structured 60 QA requirements into 18 modules to support modular testing, AI-assisted workflows, governance, and enterprise QA delivery.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"none","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"both","_seopress_redirections_param":"","_seopress_redirections_type":301,"_seopress_analysis_target_kw":"","footnotes":""},"categories":[29],"tags":[],"class_list":["post-7877","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-genai"],"_links":{"self":[{"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/posts\/7877","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/comments?post=7877"}],"version-history":[{"count":43,"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/posts\/7877\/revisions"}],"predecessor-version":[{"id":7927,"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/posts\/7877\/revisions\/7927"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/media\/7907"}],"wp:attachment":[{"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/media?parent=7877"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/categories?post=7877"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.changepond.com\/resources\/blog\/wp-json\/wp\/v2\/tags?post=7877"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}