Video summary

Goodbye WordPress.

Main summary

Key takeaways

Technology

Summary of Technological Concepts, Product Features, and Analysis

Shift away from WordPress + Elementor (workflow change)

  • Previously, Emmanuel mostly built sites using:
    • WordPress as the CMS
    • Elementor for page/theme design
  • Since February of this year, after adopting Claude Code (referred to as “CloudCode” / Claude/CloudCode):
    • He has mostly stopped using WordPress and Elementor
    • WordPress remains in use mainly for legacy customers

Key turning point: “CloudCode/Claude Code” generating a complex site quickly

  • A real estate customer required:
    • A custom post type (real estate listings)
    • Custom loops/templates
    • Map integration
    • Search across custom listings (tools mentioned: JetEngine/JetSearch, Crocoblocks)
    • Additional plugins for advanced features (e.g., map)
  • Expected timeline: months
  • Outcome (from a Claude Code demo):
    • A mostly complete, working website with map + custom features + functional search
    • In approximately ~20 minutes
  • How he describes the system:
    • Generates code from natural-language prompts
    • Doesn’t require deep knowledge of JavaScript/React
    • Produces outputs that can be reviewed and tested

Building custom functionality without buying WordPress plugins

  • He used Claude Code to generate:
    • JSON templates for Elementor
    • Custom plugins, including:
      • A custom search plugin
      • A real estate custom post type plugin
  • Claimed benefit:
    • Generate plugins only with the required features
    • Avoid the “million settings” complexity common in purchased plugins

Rapid iteration examples

  • When listing card images weren’t ready, he prompted Claude Code to add:
    • A plugin setting for a default placeholder image
  • Result:
    • The site improved immediately without waiting for final assets

Replacing “low-stakes” software with custom AI-assisted code

  • He argues AI-assisted development is suitable for many small-business needs, such as:
    • Widgets, calculators
    • Maps
    • Booking flows
  • For high-stakes systems (e.g., payment processors):
    • He recommends relying on APIs like Stripe
    • Rather than building custom payment code via live coding

Automation via an AI-connected plugin to WordPress

  • He built a plugin that creates an API/connection enabling Claude to:
    • Log into WordPress
    • Perform edits across:
      • Elementor pages
      • shop/catalog content
      • settings and other plugins (e.g., Yoast)
  • Example (WooCommerce):
    • Find products with no sales in the last 2 years
    • Produce a confirmation list
    • Apply changes in one click (e.g., move/remove/put into draft)
    • Claimed time savings: “saving hours”

Design workflow: avoiding “AI slop”

  • He does not let AI fully design the website end-to-end.
  • Instead, he:
    • Defines creative direction (layout, colors, buttons)
    • Uses prompts to iteratively refine the result
  • He notes that reaching a good design often takes many prompts (roughly 1–200).
  • He highlights mega menus as a case where custom code feels easier than Elementor/WordPress:
    • Easier to add icons/images/hover effects
    • Faster to test multiple versions

Content and visual generation improvements with AI image/video tools

  • He uses AI tools such as Google AI Studio and Higgs Field to:
    • Generate custom graphics instead of repetitive stock images
  • Example workflow:
    • Use Gemini to clean up a provided photo (improve composition/exposure) while preserving the original image

Contact form reliability via an API-based email service

  • He criticizes typical WordPress contact form behavior, such as:
    • PHP submissions getting sent to spam
    • Delivery failures
    • SMTP plugin setup hassle
  • He promotes Resend:
    • Sends form submissions via API
    • Supports domain verification
    • Uses transactional email setup
    • Claimed benefit: more reliable delivery than PHP-based form handlers

Security argument for custom sites

  • His response to security concerns:
    • Custom sites for small businesses can reduce the attack surface
    • They may not require the same login exposure as WordPress
    • WordPress is widely targeted when vulnerabilities appear
  • His position:
    • For small businesses, security risk is manageable due to reduced surface area
    • For larger/enterprise cases, code review by engineers is still necessary

Product/market conclusion

  • He believes most small businesses didn’t need WordPress because they often:
    • couldn’t figure it out
    • broke the site
    • made it ugly
  • Alternative approach:
    • Offer ongoing site management
    • Or provide a custom editor designed for the client’s skill level (reducing the chance they break things)
  • Where WordPress still fits:
    • If the client explicitly wants it, it’s still valid
  • He questions:
    • Why embed AI inside Elementor/WordPress rather than using AI tools directly for code generation
  • Claim:
    • Performance is better with clean custom code

Main Speakers / Sources

Main speaker

  • Emmanuel — owner/operator of a website design company called “I Create Your Site”

Primary technology mentioned

  • Claude/Claude Code (“CloudCode”)
  • WordPress
  • Elementor
  • ChatGPT
  • Gemini
  • JetEngine / JetSearch
  • Crocoblocks
  • WooCommerce
  • Yoast
  • Resend
  • Stripe
  • Google AI Studio
  • Higgs Field
  • reCAPTCHA

Original video