developer tools
BeaconWP Dev Tools
Runtime inspection tools for seeing how BeaconWP pages actually render.
BeaconWP Dev Tools is a developer-focused module for inspecting frontend render behavior, resolved templates, runtime context, hooks, assets, and capture evidence inside a BeaconWP-powered WordPress site.
What Dev Tools Does
BeaconWP Dev Tools helps site builders and developers see what actually happened during a frontend page render. Instead of guessing which template, pack, hook, or asset path was used, the module captures runtime evidence and presents it in an inspection interface.
The module is built for troubleshooting BeaconWP sites, verifying page rendering behavior, checking theme pack output, confirming frontend template resolution, and preparing support-ready diagnostic data.
Frontend Capture
Launches a real frontend render request and captures runtime evidence from the actual page load.
Template Inspector
Shows the resolved template path, template file, evidence source, and whether the detected file exists.
Runtime Context
Reports BeaconWP runtime state, pack context, request details, and relevant render information.
Hook Timeline
Displays captured frontend hook activity so render flow can be reviewed more clearly.
Asset Inspector
Lists captured frontend scripts and styles, including handles, sources, versions, and dependencies.
Support Exports
Provides exportable snapshots and support bundles for debugging, QA, and handoff workflows.
Current Status: 1.0.41 Capture UX
BeaconWP Dev Tools is currently focused on stabilizing the capture experience, improving feedback after capture attempts, and making the admin inspection flow clearer when no completed render evidence is available.
The current build keeps the module root, entitlement slug, BeaconWP add-on contract, and existing inspection model stable while improving the way capture status is reported to the user.
Recent Improvements
- Shared capture status messaging
- Visible capture status notices after capture return states
- Dedicated live capture feedback region
- Timeout status handling for frontend capture launches
- Cleaner debug/probe output handling
- Stable BeaconWP add-on contract preservation
Current Build Role
This version is focused on making Dev Tools easier to operate during real capture workflows. The goal is to reduce confusion when captures are pending, completed, timed out, or unavailable.
How the Workflow Works
- Open BeaconWP Dev Tools inside WordPress admin.
- Select or enter a target page or frontend URL.
- Launch a frontend render capture.
- Allow the capture window to complete or return status.
- Review the captured template, runtime context, hooks, assets, and diagnostics.
- Export a snapshot or support bundle if needed.
What It Helps Diagnose
- Wrong page template rendering
- Theme pack assignment problems
- Unexpected frontend layout behavior
- Missing or incorrect resolved template evidence
- Frontend hooks not firing as expected
- Assets loading from unexpected sources
- BeaconWP runtime detection issues
- Support cases requiring exportable evidence
For Site Builders
Dev Tools helps confirm whether a page is rendering through the expected BeaconWP path, theme pack, template, or frontend runtime behavior.
For Developers
Dev Tools provides structured inspection data for debugging templates, hooks, assets, capture state, and frontend render evidence.
Future Direction
BeaconWP Dev Tools can grow into a deeper inspection suite for BeaconWP sites and modules. Future versions may include saved capture history, side-by-side capture comparison, stronger module-aware diagnostics, more advanced asset analysis, expanded hook visibility, and clearer support-report generation.
The long-term role is to make BeaconWP easier to debug, support, and verify as the platform expands through modules, visual packs, cloud services, and more advanced frontend systems.
Part of the BeaconWP module ecosystem.
Dev Tools supports BeaconWP by making frontend rendering behavior easier to inspect, verify, and troubleshoot.