WP Manifestindependent plugin directory
manifest / editor / aggressive-blocks

Aggressive Blocks

Reusable Gutenberg blocks extracted from Aggressive Apparel, with WordPress VIP-oriented quality gates

by The Aggressive Network, LLC · github.com/theaggressive/aggressive-blocks · website

★ 0stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/theaggressive/aggressive-blocks/archive/refs/heads/main.zip
Readme github.com/theaggressive/aggressive-blocks ↗

Reusable Gutenberg blocks extracted from the Aggressive Apparel WordPress theme.

The plugin is developed and tested against WordPress VIP Coding Standards. It is not WordPress VIP certified unless Automattic has issued that approval.

Requirements

  • WordPress 7.0 or later
  • PHP 8.2 or later
  • Node 24 and pnpm 11 for development

Local development

WordPress Studio is the local site. GitHub Actions runs the Docker lanes.

pnpm install --frozen-lockfile
composer install
pnpm qa:fast

pnpm qa:fast is the pre-push check. It does not start containers. pnpm qa rehearses the same wp-env lanes CI runs. The WordPress floor and screenshot lanes (pnpm ci:floor, pnpm ci:visual) run WordPress natively, so they also work without Docker once pnpm build && bash bin/release/package.sh has built aggressive-blocks.zip.

For browser tests without Docker, pnpm test:e2e:studio runs Playwright against your Studio site. Opt the site in once with touch <site>/.aggressive-blocks-e2e-site; the script restores everything it changes. Pass Playwright arguments through, e.g. pnpm test:e2e:studio tests/e2e/modal.spec.ts.

Report vulnerabilities privately as described in SECURITY.md. Release notes live on the Releases page.

See docs/ci.md for workflows, required branch checks, the PHP/WordPress matrix, packaging, and VIP-oriented gates.

Migrating from Aggressive Apparel

2.0.0 removed the aggressive-apparel/* block names that 1.x kept as hidden aliases. Content that still uses them does not render. Rewrite it to aggressive-blocks/* before updating:

wp aggressive-blocks migrate-blocks --dry-run
wp aggressive-blocks migrate-blocks

The command rewrites posts and block widgets. It renames only the blocks this plugin owns, leaves every other byte as saved, and is safe to rerun. docs/migration.md states the contract and how it is tested.

Updates

The plugin updates from this repository's GitHub releases through WordPress's own plugin updates, with every package checked against its release's SHA-256 checksum. It stays off on git checkouts, local/development environments, and sites with DISALLOW_FILE_MODS. See docs/updates.md.

Build

pnpm build

The production build emits block assets, Interactivity API modules, PHP render files, *.asset.php sidecars, icons, and build/blocks-manifest.php. Runtime never compiles these files.

Package

CI builds an allowlisted ZIP and installs that ZIP, not the source checkout, before a release is published. Merging to main does not publish. A release is a manual CI run on main with publish enabled.

Packaging stamps the release version into the plugin header, the AGGRESSIVE_BLOCKS_VERSION constant, and the readme's Stable tag. After publishing, CI opens a pull request that writes the same version back to main, and proves the release installs through the plugin's own updater from an older install. See docs/ci.md.