Skip to content
Documentation

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.

Developer handoff

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.

1. Run the starter kit

Download the ZIP, run the local PHP server, then review content/site.php, content/services.php, resources/views, and app/ViewModels.

2. Connect tenant APIs

Set MEMEH_API_BASE, MEMEH_TENANT_ID, and menu locations. Keep tenant ID required for public websites.

3. Map data in ViewModels

Do not send raw API payloads into templates. Normalize data first, then render stable keys in HTML.

4. Ship with a checklist

Test menus, mobile layout, services/products, CTAs, empty alerts, accessibility settings, security headers, and HTTPS before deployment.

Migration

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.

1. Export from WordPress

In WordPress, open Tools → Export and download the XML export. Choose all content, or export only posts/pages for a smaller migration.

2. Import into MemehCMS

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.

3. Review and modernize

Posts become Articles and pages become Pages. Re-importing updates matching WordPress IDs without deleting existing MemehCMS records.

4. Connect the new website

Keep WordPress online during review, then point the public website or Web Engine package to the MemehCMS APIs when content is approved.

WordPress XML stores media references, not the file bytes. The recommended migration is to bring media into the MemehCMS Media Library. For public media, MemehCMS can read the URLs in the XML and download the files server-side. For private or heavy media libraries, upload wp-content/uploads as one ZIP or in repeat-safe year/month batches such as 2025.zip, 2024.zip, or 2025-05.zip. MemehCMS rewrites imported links when a file is copied and preserves the old URL only when a file cannot be reached.