Custom WordPress Theme Research for NeuroCumulus.com

Full report

On this page

Executive summary

As of May 20, 2026, NeuroCumulus.com is effectively a blank slate: the live site is a default WordPress installation showing the standard sample page and “Hello world!” post. That is good news for implementation because this is not a migration-heavy redesign; it is a greenfield branding, information architecture, content, and theme-engineering project.

The uploaded Neuro Cumulus description positions the brand as AI infrastructure for shared memory, cross-model interoperability, secure federation, and coordinated multi-agent intelligence. It also explicitly separates Neuro Cumulus from biological or clinical neuroscience platforms. That separation should become a visible brand rule on the site because Cumulus Neuroscience already occupies adjacent naming territory in public search and uses highly medical language around brain function, biomarkers, clinical studies, and EEG. NeuroCumulus.com should therefore look and sound like advanced AI systems infrastructure, not health tech, neuro devices, or consumer “brain” branding.

For WordPress implementation, the strongest fit is a custom hybrid theme: classic PHP templates for precise layout control, plus theme.json for global design tokens and editor constraints, Gutenberg block patterns for consistent layout primitives, and ACF Pro for a small number of structured fields and dynamic blocks. WordPress explicitly supports theme.json in both classic and block themes; block patterns can be registered by themes; custom post types and taxonomies can be exposed through the REST API; and ACF now recommends block.json for block registration while Local JSON improves version control and performance.

The site should launch with a tight primary architecture: Home, About, Services, Blog, Resources, Contact, and Legal, supported by single templates for blog posts and resources, plus a resource taxonomy system for topic-based discovery. The content strategy should emphasize one clear core promise—“shared memory for interoperable AI”—and then ladder down into explainers, services, research resources, and thought-leadership posts. That structure is more persuasive for enterprise technical buyers than a sprawling startup page with too many abstractions.

The non-negotiable quality bar should be WCAG 2.2 Level AA, not an older accessibility baseline, alongside Core Web Vitals targets based on LCP, INP, and CLS, structured data for Organization, Breadcrumbs, and Articles, and privacy-aware analytics with consent controls. W3C advises using WCAG 2.2 as the current version; Google’s Core Web Vitals currently focus on LCP, INP, and CLS; Google recommends Organization markup to help disambiguate an organization in search; and Breadcrumb markup helps users understand page position in site hierarchy.

Operationally, the theme should be built against the latest stable production release line of WordPress 6.9.x, while being smoke-tested against the currently published WordPress 7.0 release candidate before launch. For hosting, Kinsta is the strongest default managed option for this project; WP Engine is strongest for enterprise workflow tooling; Cloudways is strongest when the team wants more infrastructure control.

A realistic effort range for a polished first release—strategy, design system, custom theme, blocks, content entry, accessibility, SEO, QA, analytics, and launch support—is roughly 190 to 240 hours, assuming one major review cycle and no extensive custom illustration or legal drafting beyond templates.

Brand and audience strategy

The brand should be built from the architecture description, not from the literal word “neuro.” The description emphasizes a unified AI cloud, memory interoperability, shared latent-state exchange, zero-trust governance, federated retrieval, and consistency across agents. In other words, the site should communicate precision, systems thinking, security, and research depth—not wellness, psychology, or medical neuroscience.

Brand identity extraction

The ideal tone is serious but legible. It should sound like an expert systems architect speaking to a CTO, research lead, or enterprise innovation buyer: credible, calm, slightly visionary, but never mystical. A good internal writing rule is “technical clarity first, ambition second.” The architecture document supports that because its strongest differentiator is not generic AI optimism; it is the specificity of interoperability, memory, consistency, and governance.

Proposed visual directions

Recommended palette: Deep infrastructure. It best aligns with the uploaded description’s emphasis on cloud systems, memory coordination, and security, while clearly separating the brand from medical-neuro visual conventions.

Typography

Typography should feel structured and rational. Use short hero lines, generous leading in long-form research pages, and restrained display sizing. Avoid decorative typefaces that suggest biotech, futurism-for-futurism’s-sake, or consumer wellness.

Logo usage guidance

The logo should communicate networked memory and cloud coordination, not brains or synapses. Preferred forms:

• a cloud-outline fused with a node network
• a layered memory-grid mark
• an abstract “N/C” monogram built from linked blocks or stack layers

