Content Management System

User Guide

Managing content: signing in, creating and editing articles, organising and translating them, and managing users and permissions.

Screenshots are from a live deployment — your site’s branding, name, and content will differ.

Use ← → arrow keys (or the buttons below) to move through the guide.

Overview

What's inside

This guide is task-oriented — each section is something you want to do, the steps, and the screen you'll see.

Part 1

Getting started

Signing in and finding your way around the dashboard.

Part 2

Working with articles

List, create, edit, delete, translate, publish.

Part 3

Other content

Pages, taxonomy, media, newsletter — same patterns.

Parts 4–5

Users & permissions

For administrators: accounts, roles, and what each person can do.

Part 1 · Getting started

1.1 — Signing in

Reach the CMS at your team's CMS web address (the cms. address for your site). The sign-in screen asks for your email and password, with a language picker in the corner if you prefer another interface language. Enter your credentials and select Login.

New account? An administrator creates it for you (Part 4) and gives you your email and a starting password.

The sign-in screen is a standard email + password form; every screen after sign-in is shown in full in this guide.

Part 1 · Getting started

1.2 — The dashboard

After signing in you land on the dashboard — your operational launchpad. Across the top: the language picker, a light/dark toggle, and your account menu (open it to sign out). Down the left is the navigation rail.

The CMS dashboard with summary row and grouped tiles
The dashboard — summary row (brand, default language, active languages) and the management tiles.

Tiles group everything you manage: Configuration, Access, Content, Taxonomy, Media, and Newsletter — each with a live count.

What you see depends on who you are. This is an administrator's view; a narrower role sees a smaller dashboard (Part 5).
Part 2 · Articles

2.1 — The article list

Select Articles in the navigation rail. From the list you can:

  • Search by title.
  • Filter by category, or narrow to published / featured only.
  • Toggle Published and Editor's choice per row.
  • Edit or delete from each row.
  • Page through results; switch the working language.
  • Start a new article with New Article.
The article list with search, filters, per-row toggles and actions
The article list — search, filters, per-row toggles, pagination.
Part 2 · Articles

2.2 — Creating an article

Blank create-article form with per-language field pairs
The create form — translatable fields appear once per language.

The form is organised around your site's languages. Translatable text fields appear once per active language — an Article Title in English and one in Chinese, each tagged with its language; likewise Subtitle and Description.

As you type the title, the Slug (web-address fragment) is generated automatically — Sample Article Titlesample-article-title. You can adjust it; it must be a valid web-address format.

Select Create Article when done; Reset clears the form.

Create form filled in, showing the slug generated automatically from the title
Filled in — the slug is derived from the title automatically.
You don't have to fill everything at once. A title is enough to create the article — subtitle, description, body, media, and other languages can all come later.
Part 2 · Articles

2.3–2.4 — Editing & deleting

Editing

Open an article's edit action to load it with its current values. Same form as create, pre-filled. Make changes and select Update Article — only what you changed is saved.

Edit form loaded with an existing article's values
The edit form, pre-filled.

Deleting

The delete action shows a confirmation dialog first, telling you whether anything else is linked (e.g. "1 linked record will be affected").

Delete confirmation dialog showing linked-record impact
The delete-impact confirmation.
Deletion is permanent — no trash, no undo. Read the dialog before confirming.
Part 2 · Articles

2.5 — Translating content

Most text can be translated per language, in two places:

  1. In the article form — each translatable field shows once per language, so you write English and Chinese side by side.
  2. From a tag or category chip — each shows a small pencil; select it to translate that item's name across all languages.

In the panel, an administrator sees every active language editable. Edit and Apply; the change saves with the article. Change nothing and the save button stays inactive.

Role-dependent. A language-restricted editor sees the same panel with only their language editable (5.4).
Per-item translation panel with all languages editable
The translation panel — all active languages, administrator view.
Part 2 · Articles

2.6–2.7 — Tags, categories & publishing

Classifying

  • Categories — structured grouping (Region, Technology, Analysis); attach an article to the relevant ones on its form.
  • Tags — free-form labels. Start typing; matching tags appear to pick from. With the right permissions, a Create "…" option adds a new tag on the spot.

