> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/sites/new-portal/create-site-contents.md).
# Creating Contents for Your Sites
From the Admin Home Page, select Sites toolkit. Under the Web Sites heading, click on the Site counter.
## Creating New Folders and Pages on your Site
From the Admin Home Page, select **Sites** toolkit. Under the **Web Sites** heading, click on the **Site** counter. Select the Webpage or Portal **Title** where you would like to add content.
Use the **Sitemap** panel to navigate to where your content should be nested under by clicking on the titles of the existing content. Use the magnifying glass to select the existing page or folder where you would like nest your new content.
Under the **Page Content > Subpages** panel, click on the **New Page** button.
Under **Page Type** select **Folder** or **Page** Add a **Title** for the **Page Type** you selected
Click **Save** to open the newly created item and begin editing it's contents.
## Changing the Page Setup settings
Under the Page Setup tab, under the Identification heading, click on the Pencil icon :pencil-alt:next to the **Type** field.
Select either **Page** or **Folder** from the dropdown menu.
Click the **Save** button.
**Important Note: Do not select Block from the dropdown menu. You are not able to change a Folder/Page to a Block OR change a Block to a Folder/Page.**
\
## Creating Blocks on a Page
To create a new **Block**, navigate to the **Page Content** panel, select the **Block** tab and then click on the **Edit** button.
Select the Block Type you want to create.
* **Different Block Types:** Headings and Paragraphs, Heading and Paragraphs with Image, Image Gallery, Two Columns, Link to Achievement, Link to Assessment, Link to Course, Link to Survey, Course Summary
Create a **Block Title** and select the **Add** button.
Below the **Block Content** add the block **Heading** and add **Contents**.
Click **Save**
**Important Note: A Block should only be created within a Page. If a Block is created within a Folder it will not display the content.**
\
## Notes on Proper Hierarchy for Sites
A Page can be created within a Folder (**Folder -> Page** :check:) Blocks can be created within a Page (**Page -> Block** :check:) A Page can be created within a Folder and a Block can be created within a Page (**Folder -> Page -> Block** :check:) Folders can be created within a Folder, and contain Pages and Blocks (**Folder -> Folder -> Page -> Blocks** :check:)
Blocks can **not** be created within a Folder (**Folder -> Block** :times:) A Page should **not** be created within another Page (**Page -> Page** :times:), as users will not be able to easily navigate deeply nested site pages.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.shiftiq.com/help/sites/new-portal/create-site-contents.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.