Use a light version on dark backgrounds and a dark version on light backgrounds. Avoid glow effects, gradients inside tiny lockups, or marks that rely on thin lines at favicon scale. A simplified favicon should be a single high-contrast symbol, not the full wordmark.

A practical rule: if the logo could plausibly belong to a neurological clinic, an EEG startup, or a meditation app, it is the wrong logo for Neuro Cumulus. That rule follows directly from the architecture document’s disambiguation need and the public positioning of Cumulus Neuroscience.

Target audience personas

The most credible first-release site should speak to four audiences, ordered by commercial importance.

A secondary persona is a strategic partner or investor who wants to understand the ambition, differentiation, and maturity of the concept quickly. That audience benefits from a homepage that pairs concise positioning with a clear architecture explainer and a resource hub.

Competitive benchmarks and information architecture

Competitive and inspirational site analysis

The site benchmarks should be used selectively. Neuro Cumulus is too early and too conceptually dense to mimic the sprawl of a mega-platform, but several public sites offer patterns worth borrowing.

Recommended site architecture

Because the live site is still the default WordPress install, the architecture should be rebuilt from first principles. WordPress uses template hierarchy to determine which file renders a given request and falls back to index when no more specific template is available, so a professional implementation should define specific templates for the homepage, services, resources, blog, contact, and legal pages rather than relying on generic fallbacks.

flowchart TD
    A[Home] --> B[About]
    A --> C[Services]
    A --> D[Resources]
    A --> E[Blog]
    A --> F[Contact]

    C --> C1[Architecture Strategy]
    C --> C2[Memory and Orchestration Design]
    C --> C3[Security and Governance Review]
    C --> C4[Prototype Implementation]

    D --> D1[Architecture Overview]
    D --> D2[Explainers]
    D --> D3[Benchmarks]
    D --> D4[Diagrams]
    D --> D5[Glossary]

    E --> E1[Single Post]
    D --> D6[Single Resource]

    A --> G[Legal]
    G --> G1[Privacy Policy]
    G --> G2[Terms of Use]
    G --> G3[Cookie Notice]
    G --> G4[Accessibility Statement]

Sitemap and template matrix

A useful refinement is to keep the top navigation extremely tight:

Home · About · Services · Resources · Blog · Contact

Everything else should live in the footer or within page-local navigation.

Page content system

The content drafts below assume that Neuro Cumulus is commercializing the framework through a combination of advisory, design, and prototype implementation services. If that assumption is wrong and the site is meant to be purely product-led or research-led, the same templates still work: rename Services to Solutions or Framework and keep the architecture.

Home page draft

Recommended homepage module order

1. Hero with architecture-visual background
2. One-paragraph problem statement
3. Four capability cards
4. Visual explainer of memory and orchestration
5. Services teaser
6. Resources teaser
7. Blog teaser
8. Contact CTA
9. Footer with legal and accessibility links

About page draft

Services page draft

Blog page draft

Resources page draft

Contact page draft

Legal page draft

Important note: any actual privacy, cookie, or terms language should be reviewed by counsel before publication. The page above is a content and UX structure, not legal advice.

Suggested blog pipeline

Accessibility, search, and performance foundation

W3C advises using WCAG 2.2 as the current standard, and WCAG 2.2 introduces additional criteria around focus visibility, focus not obscured, target size, redundant entry, and accessible authentication. WAI’s tutorials also provide concrete guidance for images, forms, labels, headings, page structure, and keyboard access. The site should therefore be designed to WCAG 2.2 Level AA from the first Figma pass onward, not retrofitted after theme development.

Accessibility and WCAG compliance checklist

The reason to start with this checklist is practical, not ceremonial: headings improve page navigation, labels improve form completion, keyboard support protects core functionality, and decorative vs informative image handling prevents screen-reader noise.

Search and performance recommendations

Google’s current Core Web Vitals are Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. Current “good” thresholds are LCP at 2.5 seconds or less, INP at 200 ms or less, and CLS at 0.1 or less, measured at the 75th percentile. WordPress already supports responsive images with srcset and sizes, and WordPress core has lazy-loaded images by default since 5.5. WordPress also exposes helper functions for loading optimization attributes, including loading, decoding, and fetchpriority.

That leads to a fairly clear implementation strategy for Neuro Cumulus:

A particularly important image rule comes from the combination of WordPress behavior and web performance guidance: below-the-fold images can lazy-load, but the hero image should load eagerly, and every image should include dimensions to avoid CLS.

Schema markup suggestions