Publishing

  • Published — whether it's live to the public. New articles start unpublished, so you can prepare privately.
  • Editor's choice — flags the article as featured.
Both toggles are available in the list and on the form. The language-restricted editor's tag view — where Create "…" is deliberately hidden — is shown in Part 5.
Part 3 · Other content

The same patterns, everywhere

The article patterns carry across the CMS:

  • Pages — standalone pages (e.g. About), managed like articles.
  • Static content — reusable translated snippets used across the site.
  • Categories / Tags — from Taxonomy; same list / create / edit / delete and per-language translation.
  • Media — images and videos.
  • Newsletter — campaigns, subscribers, templates.
Not covered in this edition. The date/time picker, inserting images/video into an article body, and the rich-text body editor weren't captured for this pass and are intentionally left out rather than described from memory — they'll be added in a later revision.
Parts 4–5 · For administrators

Users & permissions

Managing accounts and controlling what each person can do. If your dashboard has no Access area, your role doesn't include this — and Part 5 explains why.

Part 4 · Users

4.1–4.2 — Creating users

The users list showing accounts and their roles
The users list — everyone with a CMS account.
Create-user form with the assigned-roles dropdown open
Creating a user — name, email, password, assigned roles.

From Access → Users, create accounts and open existing ones. A new user gets a full name, email, and password, then one or more roles (with optional direct permissions for finer control). They sign in with the email and password you set.

A user's role determines which parts of the CMS they can see and use — the subject of Part 5.
Part 5 · Roles & permissions

5.1–5.2 — Roles & permissions

Roles (Access → Roles) each carry a short description — from full administrators (who manage everything, including users and permissions) down to editors limited to content, or even content in a specific language.

Permissions are the individual capabilities a role is built from — managing articles, media, users, and so on. A role's permission set is exactly what its users can do, nothing more.

The roles list with descriptions
The roles list.
One role's permission set
A single role's permissions.
The full permissions catalogue grouped by area
The full permissions catalogue.
Part 5 · Worked example

5.3 — A language-restricted editor

The clearest way to understand roles is to follow one: an Editor limited to Chinese content. This single setting reshapes the whole CMS for that person — the interface adapts to match exactly what they're allowed to do.

A smaller dashboard. Compare with the administrator dashboard earlier: the navigation rail shows only Dashboard, Categories, Articles, Tags, Gallery — no Access, Configuration, Pages, or Newsletter. Only the Content and Taxonomy tiles appear.

The language-restricted editor's reduced dashboard
Same CMS, role-shaped — fewer areas, only what they can use.
Part 5 · Worked example

5.3 — What they can & can't do

Article form with non-Chinese language fields greyed out
Locked language fields — only Chinese is editable; other languages are read-only.
Tag field with a populated list but no Create option
No "Create new" tag — existing tags still appear, but creating one (which needs the default language) isn't offered.
Translation panel with only Chinese editable
Translation limited to their language — only Chinese is editable; English, Arabic, Korean, Russian are locked.
Part 5 · The principle

Capability follows the role

A person's role is set once. The CMS then consistently shows them only what they may use, and lets them change only what they're permitted to change — across the dashboard, the forms, and every action.

You manage what someone can do by assigning the right role. The interface follows automatically — there's no separate "hide this button" step to maintain.

Appendix

Quick reference

I want to…Go toThen
Sign inthe CMS web addressemail + password, Login
See all articlesArticlessearch / filter / page
Create an articleArticles → New Articlefill fields, Create Article
Edit an articleArticles → editchange, Update Article
Delete an articleArticles → deleteread impact dialog, confirm
Translate a fieldthe form, or a chip's penciledit per language, Apply
Add a tagthe form's Tags fieldpick existing, or Create "…"
Publishlist or formPublished toggle
Add a userAccess → Usersfill form, assign roles, save
Change what someone can doAccess → Rolesedit the role's permissions
Remember: deletes are permanent; new articles start unpublished; and what you can see and do is governed by your role.
CMS — User Guide
1 / 0