WPAlloy Blocks

PLANNED · WPALLOY BUILD

Native components that extend WordPress instead of replacing it.

WPAlloy Blocks is planned as a focused collection of reusable Gutenberg components that share design tokens, accessibility rules and performance discipline across MachAxis, Ready Sites and Solution Packs.

ONE DESIGN CONTRACT

Advanced components without a second page-builder universe.

WordPress-native

Core blocks remain first-class. WPAlloy adds a custom block only where the native editor cannot reasonably express the capability or where the component has meaningful behavior, data or state.

Design-aware

Blocks are intended to inherit MachAxis colors, typography, spacing, radii, shadows, responsive rules and Style Recipes instead of shipping isolated styling systems.

Portable

Ordinary content should remain understandable in WordPress structures, avoiding shortcode-style lock-in and unnecessary proprietary runtime dependencies.

PLANNED COMPONENT FAMILIES

Reusable building blocks for richer WordPress sites.

Interaction

Accordions, tabs, advanced modals and other structured interactive components with shared keyboard, focus and motion behavior.

Content & proof

Testimonials, timelines, comparisons, pricing and progress components designed to reuse the site design system.

Media & data

Advanced galleries, sliders, charts, maps and hotspots where native blocks need a specialist component.

Vertical components

Industry-aware components can be packaged into Ready Sites and Solution Packs without forking the underlying MachAxis engine.

Built to stay fast when the catalogue grows.

Capability-aware assets

Scripts and styles should load because a page uses a capability, not merely because WPAlloy Blocks is installed.

Server-first rendering

Components should prefer semantic HTML, CSS and progressive JavaScript rather than requiring a heavy frontend framework for ordinary rendering.

Catalogue isolation

Adding more components to WPAlloy must not materially increase the runtime cost of pages that do not use them.

Accessibility is part of the component contract.

Each WPAlloy-owned interactive component is intended to define its semantic role, keyboard and focus behavior, labels, states, motion rules and required properties. The goal is to make the accessible implementation the normal implementation—not an optional overlay added afterwards.

  • Keyboard and visible-focus behavior
  • Reduced-motion support
  • Semantic HTML before ARIA simulation
  • Design-token-aware contrast and interaction states
  • Block and component health checks for regressions

Planned, not yet available.

The first component set, editor UX, compatibility matrix, free/Pro packaging and release gates still require implementation and validation. WPAlloy Blocks will be released only when it improves site-building capability without compromising WordPress portability, accessibility or runtime discipline.