Google recommends Organization structured data on the homepage to help Google understand administrative details and disambiguate the organization. Google also documents BreadcrumbList and Article markup, and Schema.org provides useful types for WebSite, Service, SoftwareApplication, TechArticle, and Dataset. That makes schema especially valuable for Neuro Cumulus because the name needs disambiguation and the content roadmap includes technical resources.

Low-priority schema: FAQPage. Google states FAQ rich results are now limited to well-known, authoritative government and health-focused websites, so FAQ schema should not be treated as a major visibility lever for this project. Use it only if the content model needs it, not as a traffic bet.

WordPress theme technical specification

Recommended theme architecture

The best build for Neuro Cumulus is a custom classic-hybrid theme rather than a full block theme or a page-builder stack.

Why this is the strongest fit:

• WordPress distinguishes classic themes and block themes, and theme.json works with both.
• theme.json provides a canonical way to define editor settings, styles, templates, and template parts, and it helps WordPress manage CSS more consistently.
• Themes can register block patterns directly, which is ideal for a controlled marketing/editor workflow.
• Custom post types and taxonomies can be exposed via wp/v2 when REST support is enabled.
• ACF Blocks are dynamic and PHP-friendly, and ACF now recommends block.json rather than the older acf_register_block_type() pattern.

That combination gives the project the balance it needs:

• Custom PHP templates for pixel-level control and clean performance
• theme.json for tokens, editor settings, spacing, typography, and block styling
• Block patterns for reusable editorial layouts
• ACF Pro only where content is structured enough that core blocks alone become awkward

Suggested file structure

neurocumulus-theme/
├─ style.css
├─ functions.php
├─ theme.json
├─ index.php
├─ front-page.php
├─ page.php
├─ page-about.php
├─ page-services.php
├─ page-contact.php
├─ page-legal.php
├─ home.php
├─ archive.php
├─ archive-resource.php
├─ archive-service.php
├─ single.php
├─ single-resource.php
├─ single-service.php
├─ search.php
├─ 404.php
├─ screenshot.png
├─ inc/
│  ├─ setup.php
│  ├─ enqueue.php
│  ├─ cpts.php
│  ├─ taxonomies.php
│  ├─ schema.php
│  ├─ blocks.php
│  ├─ patterns.php
│  ├─ acf-fields.php
│  ├─ rest.php
│  └─ helpers.php
├─ template-parts/
│  ├─ header/site-header.php
│  ├─ footer/site-footer.php
│  ├─ hero/page-hero.php
│  ├─ cards/resource-card.php
│  ├─ cards/post-card.php
│  └─ sections/cta-band.php
├─ assets/
│  ├─ css/
│  │  ├─ app.css
│  │  ├─ editor.css
│  │  └─ critical.css
│  ├─ js/
│  │  ├─ app.js
│  │  └─ analytics.js
│  ├─ fonts/
│  └─ images/
├─ blocks/
│  ├─ nc-hero/
│  │  ├─ block.json
│  │  ├─ render.php
│  │  └─ style.css
│  ├─ nc-capability-grid/
│  ├─ nc-resource-list/
│  ├─ nc-proof-strip/
│  └─ nc-cta-band/
├─ patterns/
│  ├─ home-hero.php
│  ├─ service-overview.php
│  ├─ resource-feature.php
│  └─ contact-cta.php
└─ acf-json/

Required templates and content model

Custom post types and taxonomies

WordPress recommends explicit registration of post types and taxonomies, and taxonomies should be directly associated with their post types so the connections are recognized correctly in queries and tooling. REST support should be enabled for custom content that editors or integrations need in the block editor or via wp/v2.

Suggested taxonomies

Theme options

An ACF Options Page is a good fit here because these fields are global, structured, and reused across templates. ACF’s field-group registration via PHP and Local JSON both support distribution and version control well.

Gutenberg block patterns

Use patterns for editorial consistency and custom blocks only when the content is structured or dynamic enough to justify them.

Recommended patterns

• homepage hero with proof strip
• three-column capability grid
• service teaser band
• featured resource section
• authoritatively styled article intro
• CTA band
• legal page nav list
• contact split layout

Recommended custom blocks

ACF usage

ACF should be used surgically, not as an all-purpose page builder. The best practice for this project is:

• use core blocks for ordinary rich-text content
• use ACF for structured, repeatable data
• commit ACF definitions to version control through Local JSON or PHP registration
• expose field data to REST only where needed

