ATHENIAN PLUG-IN SYSTEM
Athenian DevDocs turns plugin source material into structured product and developer documentation.
Scan installed plugins and source assets, extract hooks, shortcodes, routes, classes, files, and versions, use AI-assisted templates, and publish polished documentation through WordPress content and front-end renderers.
Plugin scanning
AI templates
Version snapshots
Front-end docs
Documentation operations layer
Use a documentation builder dashboard showing plugin scan manifest, source files, AI template controls, generated doc JSON, table of contents, and front-end preview.
PRODUCT SNAPSHOT
Documentation closer to the code and easier to publish.
Position DevDocs as the documentation workflow for a portfolio of WordPress and WooCommerce plugins.
For plugin product teams
Built for teams shipping many custom plugins that need aligned marketing, developer, support, and release documentation.
Replaces scattered documentation habits
Reduces drift between code, README files, marketing copy, internal notes, release messages, and support guidance.
Connects scanners, sources, AI, CPTs, shortcodes, and renderers
Turns plugin source material into structured documentation stored and presented in WordPress.
Delivers repeatable documentation operations
The scan-to-snapshot-to-generate-to-publish flow can scale across a plugin suite.
FROM FRICTION TO FLOW
Show how the plug-in changes day-to-day work.
The before/after framing makes the value obvious before visitors read feature details.
CURRENT WORKFLOW
Before DevDocs
-> Product, developer, and support docs are written separately.
-> Hooks, routes, shortcodes, and class structures are discovered manually.
-> Version changes are hard to connect to documentation refreshes.
-> Publishing docs requires hand-built pages and one-off formatting.
CONNECTED WORKFLOW
After DevDocs
-> Plugin scans produce documentation-ready manifests.
-> AI templates generate structured product and developer content from source assets.
-> Snapshots preserve source state by version.
-> Front-end renderers and shortcodes publish docs inside WordPress.
FEATURE MODULES
Six capabilities that make plugin documentation operational.
The local code shows DevDocs CPTs, presets, AI templates, source/meta boxes, installed plugin pages, front-end renderer, product tabs, and shortcodes.
Plugin manifest scanning
Extract files, classes, functions, hooks, filters, shortcodes, REST routes, metadata, and version context.
Source asset ingestion
Generate documentation from installed plugins, ZIP snapshots, attached source files, README content, and configuration assets.
AI-assisted templates
Use reusable templates and schema expectations so generation produces reviewable structured documentation.
Version snapshots
Preserve plugin source states so documentation refreshes can align with releases and code changes.
Native WordPress content
Stores docs, presets, and templates in custom post types with admin builder controls.
Front-end presentation
Publishes docs through renderers, shortcodes, product tabs, TOC, FAQ, changelog, and tabbed marketing/developer layouts.
WORKFLOW
Explain the product as a sequence from setup to outcome.
The workflow section helps buyers understand how the plug-in fits into real operations.
01
Scan
Inspect plugin source, installed plugins, ZIPs, README files, and code structures.
02
Generate
Apply AI templates and schema-oriented output rules to create structured doc content.
03
Review
Edit generated JSON/content, attach sources, preserve snapshots, and refine presets.
04
Publish
Render front-end docs through shortcodes, product tabs, and WordPress documentation pages.
VISUAL DIRECTION
Use real product visuals, then add compact callouts.
Keep screenshots specific to the product and use the shared compact card system for consistency.
Plugin scan manifest
Show detected files, hooks, REST routes, shortcodes, classes, and version metadata.
AI template builder
Show structured prompt/template controls and generated canonical doc JSON.
Front-end documentation
Show hero, TOC, FAQ, changelog, marketing tab, and developer tab in a polished documentation layout.
ECOSYSTEM
Platforms and systems this plug-in touches.
Use official marks where licensing allows; otherwise keep these as Material-style text/logo slots.
WordPress
WooCommerce
Plugins
Hooks
REST Routes
Shortcodes
AI Templates
Snapshots
Docs CPT
Product Tabs
OUTCOMES
Close with the operational change the buyer should expect.
These outcomes should stay practical and tied to the operational friction the plug-in removes.
Reduce documentation drift
Docs can start from the same source material the plugin team actually ships.
Scale a plugin portfolio
A repeatable scan/generate/publish workflow is stronger than writing every plugin page by hand.
Support evaluation and handoff
Marketing, developer, support, and customer-facing documentation can share one structured base.
Ready to turn plugin source into maintainable product documentation?
This plugin-linked page is based on WooCommerce product 90017, local folder athenian-devdocs, and available plugin documentation/code signals. Use the product page for licensing and purchase details.