MemehCMS Product Bible

This product bible defines what MemehCMS is, who it serves, how modules should behave, and how the platform should grow without becoming confusing or fragile.

MemehCMS is an enterprise headless CMS for institutions and large organizations. It can serve government institutions, security-sector agencies, banks, universities, regulators, NGOs, corporate groups, and service organizations that need structured content, governance, public websites, migration, and digital service delivery.

Product Promise

MemehCMS gives serious organizations a structured, secure, and modern alternative to traditional website CMS setups.

The promise:

1. Manage content once.
2. Publish to websites and portals through APIs.
3. Keep institution data separated.
4. Make migration from WordPress realistic.
5. Support services, records, documents, alerts, tenders, jobs, and public engagement.
6. Give developers a clear platform to build on.
7. Keep governance and auditability visible.

Positioning

MemehCMS should not be positioned as a small website builder or experimental MVP.

Recommended positioning:

MemehCMS is an enterprise headless content platform for institutions and regulated organizations.

Supporting message:

It combines content management, public records, service directories, website delivery, WordPress migration, audit logs, media management, and a provider ecosystem in one platform.

Avoid weak positioning:

1. Production SaaS CMS for government institutions.
2. Government Institutions CMS.
3. Simple CMS for websites.
4. Basic admin panel.

Use broader professional language:

1. Enterprise headless content platform.
2. Institutional content and service delivery platform.
3. CMS for regulated organizations.
4. Content operations platform for public websites and service portals.

Primary Audiences

MemehCMS serves several audiences.

Institution administrators:

They manage workspace setup, users, content governance, and publishing readiness.

Content managers:

They create articles, pages, media, services, publications, records, notices, tenders, events, jobs, and alerts.

Developers:

They build websites, portals, Web Engine themes, mobile apps, and integrations from the public APIs.

Super admins:

They manage institutions, billing state, contact requests, developer approvals, marketplace moderation, and audit logs.

Implementation partners:

They help organizations migrate, build public websites, configure service portals, and train teams.

Product Pillars

1. Structured content.
2. Institution isolation.
3. Headless delivery.
4. Governance and auditability.
5. WordPress migration.
6. Website delivery.
7. Public service readiness.
8. Marketplace ecosystem.
9. Security baseline.
10. Professional onboarding.

Every major feature should support one or more of these pillars.

Core Platform Modules

Content:

1. Posts / News.
2. Categories.
3. Tags.
4. Pages.
5. Media Library.
6. Upload Media.
7. Migrate from WordPress.

Services and directory:

1. Services / Products.
2. Departments.
3. Locations.
4. Leadership / Organogram.

Public website:

1. Website Builder.
2. Menus.
3. Sliders.
4. Accessibility settings.

Records and publishing:

1. Publications.
2. Records / Forms.
3. Tenders.
4. Public Notices.
5. Events.

Requests and engagement:

1. Request Cases.
2. Emergency Alerts.
3. Help Centre FAQs.
4. Jobs and Recruitment.

Tools and settings:

1. Audit Logs.
2. Institution Settings.
3. Users and Roles.
4. Profile and API tokens.

Super admin:

1. Platform administration.
2. Sales and contact requests.
3. Developer approvals.
4. Marketplace.
5. Invite institution admins.
6. Platform audit logs.
7. Institution billing.

WordPress Comparison

MemehCMS should feel familiar to people coming from WordPress, but it should not copy WordPress blindly.

What should feel familiar:

1. Sidebar navigation.
2. Posts and pages.
3. Categories and tags.
4. Media library.
5. Menus.
6. Sliders.
7. Trash and restore.
8. User roles.
9. Migration path.

What should be better:

1. Tenant isolation.
2. Structured service and records modules.
3. Public APIs.
4. Security and two-factor expectations.
5. Audit logs.
6. Institution onboarding.
7. Developer marketplace.
8. Dedicated WordPress import with media migration.
9. Web Engine export for simple hosting.

Strapi Comparison

Strapi is flexible for developers. MemehCMS should be more directive for institutions.

MemehCMS should provide ready content modules instead of making every institution design its own content model from zero.

The advantage:

1. Faster onboarding.
2. Fewer modeling mistakes.
3. Better public website templates.
4. More predictable APIs.
5. More useful documentation.
6. More governance for regulated organizations.

WordPress Migration

WordPress migration is a major selling point.

The professional migration flow:

1. User exports WordPress XML.
2. MemehCMS imports posts as Articles.
3. MemehCMS imports pages as Pages.
4. Categories and tags are recreated.
5. Body HTML is sanitized.
6. WordPress IDs are saved to avoid duplicate re-imports.
7. Public media URLs from XML can be downloaded server-side.
8. Private or heavy media libraries can be uploaded as wp-content/uploads ZIP files or year/month ZIP batches.
9. Imported links are rewritten when media is copied.
10. Old URLs are preserved when media cannot be reached.

Do not require raw cPanel, FTP, or shared-hosting credentials as the primary migration approach. That creates credential risk.

Media Migration Philosophy

Media migration must answer the user's real concern: moving content is not useful if images and PDFs are lost.

Supported approaches:

1. Download reachable media from URLs inside the WordPress XML.
2. Upload a ZIP of wp-content/uploads.
3. Upload split year/month ZIPs for heavy libraries.

Best practice:

1. Keep old WordPress site online during XML URL download.
2. Use ZIP import when the old site is blocked, private, slow, or already removed.
3. Migrate media into MemehCMS Media Library, not only by preserving external URLs.
4. Show clear limits when PHP upload size blocks large files.

Public Website Delivery

MemehCMS supports two website delivery models:

