Athenian Site Themes for WordPress
Overview
Product overview
Most WordPress sites treat theming as a scattered implementation problem. Colors live in a stylesheet, spacing values are buried in component CSS, dark mode becomes a one-off patch, and any new campaign or brand variant turns into another round of manual edits. Over time, visual consistency erodes and even small theme changes become slow, risky, and expensive.
Athenian Site Themes solves that by turning theme design into structured site data instead of scattered styling overrides. Administrators can define or import full theme payloads, set a default theme, output clean CSS variables to the frontend, and give users a polished theme switcher that persists their selection. The result is faster theme rollout, cleaner governance, and a more adaptable design system for WordPress.
Use cases
- Brand systems
- Theme configuration
- Frontend consistency
- Site styling
Developer
Developer starting point
This baseline documents Site Themes token and frontend architecture. It does not claim that a theme was activated, a production style was changed, or a cross-site visual result was exercised.
Ecosystem integration story
WordPress and custom themes
Athenian Site Themes is built to work with standard WordPress rendering patterns. It does not replace the active theme. It provides the token layer that the theme can consume, allowing existing templates and styles to shift toward a more structured, reusable design system.
Blocks, templates, and custom CSS
Because the plugin emits CSS variables rather than rigid component output, it fits cleanly into block themes, classic themes, custom templates, and hand-authored CSS. Teams can progressively adopt tokens without rewriting the whole site.
Plugin UI and frontend components
The same token definitions can support not only page design but also plugin surfaces, utility components, badges, cards, buttons, and other interface elements that need to remain visually aligned.
Brand variants, campaigns, and alternate modes
Athenian Site Themes makes it easier to support multiple brand looks, promotional themes, seasonal variants, or alternate presentation modes from one control layer instead of spinning up disconnected CSS branches.
Install
- Reviewed source folder: athenian-site-themes
- Plugin version reviewed: 1.2.2
- Local source inventory: 14 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-site-themes at baseline/devdocs-1.2.2-20261006e / 2dc25f6726fcc8aa39d4d757f01c2ac3ff9d184e.
- WordPress and the active site theme.
- Theme activation, frontend rendering, token persistence, and property-specific styling require separate target verification.
Configuration
- Working positioning — see the linked technical reference excerpt.
- Executive summary — see the linked technical reference excerpt.
- Core marketing message — see the linked technical reference excerpt.
- The problem Athenian Site Themes solves — see the linked technical reference excerpt.
- What Athenian Site Themes does — see the linked technical reference excerpt.
- Ecosystem integration story — see the linked technical reference excerpt.
- Why this matters commercially — see the linked technical reference excerpt.
- Key differentiators — see the linked technical reference excerpt.
- Suggested messaging pillars — see the linked technical reference excerpt.
- Short-form copy options — see the linked technical reference excerpt.
- Sales narrative — see the linked technical reference excerpt.
- Best-fit use cases — see the linked technical reference excerpt.
- Positioning statement — see the linked technical reference excerpt.
- Platform-focused primary functionality copy — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 1
- Static action/filter hooks detected in local PHP source: 11
- REST route registrations detected in local PHP source: 0
Shortcodes
- site_theme_switcher — site-theme-tokens-structured.php
REST Endpoints
- No register_rest_route calls were detected by the baseline scanner.
Hooks
- admin_enqueue_scripts — site-theme-tokens-structured.php
- admin_init — site-theme-tokens-structured.php
- admin_menu — site-theme-tokens-structured.php
- admin_notices — site-theme-tokens-structured.php
- language_attributes — site-theme-tokens-structured.php
- wp_ajax_nopriv_sttm_set_theme — site-theme-tokens-structured.php
- wp_ajax_sttm_generate_theme — site-theme-tokens-structured.php
- wp_ajax_sttm_poll_theme_generation — site-theme-tokens-structured.php
- wp_ajax_sttm_set_theme — site-theme-tokens-structured.php
- wp_enqueue_scripts — site-theme-tokens-structured.php
- wp_head — site-theme-tokens-structured.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: e7fbfd223775fcc2785112c50dc20cf3872d88a8292483e2a0beaf35853e3142
- Repository URL: https://github.com/Athenian-Brands/athenian-site-themes
- Repository reference: baseline/devdocs-1.2.2-20261006e
- Repository commit: 2dc25f6726fcc8aa39d4d757f01c2ac3ff9d184e
Source files include: assets/admin.css, assets/admin.js, assets/front.js, assets/switcher.css, athenian-site-themes.png, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/athenian-site-themes-marketing-document.md, docs/technical-marketing.md, site-theme-tokens-structured.php, site-theme-tokens-structured.zip, theme-packs/README.md, theme-packs/athenian-alternative-themes.json, uninstall.php
Troubleshooting
This baseline documents Site Themes token and frontend architecture. It does not claim that a theme was activated, a production style was changed, or a cross-site visual result was exercised.
- Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.
FAQ
What is this page intended to establish?
A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.
Is the linked repository baseline verified?
Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.
What remains for release-grade documentation?
Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.