Athenian Font File Manager for WooCommerce
product details.
Athenian Font File Manager for WooCommerce organizes font uploads, metadata, preview use, and product-design availability for WooCommerce customization and production workflows. It helps teams keep customer-facing design tools, print workflows, licensing context, and production output using approved font assets while keeping data, permissions, and automation aligned with the broader Athenian Platform Ecosystem.
Athenian Font File Manager is the shared font asset and registry layer for the Athenian plugin ecosystem. It gives WordPress-based platform builds one reliable place to store, index, manage, migrate, and serve font assets so downstream plugins, frontend tools, and rendering systems can work from a single trusted catalog instead of scanning scattered plugin folders or maintaining duplicate font manifests.
Instead of letting each plugin define its own font directory, naming rules, registry shape, and compatibility logic, AFFM centralizes the font lifecycle. It supports managed font uploads, legacy font detection, registry rebuilding, family-level organization, cached manifest output, REST access, and PHP helper functions for plugin consumers that need stable font lookup.
The plugin is especially useful for Athenian PrintForge, 3D text rendering, Troika-based interfaces, typeface JSON consumers, configurators, product builders, and frontend applications that need consistent font availability without relying on direct filesystem assumptions. It can expose grouped outputs for Troika-ready fonts, typeface JSON assets, full registry consumers, family lookups, and direct manifest access.
For internal teams and implementation partners, Athenian Font File Manager reduces duplicated assets, broken previews, inconsistent font lists, and migration friction. It turns fonts into a shared platform service with admin-managed upload, rebuild, inspect, migrate, and delete workflows inside WordPress.
Font Registry
Create One Shared Source of Truth for Platform Fonts
AFFM centralizes managed font storage, family organization, cached indexing,
and registry output so Athenian plugins can consume one trusted font catalog.
| Layer | Platform Value |
|---|---|
| Managed Library | Stores shared fonts in a dedicated uploads location organized by font family. |
| Registry Manifest | Builds a cached registry.json catalog for faster, stable font lookups. |
| Family Lookup | Allows consumers to request specific font families by slug or registry reference. |
| Legacy Sources | Indexes supported legacy font roots while teams migrate toward the managed library. |
- Reduce duplicated font files across plugins and repositories.
- Replace repeated directory scans with one cached registry layer.
- Keep managed and legacy font assets visible from the same catalog.
- Give Athenian plugins a stable font contract instead of filesystem assumptions.
Font Operations
Manage Font Uploads, Rebuilds, Legacy Inventory, and Cleanup
AFFM moves font administration into WordPress with operational tools for uploading,
indexing, detecting legacy sources, migrating assets, rebuilding the registry,
and removing managed font families cleanly.
Manage TTF, OTF, WOFF, WOFF2, and supported typeface JSON assets
Detect legacy font roots and copy supported files into the managed library
Rebuild the registry and delete managed font families from admin tools
| Workflow | Result |
|---|---|
| Upload | Admins add supported font files through a managed WordPress interface. |
| Inspect | Teams can review managed inventory and legacy font availability. |
| Rebuild | The registry manifest can be regenerated when font assets change. |
| Clean Up | Managed font families can be removed without manually editing server folders. |
- Move font management out of ad hoc server maintenance.
- Support gradual migration from older upload structures.
- Give operators a repeatable workflow for catalog updates.
- Reduce broken previews caused by stale paths or inconsistent manifests.
API & Consumers
Serve Fonts to Plugins, Frontends, and Rendering Systems
AFFM exposes the shared font catalog through PHP helpers, REST endpoints,
grouped consumer outputs, family lookups, and direct manifest access for
plugin, app, and frontend integrations.
| Consumer Pattern | How AFFM Supports It |
|---|---|
| Troika Fonts | Provides grouped Troika-ready font outputs for WebGL and 3D text workflows. |
| Typeface JSON | Serves typeface-compatible assets for consumers expecting JSON font references. |
| PHP Helpers | Offers functions such as registry, grouped, Troika, typeface, and manifest helpers. |
| REST Access | Publishes font catalog endpoints for headless, frontend, and service consumers. |
Shared font infrastructure:
AFFM lets Athenian plugins stop solving font storage, indexing, compatibility,
and delivery separately by providing one registry contract for managed assets,
legacy sources, and frontend rendering needs.
- Expose full registry, grouped, Troika, typeface, family, and manifest access patterns.
- Support APF-oriented helper aliases to reduce migration friction.
- Let external tools consume font data without direct filesystem access.
- Provide a reusable font foundation for PrintForge, configurators, and design tools.