MemehCMS User Manual

MemehCMS is a headless content management platform for institutions, enterprises, public agencies, service providers, and regulated organizations. It separates the admin workspace from public websites so teams can manage content, records, media, services, and governance in one secure place while websites consume published content through APIs or the Web Engine.

Use this manual when you need to understand the daily platform workflow.

Core Ideas

MemehCMS has three operating layers:

1. Platform administration: super admins manage institutions, billing status, contact requests, developer approvals, marketplace moderation, and platform audit logs.
2. Institution workspace: institution admins and editors manage the content, media, records, services, and website configuration for one organization.
3. Public delivery: websites, portals, mobile apps, and the Web Engine consume only published content through tenant-scoped APIs.

Every institution has its own workspace. Content from one institution should not appear inside another institution unless a user has been granted access to both.

Signing In

Open the MemehCMS login page and sign in with your email and password.

For protected admin access, two-factor authentication is required. If your account has not finished two-factor setup, MemehCMS will redirect you to your profile before allowing admin access.

Recommended login practice:

1. Use a strong password.
2. Enable two-factor authentication.
3. Save recovery codes in a secure place.
4. Do not share user accounts between staff members.
5. Ask an admin to invite each person with the correct role.

Choosing An Institution

The top bar shows the current institution and institution ID. Confirm that you are working inside the right institution before publishing content.

If one email manages multiple institutions, the platform can allow that. The important control is the institution membership and role, not only the email address.

Dashboard

The dashboard is the starting point for institution work. Use it to:

1. See article, page, service, records, tender, and alert counts.
2. Open quick actions for common tasks.
3. Review recent content.
4. Copy API endpoints for developers.
5. Confirm that core publishing modules are ready.

If the dashboard looks empty, start by adding media, pages, and at least one public content module such as articles, services, or publications.

Content Navigation

The sidebar is organized like a familiar CMS:

1. Content: posts/news, categories, tags, pages, media, upload media, WordPress migration.
2. Services and Directory: services/products, departments, locations, leadership/organogram.
3. Public Website: website builder, menus, sliders, accessibility.
4. Records and Publishing: publications, records/forms, tenders, notices, events.
5. Requests and Engagement: request cases, emergency alerts, FAQs, jobs.
6. Tools: audit logs.
7. Settings: institution settings, users and roles, profile and API tokens.

When you open a sidebar page, read the description under the page title. It explains what the page is for and what work belongs there.

Posts And News

Use Posts / News for public updates, press releases, speeches, articles, operational updates, and announcements.

Recommended workflow:

1. Click Content > Posts / News.
2. Click Add Article.
3. Enter the title.
4. Add an excerpt for public listing pages.
5. Write or paste the content.
6. Choose a category.
7. Add tags if useful.
8. Choose a featured image from the Media Library.
9. Review the slug and metadata.
10. Save as draft or publish.

Draft posts are private. Published posts are available to public websites through the API.

Categories And Tags

Categories organize articles into public sections such as News, Press Releases, Public Notices, Speeches, or Media Updates.

MemehCMS prefixes category slugs by tenant to avoid conflicts between institutions. For example, two institutions can both use a category called News without blocking each other.

Tags are optional keywords that help internal search and public filtering.

Pages

Use Pages for stable website pages such as About, Contact, Mandate, Leadership, Structure, Service Guide, Privacy Policy, or custom landing pages.

Pages can use the editor and page-builder style sections. Keep each page focused. A page should answer one clear public need.

Media Library

Use the Media Library for reusable images, PDFs, documents, and imported WordPress files.

Good media practice:

1. Upload images through the Media Library or the image picker.
2. Use clear file names before upload when possible.
3. Keep oversized files out of public pages unless necessary.
4. Use PDF uploads for official reports and publications.
5. Avoid pasting raw image URLs when a managed media picker is available.

When choosing a featured image, uploaded images should appear in the picker automatically and can be selected without a second upload step.

WordPress Migration

Use Content > Migrate from WordPress when moving an existing WordPress website to MemehCMS.

From the WordPress side:

1. Log in to WordPress.
2. Open Tools > Export.
3. Choose All content, or choose only Posts and Pages for a smaller migration.
4. Download the XML export file.
5. Keep the old WordPress website online until review is complete if media URLs need to be downloaded.

In MemehCMS:

1. Open Migrate from WordPress.
2. Upload the XML export.
3. Enable media download from public URLs when the old media files are reachable.
4. For private or heavy media, upload a ZIP of wp-content/uploads or split year/month ZIP files.
5. Review imported articles, pages, categories, tags, and media.
6. Fix old formatting before switching the public website.

