Athenian DevDocs
Overview
Product overview
Plugin documentation usually breaks down for the same reason product documentation breaks down everywhere else: the truth is scattered. Product positioning lives in a marketing brief, setup steps live in internal notes, API behavior lives in code, changelog details live in release messages, and support teams are left reconciling the gaps after the plugin ships.
Athenian DevDocs solves that by creating a documentation workflow around the plugin itself. It can scan installed WordPress and WooCommerce plugins, extract key structural information such as files, classes, hooks, shortcodes, and REST routes, preserve source snapshots by version, and use AI templates to generate structured documentation that supports both marketing copy and developer reference content. The result is a documentation system that is closer to the code, easier to update, and better aligned with how plugin teams actually ship.
Use cases
- Product documentation
- Developer onboarding
- Implementation references
- Plugin operations
Developer
Developer starting point
This baseline documents the DevDocs plugin architecture. It does not claim that every admin workflow, rendering variant, importer path, or product-link lifecycle has been exercised.
Ecosystem integration story
WordPress and WooCommerce plugin teams
Athenian DevDocs is built for plugin-driven product environments. It helps WordPress and WooCommerce teams document plugin capabilities in a way that reflects how those products are actually built: through code, hooks, admin screens, REST endpoints, and evolving release versions.
Athenian platform plugins
Within the Athenian ecosystem, DevDocs can serve as the shared documentation layer for plugin products that need both market-facing explanation and technical reference material. Instead of documenting each plugin through a disconnected workflow, teams can use a common system for scan, generation, storage, and presentation.
AI-assisted documentation operations
Athenian DevDocs uses prompt templates and structured output expectations to make AI useful in a controlled documentation workflow. Rather than generating free-form copy with no constraints, it pushes generation toward defined schemas and reusable document shapes that can be reviewed and refined.
Release and version management workflows
The manifest and snapshot model makes DevDocs valuable beyond publishing. It can support internal release validation, version-aware doc refreshes, and a more disciplined documentation process tied to shipping artifacts.
Install
- Reviewed source folder: athenian-devdocs
- Plugin version reviewed: 0.4.4
- Local source inventory: 30 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-devdocs at baseline/devdocs-0.4.4-20261006g / ec7bce87d586dde280d89492742ae3406057c673.
- WordPress, WooCommerce, and the active site theme.
- Documentation import, admin editing, product linking, frontend rendering, and repository-provenance workflows 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 DevDocs solves — see the linked technical reference excerpt.
- What Athenian DevDocs 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: 2
- Static action/filter hooks detected in local PHP source: 14
- REST route registrations detected in local PHP source: 1
Shortcodes
- ath_devdocs — includes/Frontend/Shortcodes.php
- ath_devdoc — includes/Frontend/Shortcodes.php
REST Endpoints
- ath-devdocs/v1 — includes/Rest/Rest.php
Hooks
- add_meta_boxes — includes/Admin/MetaBoxes.php
- admin_enqueue_scripts — includes/Plugin.php
- admin_init — includes/Plugin.php
- admin_menu — includes/Admin/Admin.php
- admin_post_ath_devdocs_save_settings — includes/Admin/Settings.php
- body_class — includes/Content/CPT.php
- init — includes/Plugin.php
- rest_api_init — includes/Rest/Rest.php
- save_post_ — includes/Admin/MetaBoxes.php
- the_content — includes/Content/CPT.php
- the_content — includes/Frontend/ProductDocs.php
- woocommerce_after_single_product_summary — includes/Frontend/ProductDocs.php
- woocommerce_product_tabs — includes/Frontend/ProductDocs.php
- wp_enqueue_scripts — includes/Plugin.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 52989d68197acedaec21a73d79cc7fb4d4d5114ce99a8b845141095836c87586
- Repository URL: https://github.com/Athenian-Brands/athenian-devdocs
- Repository reference: baseline/devdocs-0.4.4-20261006g
- Repository commit: ec7bce87d586dde280d89492742ae3406057c673
Source files include: README.md, assets/css/admin.css, assets/css/frontend.css, assets/js/admin.js, assets/js/frontend.js, athenian-devdocs-icon.png, athenian-devdocs-marketing-document.md, athenian-devdocs.php, athenian-devdocs.zip, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/technical-marketing.md, includes/Admin/Admin.php, includes/Admin/MetaBoxes.php, includes/Admin/PluginsPage.php, includes/Admin/Settings.php, includes/Autoloader.php, includes/Content/CPT.php, includes/Content/PresetCPT.php, includes/Content/TemplateCPT.php, includes/Frontend/ProductDocs.php, includes/Frontend/Renderer.php, includes/Frontend/Shortcodes.php, includes/Plugin.php, includes/Plugins/Analyzer.php, includes/Plugins/Installed.php, includes/Rest/OpenAIClient.php, includes/Rest/Rest.php, …
Troubleshooting
This baseline documents the DevDocs plugin architecture. It does not claim that every admin workflow, rendering variant, importer path, or product-link lifecycle 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.