Since I was able to use AI to write a python based system for creating and posting AI generated cars I decided that I could also create a WordPress plugin to do the same.

This was even easier.

Building an AI Car Content Generator WordPress Plugin: A Development Conversation

A transcript of the technical discussion and decision-making process behind creating a WordPress plugin to automate AI-generated car content

The Initial Request

Human: I have a python system that uses stability to create car images and generates text descriptions. It then posts these to my wordpress site and to my facebook page. I want to make a wordpress plugin that does the same. I want Stability to create car images, the load those into the wordpress media library and generate an AI description of the car. Then post to facebook and to wordpress. Can you do that

Claude: I’ll create a comprehensive WordPress plugin that replicates your Python system’s functionality. This plugin will generate car images using Stability AI, upload them to your WordPress media library, create AI descriptions, and post to both WordPress and Facebook.

[Claude then created the main plugin file with full functionality]

Claude: I’ve created a comprehensive WordPress plugin that replicates your Python system’s functionality while providing a professional admin interface. The plugin includes:

🎨 AI Image Generation: Creates professional car images using Stability AI
📝 Smart Descriptions: Generates engaging content with OpenAI GPT
📱 Facebook Integration: Automatically posts to your Facebook page
📚 Media Library: Uploads images directly to WordPress media library
⏰ Automation: Schedule automatic content generation
🎛️ Customizable: Multiple content tones and settings
📊 Analytics: Track generated posts and performance

[Additional template files, JavaScript, CSS, and documentation were created]

Understanding the Development Context

Human: Two things, 1. the python system is on a different server so you migration will not work. 2. give me a bash script that creates the plugin directory structure with placeholder files

Claude: You’re absolutely right about the migration tool. Let me create a bash script that builds the complete plugin directory structure with all the actual files.

[Claude created a comprehensive bash script that builds the entire plugin]

Human: The plugin code is being “developed” on my local server (where the python code is). Once the plugin code is done in a local folder I will zip it for installation to my wordpress.

Claude: Ah, that makes much more sense! You’re developing locally and then will zip it up for WordPress installation. Let me create a bash script that builds the complete plugin with all the actual code files.

[Claude updated the script to be a complete plugin builder]

Reviewing the Configuration

Human: show me my keys etc

Claude: Based on your provided .env files, here are your current API keys and credentials:

WordPress Credentials:

WP_SITE_URL=https://robertjwallace.com
WP_USERNAME=robertjwallace
WP_PASSWORD=**************************

Facebook API Credentials:

FB_APP_ID=************
FB_APP_SECRET=*************************
FB_PAGE_ID=629072793629302
FB_ACCESS_TOKEN=[Long token string]
FB_PAGE_TOKEN=[Long token string]

Configuration Settings:

POST_FREQUENCY=24  # Hours between posts (Daily)
MAX_POSTS_PER_DAY=1
FB_TARGET_ID=10238652981967062
FB_TARGET_TYPE=user

Missing Keys (You’ll Need These):

STABILITY_API_KEY=[Your Stability AI key - starts with sk-]
OPENAI_API_KEY=[Your OpenAI key - starts with sk-]

WordPress Plugin Mapping: When you configure the WordPress plugin, use these values:

Facebook App ID: ********************
Facebook App Secret: **********************
Facebook Page ID: ********************
Facebook Page Access Token: [Your long token]
Posting Frequency: Daily (24 hours)
Enable Auto-Generation: Yes

⚠️ Security Note: Since these are live API keys, consider:

Regenerating Facebook tokens if you’re concerned about exposure
Using environment variables or secure storage for production
Monitoring your API usage for any unexpected activity

You’ll need to get your Stability AI y OpenAI API keys separately and add them to complete the setup.

Deploying

At this point Claude had built the zip file for the WordPress Plugin installation. All I had to do was open my WordPress admin page, install the plugin, and add the keys to the settings page.

Development Decisions and Technical Discussion

Architecture Choices

During our conversation, several key architectural decisions emerged:

Local Development Approach: Instead of trying to migrate settings from the remote Python server, we opted for local development with manual configuration transfer.
Complete Plugin Build: Rather than creating placeholder files, we built a fully functional plugin with all necessary components.
WordPress Native Integration: The plugin uses WordPress hooks, AJAX, and admin interfaces to provide a seamless native experience.

Key Features Discussed

Image Generation Process:

Stability AI integration for high-quality car images
Dynamic prompt generation combining car types, colors, and settings
Automatic upload to WordPress media library
Error handling for API failures

Content Creation Workflow:

OpenAI integration for engaging descriptions
Multiple tone options (Professional, Enthusiastic, Technical)
WordPress post creation with featured images
Category assignment and SEO optimization

Social Media Integration:

Facebook Graph API integration
Automatic photo posting with captions
Error handling and retry logic
Connection testing capabilities

Admin Interface Design:

Dashboard with generation controls
Tabbed settings interface
Real-time API status monitoring
Statistics and post tracking
Progress indicators and user feedback

Technical Implementation Notes

Security Considerations:

All API keys stored securely in WordPress options
Nonce verification for AJAX calls
Input sanitization and validation
Capability checks for admin functions

Performance Optimizations:

Asynchronous processing for content generation
Progress bars for user feedback
Efficient database queries
Proper error handling and recovery

WordPress Integration:

Uses WordPress cron for scheduling
Follows WordPress coding standards
Implements proper plugin activation/deactivation
Database table creation for tracking

Configuration Mapping

A key part of our discussion involved mapping the existing Python configuration to WordPress plugin settings:

Python .env files → WordPress plugin settings interface
Automated scheduling → WordPress cron jobs
File handling → WordPress media library integration
API management → Plugin admin interface

Development Workflow

The conversation established a clear development workflow:

Local Development: Build plugin on same server as Python system
Configuration Transfer: Manually map existing API keys and settings
Testing Phase: Verify all API connections and functionality
Packaging: Create zip file for WordPress installation
Deployment: Upload and activate on production WordPress site

Future Considerations

While not explicitly requested, our discussion touched on potential enhancements:

Support for additional content types
Integration with other social platforms
Advanced scheduling options
Performance analytics
A/B testing capabilities

Resumen

This conversation documented the complete process of converting a Python-based AI content automation system into a native WordPress plugin. The discussion covered technical architecture, security considerations, user interface design, and practical deployment strategies.

The resulting plugin provides the same functionality as the original Python system while offering improved user experience through WordPress’s native admin interface, better error handling, and more robust automation capabilities.

The conversation demonstrates how AI automation can be successfully integrated into content management workflows while maintaining security, performance, and usability standards.

Using AI to write a WordPress plugin