1. Developers build custom websites against the API.
2. Users export or use a Web Engine theme/package.

The Web Engine should be:

1. PHP/HTML friendly.
2. Heavily commented.
3. Easy to deploy on shared hosting.
4. Config-driven through API base and tenant ID.
5. Structured around ViewModels or clear data adapters.
6. Ready for menus, services, pages, articles, sliders, records, and footer copyright.

Request Cases

Request Cases are internal operational records for:

1. Public enquiries.
2. Complaints.
3. FOI requests.
4. Implementation help.
5. Sales leads.
6. Support follow-up.
7. Internal case tracking.

This module should not behave like public posts. It stores private work, status, assignment, priority, and notes.

Marketplace And Developer Pool

The ecosystem has two related but different concepts.

Developer Pool:

1. People apply to be recognized providers.
2. Super admin reviews and verifies them.
3. Approval gives confidence and access to the ecosystem.

Marketplace:

1. Approved providers list gigs, services, packages, and solutions.
2. Buyers submit enquiries.
3. Super admins moderate providers, listings, and enquiries.

The marketplace can include:

1. MemehCMS websites.
2. PHP/Web Engine themes.
3. Graphic design.
4. Cybersecurity.
5. DevOps.
6. Mobile apps.
7. Data dashboards.
8. Corporate websites.
9. Training.
10. Migration services.

This expands MemehCMS beyond only a CMS and helps build a service ecosystem.

Security Baseline

MemehCMS must feel trustworthy for regulated organizations.

Baseline expectations:

1. Two-factor authentication for admin access.
2. Strong password controls.
3. CSRF protection for forms.
4. Rate limiting for public forms and APIs.
5. Tenant isolation.
6. Audit logs.
7. Secure file upload validation.
8. Sanitized imported HTML.
9. No raw secrets in public websites.
10. Principle of least privilege.
11. Secure invite flows.
12. Clear file upload limits.

Security language should be plain and practical. Do not make unsupported compliance claims.

Governance Baseline

Governance means people can understand and review how the platform is being used.

Important governance features:

1. Audit logs.
2. Trash and restore.
3. User roles.
4. Institution membership.
5. Publishing states.
6. Onboarding invites.
7. Request tracking.
8. Marketplace moderation.
9. Developer approval workflow.

Sidebar Philosophy

The sidebar should feel familiar to WordPress users, but more organized for institutional work.

Good sidebar rules:

1. Put common content first.
2. Group related modules.
3. Use clear labels.
4. Avoid hiding critical modules.
5. Keep descriptions on every destination page.
6. Make it obvious where to add each type of content.

The page title and description should explain the page without requiring training.

Documentation Philosophy

MemehCMS documentation should be treated as product, not afterthought.

Core documentation sets:

1. User Manual.
2. Content Manager Manual.
3. Developer Documentation.
4. Web Engine Documentation.
5. API Guide.
6. Product Bible.
7. Migration Guide.
8. Implementation Checklist.

Docs should be direct, practical, and role-based.

Pricing And Sales Philosophy

Pricing should be clear enough to qualify customers but flexible enough for institutional deployments.

Suggested pricing language:

1. Managed SaaS for organizations that want MemehCMS hosted and maintained.
2. Self-hosted or private deployment for organizations with internal infrastructure.
3. Migration and implementation packages.
4. Website build packages through approved marketplace providers.
5. Training and support options.

The sales form should feed super-admin requests so leads are not lost.

Implementation Playbook

For a new institution:

1. Create institution workspace.
2. Invite institution admin.
3. Enforce two-factor authentication.
4. Configure institution identity.
5. Import WordPress content if applicable.
6. Upload media or migrate media.
7. Create categories and menus.
8. Add pages, services, departments, leadership, locations, and records.
9. Configure sliders and accessibility settings.
10. Build or export the public website.
11. Test APIs.
12. Train content managers.
13. Review security and audit logs.
14. Launch.
15. Monitor support requests.

Quality Bar

MemehCMS should be judged by the quality bar of a serious SaaS product.

Every feature should answer:

1. Does the user understand what this page is for?
2. Does the workflow avoid unnecessary clicks?
3. Does the UI behave predictably on mobile?
4. Does it preserve tenant isolation?
5. Does it avoid breaking public API contracts?
6. Does it handle empty states?
7. Does it handle upload errors clearly?
8. Does it support auditability?
9. Does it feel professional for institutions and enterprises?

Roadmap Direction

Strong future modules:

1. Approval workflows.
2. Version history.
3. Scheduled publishing calendar.
4. Public API cache controls.
5. Advanced form builder.
6. Data hub from Excel/CSV uploads.
7. Media transformation and thumbnails.
8. More Web Engine themes.
9. Marketplace billing.
10. Theme seller workflow.
11. Multi-language content.
12. Accessibility reporting.
13. SSO for enterprise customers.
14. Backup and export tools.
15. Content quality checks.

Product Decision Rules

When adding features:

1. Preserve current article APIs unless a versioned API is introduced.
2. Prefer structured modules over vague custom blobs.
3. Keep admin pages explanatory.
4. Use Media Library flows instead of raw URLs for images and documents.
5. Keep the sidebar readable.
6. Use clear names for modules.
7. Avoid overloading one feature with too many jobs.
8. Add documentation alongside new workflows.
9. Add tests for critical behavior.
10. Do not ship security-sensitive changes without review.

North Star

MemehCMS should let an institution move from a fragile website setup to a governed content platform that developers, editors, administrators, and leadership can trust.

The platform wins when content teams feel capable, developers have stable APIs, administrators can see governance activity, and public users can find accurate information quickly.