MemehCMS does not delete WordPress content during import. It imports into the selected institution.

Services And Products

Use Services / Products for public-facing services, paid or unpaid products, permits, applications, support offerings, and institutional service pages.

Each service can include:

1. Service or product name.
2. Description.
3. Fee, if any.
4. About section.
5. Apply, pay, contact, or learn more CTA link.
6. Department ownership.
7. Publication status.

Use a CTA when the public user should do something next, such as Apply, Pay, Book Appointment, Contact Office, or Download Form.

Departments

Use Departments for directorates, units, divisions, commands, teams, or service departments.

Departments help websites create public directories and help staff connect content to the right unit.

Locations

Use Locations for headquarters, branches, offices, stations, regional centers, service points, and desks.

Include contact details, address, opening hours, and map data when available.

Leadership And Organogram

Use Leadership / Organogram for official leadership profiles, positions, biographies, reporting lines, and department placement.

Photos should be selected from the Media Library. Avoid raw photo URLs.

Website Builder

Use Website Builder to prepare a public website package that connects to MemehCMS content and APIs.

Typical workflow:

1. Confirm branding and API configuration.
2. Choose the modules to display.
3. Build menus and footer menus.
4. Add sliders and homepage sections.
5. Export the website files.
6. Deploy the files to hosting.
7. Test public pages on mobile and desktop.

Menus

Use Menus to build website navigation for headers, footers, publications, services, departments, and public information pages.

Start with module presets, then add pages, categories, services, departments, publications, jobs, events, and custom links.

Sliders

Use Sliders for homepage or section hero slides.

Each slider should have:

1. Clear image.
2. Short title.
3. Short description.
4. Optional CTA.
5. Placement and status.

Avoid too many slides. Three to five strong slides are usually better than many weak ones.

Accessibility

Use Accessibility settings for public website controls such as language readiness, accessibility statement URL, skip links, and display behavior.

Public websites should be readable, keyboard-accessible, and mobile-friendly.

Publications

Use Publications for official reports, strategy documents, policy publications, annual reports, budget documents, and formal PDFs.

Attach the PDF through the media picker or upload flow. If upload fails, check the displayed file size limit before trying again.

Records And Forms

Use Records / Forms for laws, policies, manuals, forms, guidelines, circulars, application documents, and public records.

Use clear titles and document types so public websites can group records properly.

Tenders

Use Tenders for procurement notices, bid opportunities, closing dates, tender documents, and procurement updates.

Always confirm closing date and status before publishing.

Public Notices

Use Public Notices for formal announcements that do not belong as normal news articles.

Examples include public warnings, office notices, service disruptions, schedule changes, and notices to applicants.

Events

Use Events for official activities, ceremonies, public meetings, deadlines, workshops, and calendars.

Include date, time, location, and event status.

Request Cases

Use Request Cases to track public enquiries, complaints, FOI requests, implementation help, sales leads, and internal follow-up cases.

This page is for operational work that needs status, priority, assignment, and notes. Do not publish private case details on the public website.

Emergency Alerts

Use Emergency Alerts for public safety advisories, warnings, urgent notices, and time-sensitive public instructions.

Keep alert language direct and action-oriented. Include what happened, who is affected, what to do, and when the alert expires.

Help Centre FAQs

Use FAQs for common public questions and support answers.

Good FAQs reduce repeated emails and phone calls. Keep answers short and update them when policies change.

Jobs And Recruitment

Use Jobs for vacancies, recruitment notices, closing dates, requirements, and apply links.

Confirm the application link before publishing.

Audit Logs

Audit logs show platform activity such as changed records, actors, timestamps, and security-relevant events.

Use audit logs to investigate who changed what and when.

Users And Roles

Use Users and Roles to invite staff and manage workspace access.

Recommended role practice:

1. Give people only the access they need.
2. Remove users who leave the institution.
3. Use named accounts instead of shared accounts.
4. Require two-factor authentication.
5. Review user access regularly.

Trash And Restore

Content modules support trash controls where appropriate.

Trash keeps content out of normal lists and public delivery while preserving the record for possible restore. Use permanent deletion only when retention rules allow it.

Publishing Checklist

Before publishing important content:

1. Confirm you are in the correct institution.
2. Check title, slug, summary, and body.
3. Confirm category and tags.
4. Select media from the Media Library.
5. Check dates, fees, closing dates, and CTA links.
6. Confirm privacy and security sensitivity.
7. Preview through the connected website if available.
8. Publish only when approved.

Getting Help

Use contact or implementation request forms when the institution needs onboarding, migration, website setup, training, or custom support.

Super admins can see those requests inside the platform and action them.