How bonny/wordpress-simple-history works
Main Components
a. Core Plugin Architecture:
• Config System (class-config.php)
• Autoloader (class-autoloader.php)
• Main Plugin Class (class-simple-history.php)
b. Logging System:
• Logger Base Class (loggers/class-logger.php)
• Log Query Handler (class-log-query.php)
• Event Details System (event-details directory)
• Log Levels Handler (class-log-levels.php)
c. Services Layer:
• Database Setup
• REST API
• Admin Pages
• Scripts & Templates
• Dropins Loader
• WP CLI Commands
d. Frontend/UI Components:
• React Components (src/components/)
• Admin Bar Integration
• Dashboard Widget
• Settings Pages
Relationships and Data Flow
• WordPress Core ↔ Simple History Plugin
• Loggers → Database
• UI Components → REST API → Database
• Services → Core Components
• Dropins → Core Extension Points
Integration Points
Highlight:
• WordPress Action/Filter Hooks
• REST API Routes
• WP CLI Integration
• Database Tables
The plugin's modular architecture with clear separation between
• Core functionality
• Logging system
• UI components
• Service layer
The extensibility points
• Dropin system
• Logger system
• Event details framework
The modern stack using
• React for UI
• REST API for data access
• WordPress integration points
[WordPress Core]
• ↓
[Simple History Core]
• ↓
[Services Layer] → [Database]
• ↓
[Logging System] → [Event Details]
• ↓
[UI Components] → [REST API]
Notes about the PSR-3 logging standard implementation and the plugin's API for developers, as these are key architectural features mentioned in the README.