Rowdy Crowd

Site-specific · One plugin holding all custom functionality for the Rowdy Crowd WooCommerce site (AU + US from one install), with each feature in its own module.

What it does

Rowdy Crowd is moving from two Shopify stores (AU and US) to one WooCommerce site. This plugin holds the site's custom code. Planned modules include the custom-print product renderer and cart flow, quoting and tiered pricing. Project context and scope are in CLAUDE.md.

Each module has its own README with settings, hooks and files.

Requirements

Installation

1. Deploy the repository root to wp-content/plugins/rowdy-crowd/.
2. Activate Rowdy Crowd.
3. Administrators should see a green "Hello World from Rowdy Crowd" notice, which confirms the deployment.
4. Follow each module's README for its setup (e.g. geolocation hosting setup).

Configuration

There is no plugin-wide settings page. Configuration is per module (see each module README) and through wp-config.php constants such as ROWDY_CROWD_TEST_COUNTRY (geolocation testing).

Usage

CSS classes aunz / usa on any element (Elementor: Advanced → CSS Classes) limit it to one region.

How it works

Data model

Core: none. Modules document their own (e.g. geolocation uses the rowdy_crowd_region cookie and no database storage).

Request flow

1. rowdy-crowd.php defines the constants, registers the autoloader and boots RowdyCrowd\Core\Plugin on plugins_loaded.
2. Plugin instantiates every class in Plugin::MODULES (filterable with rowdy_crowd_modules) and calls register() on those whose is_enabled() returns true.
3. rowdy_crowd_loaded fires. Get a loaded module with RowdyCrowd\Core\Plugin::instance()->get_module( 'module-id' ).

Autoloading follows WordPress file naming: RowdyCrowd\Core\Foo_Bar → includes/class-foo-bar.php; RowdyCrowd\Modules\Some_Module\Foo_Bar → modules/some-module/class-foo-bar.php. Details: includes/README.md and modules/README.md.

Endpoints

Front end

Core loads no assets. Modules enqueue their own (e.g. geolocation prints an inline redirect script and switcher CSS/JS).

File structure

rowdy-crowd.php              Plugin header, global constants, bootstrap
includes/                    Core (RowdyCrowd\Core): Autoloader, Plugin, abstract Module   → includes/README.md
modules/                     One folder per feature                                      → modules/README.md
  geolocation/               AU/US regions, redirect, switcher                            → modules/geolocation/README.md
  hello-world/               Deployment check placeholder                                 → modules/hello-world/README.md
CLAUDE.md                    Project context, coding standards, git workflow

Hooks

Module hooks are listed in each module's README (e.g. rowdy_crowd_region, rowdy_crowd_region_domains).

Gotchas

• Pages are cached by Kinsta. Per-visitor logic can't rely on PHP running each page view. Use the domain, an uncached REST endpoint, or client-side JS (the geolocation module is the pattern to follow).
• Two domains, one install. Carts and logins don't carry across .com and .com.au. Content saved with absolute URLs keeps the domain it was created on.
• Every new module must be registered in Plugin::MODULES and listed in modules/README.md, or it won't load.
• WooCommerce-dependent modules must return false from is_enabled() when Woo isn't active, so the plugin never fatals.
• PHP isn't installed locally, so code can't be linted or run before deploying. Test on staging.
• Remove the hello-world module before launch.

Development

• Project context, coding standards and git workflow: CLAUDE.md.
• Versioning: bump ROWDY_CROWD_VERSION and the plugin header together.
• New feature: add a module (see modules/README.md) with its own README, and update the module table here.
• Testing: deploy to staging; for geolocation use ROWDY_CROWD_TEST_COUNTRY in wp-config.php.

Changelog