Athenian Font File Manager for WooCommerce
Overview
Product overview
Font handling becomes fragile when every plugin manages its own asset directory, naming rules, and discovery logic. One plugin scans a local folder, another expects a different JSON shape, a third depends on an outdated uploads path, and nobody has a reliable way to know which fonts are actually available in production. The result is duplicated assets, inconsistent font lists, broken previews, and unnecessary migration work whenever the stack evolves.
AFFM solves that by acting as the central font management service for the Athenian ecosystem. It provides managed uploads, a canonical registry manifest, grouped font outputs for known consumer patterns, REST access, public PHP helpers, and legacy migration tooling so the platform can work from one consistent source of font truth.
Use cases
- Shared font catalogs
- Print workflows
- 3D text consumers
- Managed asset operations
Developer
Developer starting point
This baseline documents the font-management and registry architecture. It does not claim that a production font upload, migration, public asset request, or consuming renderer has been exercised.
Ecosystem integration story
Athenian plugin ecosystem
AFFM is designed as shared infrastructure rather than a single-feature plugin. Its value increases as more Athenian plugins stop maintaining their own font directories and start consuming one shared registry.
Athenian PrintForge and 3D text consumers
AFFM explicitly supports grouped Troika and typeface outputs, making it a natural registry layer for plugins and interfaces that render text in canvas, WebGL, or configurable design experiences. Instead of discovering fonts from arbitrary folders, those consumers can request the exact grouped shape they already expect.
Existing APF integrations
AFFM includes compatibility helpers such as apf_get_typeface_fonts() and apf_get_troika_fonts(), which lowers migration friction for existing consumers that were built around APF-oriented helper names. This helps older integrations move toward the shared registry model without a full rewrite on day one.
Legacy font libraries
AFFM can scan configured legacy roots and fold those files into the registry alongside managed assets. It also provides a migration path to copy legacy files into the managed library, allowing teams to modernize gradually instead of forcing a risky cutover.
Headless and external consumers
Because AFFM exposes a manifest URL and public REST endpoints, external tools and frontend applications can consume the same font truth without direct WordPress filesystem access. That supports cleaner integration patterns for apps, configurators, and future service layers.
Install
- Reviewed source folder: athenian-font-file-manager
- Plugin version reviewed: 0.1.0
- Local source inventory: 13 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-font-file-manager at baseline/devdocs-0.1.0-20261006e / 38cd0133898b3ad885310cc3e30b638a2d0840c2.
- WordPress and the configured uploads filesystem.
- Font uploads, legacy migration, public asset availability, and consuming-plugin rendering 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 AFFM solves — see the linked technical reference excerpt.
- What AFFM 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: 0
- Static action/filter hooks detected in local PHP source: 12
- REST route registrations detected in local PHP source: 1
Shortcodes
- No static add_shortcode registrations were detected by the baseline scanner.
REST Endpoints
- athenian-fonts/v1 — includes/class-affm-rest.php
Hooks
- admin_enqueue_scripts — includes/class-affm-plugin.php
- admin_menu — includes/class-affm-plugin.php
- admin_post_affm_delete_family — includes/class-affm-plugin.php
- admin_post_affm_delete_file — includes/class-affm-plugin.php
- admin_post_affm_migrate_legacy — includes/class-affm-plugin.php
- admin_post_affm_rebuild_registry — includes/class-affm-plugin.php
- admin_post_affm_update_family — includes/class-affm-plugin.php
- admin_post_affm_upload_fonts — includes/class-affm-plugin.php
- init — includes/class-affm-plugin.php
- rest_api_init — includes/class-affm-plugin.php
- upload_mimes — includes/class-affm-plugin.php
- wp_check_filetype_and_ext — includes/class-affm-plugin.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 5e05ac773141f5cd657ffedf4772edde04c3859766ed811e463f2b529d85548d
- Repository URL: https://github.com/Athenian-Brands/athenian-font-file-manager
- Repository reference: baseline/devdocs-0.1.0-20261006e
- Repository commit: 38cd0133898b3ad885310cc3e30b638a2d0840c2
Source files include: README.md, assets/admin.css, athenian-font-file-manager-icon.png, athenian-font-file-manager.php, docs/athenian-font-file-manager-marketing-document.md, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, includes/class-affm-admin.php, includes/class-affm-paths.php, includes/class-affm-plugin.php, includes/class-affm-registry.php, includes/class-affm-rest.php, includes/functions-public.php
Troubleshooting
This baseline documents the font-management and registry architecture. It does not claim that a production font upload, migration, public asset request, or consuming renderer has been 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.