> For the complete documentation index, see [llms.txt](https://docs.chamilo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chamilo.org/administration-guide/admin-guide/platform/pages.md).

# Pages

Pages is Chamilo's built-in, CMS-like tool for the content blocks that make up your portal's public-facing areas — the homepage, footer, navigation menus, and similar placements — without needing to touch a template file.

## Accessing Pages

From the administration panel, click **Platform > Pages**.

## How Pages Work

Each page has:

* **Title** and rich-text **content**
* A **slug**, generated automatically from the title
* **Enabled** — whether the page is currently visible
* **Position** — drag-and-drop ordering within its category
* **Locale** — content is per-language: the same placement can hold one page per language, and the site falls back to the platform's default language if no page exists for a visitor's language
* A **category** — this is what determines *where* the page is rendered (for example `index`, `home`, `footer_public`, or `menu_links`); Chamilo creates the categories it needs automatically

On a multi-URL (multi-portal) install, pages are also scoped per access URL, so each portal manages its own content.

## Where Each Category Appears

The page creation and edition form ends with two diagrams that show where the pages of each category are displayed. Use them to pick the right **Category** before writing the content.

![The page edition form, with the title, friendly URL, enabled, category, language and content fields, followed by two diagrams of the login page and of the interface of signed-in users, whose blue areas are labelled with the page categories index, faq, demo, footer\_public, home, menu\_links and footer\_private](https://1017882194-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi7ZWkudXbaCVfVPkxtuc%2Fuploads%2Fgit-blob-37968af4f4b35729c2566d990eff350ef8b9ee4e%2Fadmin-pages-form.png?alt=media)

* **Login page (visitors who are not signed in)** — the `index` pages fill the main area next to the login form, and the `footer_public` pages are shown in the footer. The `index`, `faq` and `demo` categories also appear as entries in the top bar.
* **Interface of signed-in users** — the `home` pages fill the main area of the home page. The `menu_links` pages are listed in the side menu and the `footer_private` pages are shown in the footer.

The highlighted blue areas are the places a page can take; the grey blocks are Chamilo's own interface, which pages do not replace.

## Menu Link Categories

Two categories turn their enabled pages into a list of links (each link shows the page title and opens the page) instead of rendering their content in place:

* **`menu_links`** — links shown to everyone: under the login form for anonymous visitors, and at the bottom of the left sidebar for logged-in users. Use it for content every user may need, such as legal notices or terms of use.
* **`menu_public_links`** — links shown **only to anonymous visitors**, under the login form on the homepage and on the login page. They disappear once the user logs in. Use it for content aimed at prospective users, such as a presentation of the platform or how to request an account.

When both categories have pages, the `menu_links` links are listed first.

## The Registration Intro Page

**Platform > Setting the registration page** is a shortcut into this same Pages system for one specific placement: the introductory text shown above the public sign-up form. It's restricted to Portal Administrators. Clicking it either:

* Opens the existing intro page for editing, if one already exists for your access URL and language, or
* Creates the placement on the fly and takes you straight to creating its content

Whatever you save here is rendered as an info box directly above the registration form — a natural place for instructions, terms specific to your organization, or context prospective users should read before signing up. Leave it disabled (or never create it) to show the plain registration form with no intro text.

## Publishing a page in all languages

In the page editor's language selector, choose **All languages** when the same page should be visible regardless of the visitor's interface language. Use a specific language for localized content instead. Existing language-specific pages and locale fallback behavior are preserved; this feature does not automatically translate a page.

See [all-languages pages PR #9398](https://github.com/chamilo/chamilo-lms/pull/9398).

## Deleting several pages or related language versions

The Pages list supports selecting multiple entries and choosing **Delete selected pages**. Review the confirmation list carefully before deleting them. When deleting an individual page, Chamilo can also display candidate pages in other languages so you can explicitly select related versions to remove.

Pages in different languages are **not automatically linked**. Do not select a similarly named page unless you have verified it is the correct translation or counterpart. Deletions are destructive, so review the selection and preserve a copy of important CMS content first. See [bulk and multilingual page deletion PR #9331](https://github.com/chamilo/chamilo-lms/pull/9331).