That aligns with ACF’s own documentation: Local JSON improves speed and version control, REST API integration is built in, ACF Blocks are dynamic and PHP-friendly, and block registration should use block.json.

Recommended ACF field groups

REST and API endpoints

WordPress’s REST API provides native endpoints for core content types and can expose CPTs and taxonomies in wp/v2. For Neuro Cumulus, that is enough for the first release. Custom endpoints should be added only when you have a clear use case, such as exposing site settings or powering a remote microsite.

Responsive breakpoints and component library

Image and asset guidelines

WordPress supports responsive images automatically, and performance guidance is clear: use efficient formats, include dimensions, lazy-load lower content, and keep the hero eager. AVIF offers high compression efficiency, and responsive image markup plus width/height attributes helps prevent layout shifts.

Visual mockup suggestions

Homepage concept A dark, quiet hero panel with a network-memory illustration over subtle grid lines. The layout should pair a short headline with a one-sentence explanation and two CTA buttons. Below that, a capability row explains memory, orchestration, security, and implementation in plain language.

About page concept A mission-led introduction followed by a “principles” section and a diagram that explains how Neuro Cumulus thinks about systems. Use a clean timeline only if there is a real founder or product history to show.

Services page concept A card grid plus a horizontal process band: assess, design, govern, prototype. Keep each card outcome-oriented and anchored in architecture.

Resources page concept A filterable hub with featured resource callout, taxonomy chips, and a sharp distinction between short explainers and downloadable briefs.

Example CSS variables

:root {
  --color-bg: #08111f;
  --color-surface: #13233f;
  --color-surface-alt: #0f1b30;
  --color-text: #f7fafc;
  --color-text-muted: #cbd5e1;
  --color-border: #2b3f63;
  --color-primary: #38bdf8;
  --color-secondary: #8b5cf6;
  --color-success: #34d399;
  --color-danger: #f87171;

  --font-heading: "SoraVariable", "Inter", system-ui, sans-serif;
  --font-body: "InterVariable", system-ui, sans-serif;
  --font-mono: "IBM Plex Mono", ui-monospace, SFMono-Regular, monospace;

  --radius-sm: 0.375rem;
  --radius-md: 0.75rem;
  --radius-lg: 1.25rem;

  --space-1: 0.25rem;
  --space-2: 0.5rem;
  --space-3: 0.75rem;
  --space-4: 1rem;
  --space-6: 1.5rem;
  --space-8: 2rem;
  --space-12: 3rem;
  --space-16: 4rem;

  --container-sm: 42rem;
  --container-md: 56rem;
  --container-lg: 72rem;
  --container-xl: 84rem;
}

Plugin options

Lean stack recommendation: ACF Pro + one SEO plugin only + SMTP plugin if needed. Avoid page builders unless there is a non-negotiable editorial requirement that cannot be met with patterns and custom blocks.

Sample code snippets

functions.php

<?php
/**
 * Neuro Cumulus theme bootstrap.
 */

if (!defined('ABSPATH')) {
	exit;
}

require_once get_theme_file_path('/inc/cpts.php');
require_once get_theme_file_path('/inc/schema.php');

add_action('after_setup_theme', function () {
	add_theme_support('title-tag');
	add_theme_support('post-thumbnails');
	add_theme_support('align-wide');
	add_theme_support('responsive-embeds');
	add_theme_support('editor-styles');
	add_editor_style('assets/css/editor.css');

	add_theme_support('html5', [
		'search-form',
		'comment-form',
		'comment-list',
		'gallery',
		'caption',
		'style',
		'script',
	]);

	register_nav_menus([
		'primary' => __('Primary Navigation', 'neurocumulus'),
		'footer'  => __('Footer Navigation', 'neurocumulus'),
	]);

	add_image_size('nc-hero', 1600, 900, true);
	add_image_size('nc-card', 720, 480, true);
	add_image_size('nc-square', 800, 800, true);
});

add_action('wp_enqueue_scripts', function () {
	$theme = wp_get_theme();

	wp_enqueue_style(
		'neurocumulus-app',
		get_theme_file_uri('/assets/css/app.css'),
		[],
		$theme->get('Version')
	);

	wp_enqueue_script(
		'neurocumulus-app',
		get_theme_file_uri('/assets/js/app.js'),
		[],
		$theme->get('Version'),
		[
			'in_footer' => true,
			'strategy'  => 'defer',
		]
	);
});

