# Content page

{% hint style="info" %} <mark style="color:blue;">Path: Homepage > Content page</mark>
{% endhint %}

* [Definition](#id-1.14.x-contentpage-definition)
* [Create a content page](#id-1.14.x-contentpage-createacontentpage)
* [Read the content pages](#id-1.14.x-contentpage-readthecontentpages)
  * [Where can users see the content pages?](#id-1.14.x-contentpage-wherecanusersseethecontentpages)
  * [Content pages](#id-1.14.x-contentpage-contentpages)
  * [Mandatory content pages](#id-1.14.x-contentpage-mandatorycontentpages)
* [Update a content page](#id-1.14.x-contentpage-updateacontentpage)
* [Delete a content page](#id-1.14.x-contentpage-deleteacontentpage)
* [Related resources](#id-1.14.x-contentpage-relatedresources)

## Definition <a href="#id-1.14.x-contentpage-definition" id="id-1.14.x-contentpage-definition"></a>

Content pages are a platform’s internal pages.

These are usually used to share information about a platform (instructions, user guides, FAQs), the company, and the platform’s added value.

It is important to enter relevant information as it will help users find important information quickly.

<mark style="color:red;background-color:yellow;">WHO CAN USE THIS FEATURE?</mark>

All users

## Create a content page <a href="#id-1.14.x-contentpage-createacontentpage" id="id-1.14.x-contentpage-createacontentpage"></a>

Users can not create a content page. Only super-administrators and administrators can create one through the SBO, it is described in the following articles: [Contents](/v2.0/superadmin/contents.md)

## Read the content pages <a href="#id-1.14.x-contentpage-readthecontentpages" id="id-1.14.x-contentpage-readthecontentpages"></a>

### Where can users see the content pages? <a href="#id-1.14.x-contentpage-wherecanusersseethecontentpages" id="id-1.14.x-contentpage-wherecanusersseethecontentpages"></a>

Users can find content pages either in the header banner hamburger menu or in the page footer both available on all interfaces accessible by any platform users (figure 1).

Underlined links indicate content pages.

<figure><img src="/files/tRajGQRE6D6Yl0BEElis" alt=""><figcaption><p>figure 1</p></figcaption></figure>

### Content pages <a href="#id-1.14.x-contentpage-contentpages" id="id-1.14.x-contentpage-contentpages"></a>

Each content page displays:

* The page title (figure 2)

<figure><img src="/files/vMTr82tUsx6hIvlVN2rl" alt=""><figcaption><p>figure 2</p></figcaption></figure>

* The content (figure 3), can be organized in paragraphs with titles.

Users can also see pictures, videos, or links, according to the page’s content.

<figure><img src="/files/7TEz4evYv6YhhKp8cese" alt=""><figcaption><p>figure 3</p></figcaption></figure>

### Mandatory content pages <a href="#id-1.14.x-contentpage-mandatorycontentpages" id="id-1.14.x-contentpage-mandatorycontentpages"></a>

Several content pages are mandatory (figure 4) on each platform:

* Legal notices
* Privacy Policies
* Terms and Conditions
* Cookies management

These pages are related to the platform rights and are usually systematically required.

<figure><img src="/files/AvZm330iRwF2hhdruZq1" alt=""><figcaption><p>figure 4</p></figcaption></figure>

## Update a content page <a href="#id-1.14.x-contentpage-updateacontentpage" id="id-1.14.x-contentpage-updateacontentpage"></a>

Users cannot update content pages.

Super-administrator or an administrator can update the content page in the SBO. The process is described in this article: [Pages](/v2.0/superadmin/contents/pages.md)

## Delete a content page <a href="#id-1.14.x-contentpage-deleteacontentpage" id="id-1.14.x-contentpage-deleteacontentpage"></a>

Users cannot delete content pages.

Super-administrators or administrators can delete the content page in the SBO. The process is described in this article: [Pages](/v2.0/superadmin/contents/pages.md)

## Related resources <a href="#id-1.14.x-contentpage-relatedresources" id="id-1.14.x-contentpage-relatedresources"></a>

**SBO :**

* [Contents](/v2.0/superadmin/contents.md)
* [Pages](/v2.0/superadmin/contents/pages.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://features.scnd.com/v2.0/front-office/content-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
