Owner: Engineering Team | Last Updated: 2026-01-30 | Status: Active
The WWAI WordPress Plugin integrates AI-powered text humanization directly into the WordPress admin interface. Content creators, bloggers, and site administrators can humanize their posts, pages, and other content without leaving WordPress. The plugin communicates with the WWAI Django REST API backend for all AI processing, and account integration is facilitated via a callback mechanism referenced in the web app's NextAuth.js authentication configuration.
Repository: To be confirmed when codebase is provided
Platform: WordPress (self-hosted)
Language: PHP
WordPress Compatibility: To be confirmed
| Technology | Purpose |
|---|---|
| PHP | WordPress plugin language |
| WordPress Plugin API | Core plugin framework |
| WordPress REST API | Internal WordPress communication |
| JavaScript | Admin UI interactivity |
Draft: Full dependency list, minimum PHP/WordPress versions, and build tooling will be documented when the codebase is analyzed.
| Feature | Description | Status |
|---|---|---|
| Text Humanization | AI-powered humanization within WordPress editor | Active |
| Post/Page Integration | Humanize content directly in the post editor (Classic or Gutenberg) | Active |
| Account Linking | Connected to WWAI user account for credits and billing | Active |
| Callback Authentication | WP plugin callback integration with web app auth | Active |
Draft: Complete feature set will be documented when the WordPress plugin codebase is analyzed.
WordPress Admin Dashboard
|
v
WWAI WordPress Plugin
|-- Admin Menu / Settings Page
|-- Editor Integration (Gutenberg Block or Classic Editor meta box)
|-- PHP Backend (API Client)
|-- JavaScript Frontend (Admin UI)
|
+---> WordPress Content APIs
| |-- Posts read/write
| |-- Pages read/write
| |-- Custom post types
|
+---> Django REST API (WWAI Backend)
|-- /api/feature/humanizer/ (text humanization)
|-- /api/user/* (account, credits)
|-- /api/payments/* (billing)
The WordPress plugin uses a callback-based authentication mechanism that integrates with the web app's NextAuth.js configuration:
WordPress Plugin WWAI Web App (NextAuth.js) Django Backend
| | |
|-- Initiate linking -------> | |
| |-- Auth flow (login/register) |
| |-- NextAuth callback config |
| <-- Callback with token ---- | |
| | |
|-- Store token locally | |
|-- API call with Bearer ------|-----------------------------> |
| | |-- Validate token
| <-- Response ----------------|------------------------------ |
Draft: The exact callback URL format, token exchange mechanism, and the specific NextAuth.js callback configuration for the WordPress plugin will be documented when both codebases are analyzed.
| Editor | Integration Type | Description |
|---|---|---|
| Gutenberg (Block Editor) | Custom Block or Sidebar Panel | Humanize selected text or entire content |
| Classic Editor | Meta Box or TinyMCE Button | Humanize content from the editor toolbar |
Draft: The specific editor integration approach will be confirmed when the codebase is analyzed.
| Component | Description |
|---|---|
| Settings Page | Plugin configuration, account linking, API key management |
| Admin Menu Item | WWAI entry in the WordPress admin sidebar |
| Dashboard Widget | Usage stats and credit balance (if applicable) |
The WordPress plugin communicates with the WWAI Django REST API backend:
application/jsonwp_remote_post() / wp_remote_get() functions| Endpoint Pattern | Purpose |
|---|---|
/api/feature/humanizer/ |
Text humanization |
/api/user/profile/ |
User profile and credit balance |
/api/user/token/refresh/ |
Token refresh |
Draft: Complete API endpoint mapping will be documented when the codebase is analyzed.
Draft: This section will be updated with project-specific details when the codebase is provided.
| Tool | Purpose |
|---|---|
| PHP 7.4+ (or 8.x) | Plugin runtime |
| WordPress (local install) | Development environment |
| Node.js | Build tooling (if applicable for JS/CSS assets) |
| Composer | PHP dependency management (if applicable) |
| Local WP or Docker | Local WordPress environment |
# 1. Clone the repository
git clone <repository-url>
# 2. Set up local WordPress environment
# Using Local WP, Docker, or MAMP/WAMP
# 3. Symlink or copy plugin to WordPress plugins directory
ln -s /path/to/plugin /path/to/wordpress/wp-content/plugins/wwai-humanizer
# 4. Activate the plugin
# Navigate to WordPress Admin > Plugins > Activate
# 5. Configure plugin settings
# Navigate to WWAI settings page and enter API credentials
# 6. If plugin has build step for JS/CSS assets:
npm install
npm run build
Draft: This section will be updated when the codebase is provided.
| Aspect | Details |
|---|---|
| Distribution Channel | WordPress Plugin Directory (wordpress.org) or direct distribution |
| Update Mechanism | WordPress auto-update system |
| Review Process | WordPress.org plugin review (if distributed via directory) |
| Versioning | Semantic versioning in plugin header |
Draft: Deployment process and release management will be documented when the codebase is analyzed.
Draft: This section will be populated with common issues and solutions when the codebase is analyzed.
| Issue | Possible Cause | Resolution |
|---|---|---|
| Plugin activation fails | PHP version incompatible | Check minimum PHP version requirements |
| Account linking fails | Callback URL incorrect | Verify WordPress site URL and callback configuration |
| Humanization not working | API token expired | Re-link account via plugin settings |
| Conflict with other plugins | Hook priority conflict | Check for JavaScript or PHP conflicts in debug log |
| Date | Author | Change |
|---|---|---|
| 2026-01-30 | Admin | Initial creation |
Up: WalterWrites