add_action('init', function () {
	$block_files = glob(get_theme_file_path('/blocks/*/block.json'));

	if (!empty($block_files)) {
		foreach ($block_files as $block_json) {
			register_block_type(dirname($block_json));
		}
	}
});

/**
 * Make the hero image eager and high priority when requested explicitly.
 */
add_filter('wp_get_attachment_image_attributes', function ($attr, $attachment, $size) {
	if ($size === 'nc-hero') {
		$attr['loading'] = 'eager';
		$attr['fetchpriority'] = 'high';
		$attr['decoding'] = 'async';
	}
	return $attr;
}, 10, 3);

single.php

<?php
/**
 * Default single post template.
 */

get_header();
?>

<main id="primary" class="site-main">
	<?php if (have_posts()) : while (have_posts()) : the_post(); ?>
		<article id="post-<?php the_ID(); ?>" <?php post_class('article'); ?>>
			<header class="article__header container">
				<?php if (has_post_thumbnail()) : ?>
					<div class="article__media">
						<?php
						echo get_the_post_thumbnail(
							get_the_ID(),
							'nc-hero',
							[
								'class' => 'article__image',
								'alt'   => trim(wp_strip_all_tags(get_the_title())),
							]
						);
						?>
					</div>
				<?php endif; ?>

				<?php if (has_category()) : ?>
					<p class="article__eyebrow">
						<?php echo wp_kses_post(get_the_category_list(', ')); ?>
					</p>
				<?php endif; ?>

				<h1 class="article__title"><?php the_title(); ?></h1>

				<p class="article__meta">
					<time datetime="<?php echo esc_attr(get_the_date('c')); ?>">
						<?php echo esc_html(get_the_date('F j, Y')); ?>
					</time>
					<span aria-hidden="true">·</span>
					<span><?php echo esc_html(get_the_author()); ?></span>
				</p>
			</header>

			<div class="article__content container container--reading">
				<?php the_content(); ?>
			</div>

			<footer class="article__footer container container--reading">
				<?php the_post_navigation([
					'prev_text' => 'Previous article',
					'next_text' => 'Next article',
				]); ?>
			</footer>
		</article>
	<?php endwhile; endif; ?>
</main>

<?php
get_footer();

Block registration with block.json

{
  "apiVersion": 3,
  "name": "nc/hero",
  "title": "NC Hero",
  "description": "Hero section with eyebrow, heading, copy, and CTA buttons.",
  "category": "design",
  "icon": "cloud",
  "keywords": ["hero", "cta", "intro"],
  "style": ["file:./style.css"],
  "supports": {
    "anchor": true,
    "align": ["wide", "full"]
  },
  "acf": {
    "mode": "preview",
    "renderTemplate": "render.php"
  }
}

<?php
/**
 * blocks/nc-hero/render.php
 */

$eyebrow   = get_field('eyebrow') ?: '';
$headline  = get_field('headline') ?: '';
$body      = get_field('body') ?: '';
$primary   = get_field('primary_cta');
$secondary = get_field('secondary_cta');
?>
<section class="nc-hero alignfull">
	<div class="container">
		<?php if ($eyebrow) : ?>
			<p class="nc-hero__eyebrow"><?php echo esc_html($eyebrow); ?></p>
		<?php endif; ?>

		<?php if ($headline) : ?>
			<h1 class="nc-hero__title"><?php echo esc_html($headline); ?></h1>
		<?php endif; ?>

		<?php if ($body) : ?>
			<div class="nc-hero__body">
				<?php echo wp_kses_post(wpautop($body)); ?>
			</div>
		<?php endif; ?>

		<div class="nc-hero__actions">
			<?php if (!empty($primary['url']) && !empty($primary['title'])) : ?>
				<a class="button button--primary" href="<?php echo esc_url($primary['url']); ?>">
					<?php echo esc_html($primary['title']); ?>
				</a>
			<?php endif; ?>

			<?php if (!empty($secondary['url']) && !empty($secondary['title'])) : ?>
				<a class="button button--secondary" href="<?php echo esc_url($secondary['url']); ?>">
					<?php echo esc_html($secondary['title']); ?>
				</a>
			<?php endif; ?>
		</div>
	</div>
</section>

Schema JSON-LD snippet

<?php
$org_name = get_field('organization_name', 'option') ?: get_bloginfo('name');
$site_url = home_url('/');
$logo_url = wp_get_attachment_image_url(get_field('schema_logo', 'option'), 'full');
$description = get_field('organization_description', 'option') ?: get_bloginfo('description');

