Opens in a new tab
Deliver toTennessee
0 0 0Cart
Get a Project Quote

Athenian Plug-in Notes

v1.0.0 October 6, 2026
Contextual plugin notes and administrative reference surfaces for maintaining WordPress operations.

Overview

Product overview

Most WordPress sites accumulate plugins faster than they accumulate operational discipline. Teams inherit unfamiliar extensions, forget why a plugin was enabled, lose update caveats in chat threads, and deactivate tools without recording the reason or downstream impact. Over time, the Plugins screen becomes a list of technical dependencies with no usable institutional memory attached to it.

APN solves that by embedding persistent context directly into plugin management. It gives administrators a fast way to document why a plugin exists, what risks it carries, who owns it, whether it has been reviewed, and why it was disabled. Instead of forcing plugin decisions into ad hoc spreadsheets or tribal knowledge, APN keeps those decisions attached to the plugin itself where admins actually work.

Plugin-scoped notes, metadata, and administrative context.
Admin UI, AJAX, REST, and frontend display components.
Source-documented persistence and role-aware extension areas.
A baseline for later note creation, permissions, and rendering verification.

Use cases

  • Plugin maintenance
  • Operational notes
  • Admin context
  • Developer handoff

Developer

Developer starting point

This baseline documents Plug-in Notes code and extension surfaces. It does not claim that a live note, role-gated action, REST request, or frontend rendering path has been exercised.

Ecosystem integration story

WordPress admin

APN is built to live inside native WordPress admin rather than alongside it. It extends the existing Plugins screen, uses familiar row actions and admin patterns, and keeps plugin notes within the operational workflow teams already use.

Plugin lifecycle management

APN complements activation, deactivation, update review, and plugin audits by attaching human context to those lifecycle events. It does not replace plugin management. It makes plugin management more accountable.

Multisite environments

APN stores note context with blog awareness while using a shared custom table, making it a practical fit for multisite operators who need per-site plugin context without creating separate note systems for every environment.

Operations and support teams

APN gives support, engineering, and site-operations teams a shared surface for runbook notes, dependency flags, ownership tracking, and review history. This reduces handoff friction when plugin issues need investigation or approval.

Install

Source and dependencies
  • Reviewed source folder: athenian-plugin-notes
  • Plugin version reviewed: 1.0.0
  • Local source inventory: 24 files (temporary, test, and Git metadata excluded).
  • GitHub baseline: https://github.com/Athenian-Brands/athenian-plugin-notes at baseline/devdocs-1.0.0-20261006g / 65e4962727dc2249642f352504c9b18bba9a917f.
  • WordPress and the configured administrator roles.
  • Note persistence, permissions, AJAX actions, REST exposure, and frontend display require separate target verification.

Configuration

Implementation reference sections
  • 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 APN solves — see the linked technical reference excerpt.
  • What APN 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.
  • Product-focused primary functionality copy — see the linked technical reference excerpt.

Usage

Detected extension surface
  • Shortcodes detected in local PHP source: 1
  • Static action/filter hooks detected in local PHP source: 26
  • REST route registrations detected in local PHP source: 1

Shortcodes

Detected shortcodes
  • role_discount_display — includes/class-role-discounts.php

REST Endpoints

Detected REST routes
  • ath-pricing/v1 — includes/class-rest-role-discount-endpoint.php

Hooks

Detected hooks
  • add_meta_boxes — includes/class-admin-ui.php
  • admin_enqueue_scripts — includes/class-admin-ui.php
  • admin_enqueue_scripts — includes/class-apn-admin.php
  • admin_footer-plugins-network.php — includes/class-apn-admin.php
  • admin_footer-plugins.php — includes/class-apn-admin.php
  • admin_init — includes/class-role-discounts.php
  • admin_menu — includes/class-role-discounts.php
  • ath/apc/role_discount_for_price — includes/class-role-discounts.php
  • manage_plugins_columns — includes/class-apn-admin.php
  • manage_plugins_custom_column — includes/class-apn-admin.php
  • plugins_loaded — athenian-plugin-notes.php
  • plugin_action_links — includes/class-apn-admin.php
  • rest_api_init — includes/class-rest-role-discount-endpoint.php
  • save_post_product — includes/class-admin-ui.php
  • tiered_pricing_table_rules — includes/class-role-discounts.php
  • tiered_pricing_table_rules — includes/class-rules-store.php
  • woocommerce_before_add_to_cart_form — includes/class-frontend-ui.php
  • woocommerce_product_after_variable_attributes — includes/class-admin-ui.php
  • woocommerce_save_product_variation — includes/class-admin-ui.php
  • woocommerce_single_product_summary — includes/class-frontend-ui.php
  • wp_ajax_apf_role_discount — includes/class-rest-role-discount-endpoint.php
  • wp_ajax_ath_apn_delete_note — includes/class-apn-ajax.php
  • wp_ajax_ath_apn_get_note — includes/class-apn-ajax.php
  • wp_ajax_ath_apn_save_note — includes/class-apn-ajax.php
  • wp_ajax_nopriv_apf_role_discount — includes/class-rest-role-discount-endpoint.php
  • wp_enqueue_scripts — includes/class-frontend-ui.php

Data Model

Persistence and integration boundary
  • Ecosystem integration story — described in the local technical reference.

API Reference

Source inventory and provenance
  • Local source digest: 42af33c2bf02ed51d7b78d313737dca5ef13bf74e0e106dd269965b930125e64
  • Repository URL: https://github.com/Athenian-Brands/athenian-plugin-notes
  • Repository reference: baseline/devdocs-1.0.0-20261006g
  • Repository commit: 65e4962727dc2249642f352504c9b18bba9a917f
  • Source files include: apn-marketing-document.md, assets/admin.css, assets/admin.js, assets/css/admin.css, assets/css/apc-cart-tier-upsells.css, assets/css/frontend-tiers.css, assets/js/admin.js, assets/js/apc-cart-tier-upsells.js, assets/js/frontend-tiers.js, athenian-plug-in-notes-icon.png, athenian-plugin-notes.php, athenian-plugin-notes.zip, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, includes/class-admin-ui.php, includes/class-apn-admin.php, includes/class-apn-ajax.php, includes/class-apn-db.php, includes/class-frontend-ui.php, includes/class-plugin.php, includes/class-rest-role-discount-endpoint.php, includes/class-role-discounts.php, includes/class-rules-store.php, readme.txt

Troubleshooting

Baseline review boundary
  • This baseline documents Plug-in Notes code and extension surfaces. It does not claim that a live note, role-gated action, REST request, or frontend rendering path 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.

Changelog

1.0.0 2026-10-06