Learn MemehCMS and ship production public-facing services
Use these docs to operate MemehCMS as a production headless CMS for enterprises, public-sector institutions, public websites, and service portals. Start with the Web Engine deployment package when PHP hosting is required, or publish directly through the APIs.
Pick the path that matches your deployment
If you need a production-capable runtime for PHP hosting, start with the Web Engine. If you already have a frontend team, focus on platform concepts and publish via APIs.
Need help shipping the first rollout?
Start with pricing to choose self-hosted vs managed Memeh Zone. We can support implementation when needed.
What a developer should read first
MemehCMS is headless-first. Developers should understand tenant scope, public modules, ViewModels, service CTAs, and the difference between the internal Developer Pool and public Marketplace before building.
Download the ZIP, run the local PHP server, then review content/site.php, content/services.php, resources/views, and app/ViewModels.
Set MEMEH_API_BASE, MEMEH_TENANT_ID, and menu locations. Keep tenant ID required for public websites.
Do not send raw API payloads into templates. Normalize data first, then render stable keys in HTML.
Test menus, mobile layout, services/products, CTAs, empty alerts, accessibility settings, security headers, and HTTPS before deployment.
Move WordPress content without losing posts or pages
MemehCMS imports the official WordPress XML export file. It brings over blog posts, pages, titles, slugs, publish dates, categories, tags, sanitized body HTML, and media files copied by server-side URL download, a full WordPress uploads ZIP, or split year/month media ZIPs.
In WordPress, open Tools → Export and download the XML export. Choose all content, or export only posts/pages for a smaller migration.
In MemehCMS, open Tools → WordPress Import, upload the XML file, keep XML URL download enabled for public media, or upload a ZIP of wp-content/uploads or a year/month ZIP.
Posts become Articles and pages become Pages. Re-importing updates matching WordPress IDs without deleting existing MemehCMS records.
Keep WordPress online during review, then point the public website or Web Engine package to the MemehCMS APIs when content is approved.