$schema = [
	'@context' => 'https://schema.org',
	'@graph'   => [
		[
			'@type'       => 'Organization',
			'@id'         => trailingslashit($site_url) . '#organization',
			'name'        => $org_name,
			'url'         => $site_url,
			'description' => $description,
			'logo'        => $logo_url,
			'sameAs'      => array_values(array_filter([
				get_field('linkedin_url', 'option'),
				get_field('github_url', 'option'),
				get_field('x_url', 'option')
			])),
		],
		[
			'@type' => 'WebSite',
			'@id'   => trailingslashit($site_url) . '#website',
			'url'   => $site_url,
			'name'  => $org_name,
			'publisher' => [
				'@id' => trailingslashit($site_url) . '#organization'
			]
		]
	]
];
?>
<script type="application/ld+json">
<?php echo wp_json_encode($schema, JSON_UNESCAPED_SLASHES | JSON_UNESCAPED_UNICODE | JSON_PRETTY_PRINT); ?>
</script>

Delivery, operations, and launch plan

Analytics and tracking setup

Google Analytics 4 should be the primary analytics layer, Google Search Console should be configured as a Domain property, and Microsoft Clarity can be layered in for behavioral analysis if privacy requirements allow it. Google’s guidance covers GA4 web collection, recommended and custom event setup, and consent mode. Search Console requires property verification and helps monitor indexing, performance, and even some security issues. Microsoft documents Clarity setup and its behavioral analysis use cases.

Recommended event map

Consent and privacy implementation

Google’s consent-mode documentation is clear that developers should set a default consent state and then update it based on the user’s choice. That means GA4 and any other analytics or advertising tags should not simply fire at page load in a legally risky “banner theater” way. If Clarity is used, its own documentation also includes consent and deployment guidance.

Recommended privacy setup

• Use a real consent banner, not implied consent
• Default analytics storage to denied until consent
• Fire GA4 only after consent update
• Document analytics and session analysis in the Privacy Policy
• Provide a Cookie Notice and Accessibility Statement in the footer
• Keep forms minimal; collect only the fields needed to respond

Security and privacy considerations

WordPress’s own security guidance emphasizes that security is risk reduction, not risk elimination, and that the most important baseline control is keeping WordPress core, themes, and plugins up to date. WordPress also documents HTTPS as the secure browsing default, and OWASP ASVS provides a strong control framework for modern web applications.

Recommended hardening baseline

If gated accounts or deeper app features are ever introduced, expand the review against OWASP’s authentication and session guidance as part of a fuller security assessment.

Hosting recommendations

Recommendation: Kinsta is the best default for NeuroCumulus.com unless the team already has enterprise-standard WP Engine processes or wants Cloudways-level infrastructure control.

Development checklist and timeline

Estimated total: 190–240 hours

gantt
    title NeuroCumulus custom theme roadmap
    dateFormat  YYYY-MM-DD
    axisFormat  %b %d

    section Strategy
    Discovery and positioning     :a1, 2026-05-25, 7d
    IA and wireframes             :a2, after a1, 10d

    section Design
    Visual system                 :b1, after a2, 10d
    High-fidelity mockups         :b2, after b1, 8d

    section Build
    Theme foundation              :c1, after b1, 12d
    CPTs and structured content   :c2, after c1, 6d
    Blocks and patterns           :c3, after c2, 8d

    section Content
    Main page drafting            :d1, after a2, 8d
    Content entry and polish      :d2, after c3, 6d

    section Optimization
    SEO and schema                :e1, after d2, 4d
    Analytics and consent         :e2, after d2, 3d
    Accessibility and QA          :e3, after e1, 7d

    section Launch
    UAT and fixes                 :f1, after e3, 5d
    Production launch             :f2, after f1, 2d
    Training and handoff          :f3, after f2, 2d

Testing plan

Testing should combine manual review and tool-based validation. Google’s documentation supports using Rich Results Test and Search Console for structured data validation, Tag Assistant for consent-mode debugging, and Core Web Vitals tooling for ongoing performance monitoring.

Deliverables for developer and client handoff

The key outcome is not just a good-looking theme. It is a clear, technically credible, search-ready, accessible, and maintainable web presence that turns Neuro Cumulus from a default WordPress placeholder into a serious AI infrastructure brand.