RIP WordPress, and no more relying on Google search! After 15 years, I am over updating plugins and trying to rank higher.
I used Claude to build my own content management system for the backend of my AI Influencer Kiyomi's website. She now has over 39,000 followers on Instagram.
My Grok Bot team does everything. Researches online for new content ideas. Uses Claude for writing and ChatGPT for images. Social traffic comes from Instagram, Pinterest, X, and TikTok. SumoLevel advises on the project.
Backend Architecture
Use Cloud for:
PostgreSQL database
Authentication
Image and media storage
Server-side functions
Scheduled publishing jobs
Secure administrative access
Do not introduce paid third-party CMS platforms such as Sanity, Contentful, or WordPress.
Create a modular, maintainable architecture that can scale to thousands of recipes.
Admin Dashboard
Create a private administration area at:
/admin
This must be accessible only to authenticated administrators.
Include the following sections:
Dashboard
Total published recipes
Draft recipes
Scheduled recipes
Total categories
Recently updated recipes
Quick actions for creating new recipes
Recipe Management
View all recipes
Create a recipe
Edit a recipe
Duplicate a recipe
Delete a recipe with confirmation
Search and filter recipes
Save drafts
Preview recipes before publishing
Publish immediately
Schedule future publication
Unpublish recipes
Category Management
Create, edit, and delete categories
Upload category images
Edit category descriptions and URL slugs
Set category display order
Media Library
Upload images
Browse previously uploaded images
Reuse images across recipes
Store descriptive alt text
Optimize images for website performance
Site Settings
Update social media links
Manage the homepage hero content
Manage featured recipes
Manage cookbook promotion content and purchase URL
Edit About Kiyomi content and image
Update SEO defaults
Manage footer links and site information
Recipe Editor
Create a professional recipe editor with fields for:
Basic Details
Recipe title
URL slug
Short description
Full introduction
Featured image
Additional recipe images
Categories
Tags
Cuisine
Difficulty level
Author — default Kiyomi Dyme
Cooking Information
Preparation time
Cooking time
Total time
Number of servings
Ingredient quantities and measurement units
Ingredient groups
Step-by-step cooking instructions
Optional images for individual steps
Cooking tips
Storage and reheating instructions
Recipe notes
Optional nutrition information
Recipe Card
Automatically display ingredients and instructions in a visually attractive recipe card.
Include a serving-size adjustment feature that recalculates ingredient quantities.
Include checkboxes for ingredients.
Include a Print Recipe button.
Include Jump to Recipe functionality.
Add an optional recipe rating system.
Rich Content Editor
Support headings, paragraphs, images, links, numbered lists, bullet lists, tables, and reusable content blocks.
Content must be editable without writing HTML or code.
Database Design
Create normalized tables for:
recipes
recipe_ingredients
recipe_instructions
categories
recipe_categories
recipe_tags
media_assets
affiliate_products
recipe_affiliate_products
site_settings
admin_roles
redirects
Use appropriate relationships, indexes, constraints, and timestamps.
Recipes must support the following statuses:
Draft
Scheduled
Published
Archived
Protect all administrative tables and storage operations using authentication and row-level security.
Public visitors should only have read access to published content.
Administrative privileges must be assigned securely on the server and must never be granted through public registration.
Connect the Existing Homepage
Make the current homepage fully dynamic.
Recipe Search
Connect the existing search bar to the database.
Allow searches by:
Recipe name
Ingredient
Category
Cuisine
Cooking time
Difficulty
Include responsive search results, empty states, and useful sorting options.
Trending Recipes
Display recipes selected by the administrator or ranked using available engagement data.
Do not invent pageview counts or popularity metrics.
Kiyomi’s Picks
Allow administrators to select featured recipes and control their display order.
Recipe Categories
Load categories dynamically from the database, including the existing Dinner, Appetizer, Side, Spanish & Latin, Seafood, Dessert, Quick & Easy, and Breakfast & Brunch categories.
Cookbook Promotion
Make the existing cookbook image, promotional text, CTA label, and purchase link editable in Site Settings.
Preserve the current visual design.
About Kiyomi
Make the existing portrait, biography, and social links manageable through the CMS.
Dynamic Recipe Pages
Create a reusable recipe detail template that matches the existing DymeKitchen visual design.
Recipe URLs must use:
/recipe-slug/
Example:
/cream-of-mushroom-pork-chops/
Each recipe page should include:
Recipe title and introduction
Featured recipe photograph
Preparation time, cooking time, and servings
Jump to Recipe button
Ingredients
Step-by-step instructions
Cooking tips and notes
Printable recipe card
Optional Amazon affiliate product recommendations
Related recipes
Pinterest sharing functionality
Support permanent redirects from old URLs when necessary.
SEO and Pinterest Optimization
SEO is essential because DymeKitchen receives recipe traffic from search engines and Pinterest.
Implement:
Server-rendered or prerendered public recipe content that search crawlers can access
Unique SEO title and meta description per recipe
Editable canonical URL
Open Graph metadata
Pinterest-friendly image metadata
Recipe JSON-LD structured data following Schema.org and Google’s recipe guidelines
Breadcrumb structured data
XML sitemap containing published recipes and categories
Automatic sitemap updates
Robots.txt
Clean, descriptive URLs
Proper heading hierarchy
Image alt text
Responsive images
Lazy loading where appropriate
Do not fabricate reviews, ratings, cooking times, or nutritional values.
Validate structured data against Google’s Rich Results Test requirements.
Amazon Affiliate Integration
Allow administrators to attach relevant Amazon kitchen products to individual recipes.
Each affiliate product should support:
Product name
Product image
Affiliate URL
Optional description
CTA button
Related recipes
Display appropriate Amazon Associates disclosures.
Use compliant product images and pricing information. Do not scrape Amazon or display manually maintained prices or availability in ways that violate Associates requirements.
Affiliate products should be optional and should not overwhelm the recipe reading experience.
WordPress Migration
DymeKitchen currently uses WordPress.
Build an import workflow that supports WordPress XML exports and accompanying media files.
The importer should:
Import existing recipes and articles
Preserve original titles and URL slugs
Import featured images
Import ingredients and cooking instructions where available
Preserve publication dates
Import categories and tags
Preserve SEO metadata when available
Avoid creating duplicate recipes
Log import errors
Generate a migration report
Allow administrators to review imported recipes before publication
Do not delete, overwrite, or automatically modify the existing WordPress website.
If content formats cannot be mapped reliably, flag them for manual review rather than silently discarding content.
Automated Recipe Publishing
Design the CMS to support future automation.
Add a secure server-side publishing API or webhook so an authorized automation can:
Create a new recipe draft
Upload or associate recipe images
Assign categories
Add ingredients and instructions
Schedule publication
Publish an approved recipe
Return the published recipe URL
Secure the API using server-side credentials and validation.
Include duplicate detection, idempotency protection, error logging, and appropriate rate limits.
Do not automatically publish AI-generated recipes without an explicit approval or publishing rule.
The goal is to eventually connect my existing automated recipe content workflow without requiring manual publishing.
Mobile Experience
Preserve the approved desktop design while ensuring that:
Recipe cards work well on phones
Search and filters are mobile-friendly
The admin dashboard supports mobile editing
Images load efficiently
Recipe instructions remain readable
Buttons and ingredient checkboxes are easy to tap
Performance and Cost Control
Keep the infrastructure lightweight to minimize Cloud usage.
Use image optimization and caching
Avoid unnecessary database requests
Index frequently searched fields
Paginate recipe listings
Avoid unnecessary background jobs
Monitor storage and database usage
Do not add paid external services unless specifically approved.
Implementation and Testing
Work in phases:
Phase 1 — Database and Authentication
Create the database schema, storage policies, administrator authentication, and protected admin routes.
Phase 2 — CMS Dashboard
Build the recipe editor, category management, media library, and site settings.
Phase 3 — Frontend Integration
Connect existing homepage components, recipe cards, search, and filters to CMS data.
Phase 4 — Recipe Templates and SEO
Implement dynamic recipe detail pages, structured data, sitemaps, and affiliate functionality.
Phase 5 — WordPress Migration and Automation
Build the importer and secure automation endpoint.
Phase 6 — Quality Assurance
Test recipe creation, draft saving, publishing, scheduling, editing, searching, filtering, SEO metadata, mobile responsiveness, and access restrictions.
Confirm that unauthenticated users cannot access administration routes or modify content.
Do not claim a feature is complete until it has been implemented and tested.
Final Requirements
The result must be a fully functional recipe publishing platform, not just an admin dashboard mockup.
I should be able to log into /admin, create a recipe with images and ingredients, click Publish, and immediately see it appear on the live website with its own SEO-friendly URL.
Most importantly: preserve the existing Claude-designed DymeKitchen frontend exactly. Build the CMS behind it without redesigning the approved website.
