What's inside this article:
- Basic information
- Build a new Landing
- Manage layout blocks
- Manage widgets
- Add a connected Category
- Preview the Landing
- Save and publish
Basic information
This article explains how to build a new Landing from Pangea CMS.
For general information about Landings, including recommendations and best practice, see the alternative article below:
Build a new Landing
To build a new Landing:
- Go to Build > Landings in the primary navigation.
- Select + Add new.
The New Landing dialog opens. Move through the sections below in order:
Layout
Under Layout, select your preferred starting layout.
This determines which empty layout blocks are included by default on the new Landing. The following options are available:
- Blank page: You start with no layout blocks. You can then create a custom layout by adding your chosen layout blocks manually.
- 3 Column Landing: You start with a basic selection of 3-column layout blocks.
After selecting a layout, hit Next.
General settings
Under General settings, provide the following details:
- Title: The title of the Landing in the local language for your site. This title is not displayed on the public site.
- English title: The title of the Landing in English. This title is not displayed on the public site. Using English makes the title understandable for CMS users who do not speak your local language.
After completing the general settings, hit Add.
The new Landing is created in Pangea CMS. However, it is in Draft status and is not accessible on the public site.
Manage layout blocks
Define a custom layout for the Landing using layout blocks. Each block runs horizontally across the page width and includes one or more areas for adding widgets. You can add one widget in each area. For example, the screenshot below shows one block that includes three areas. This block should be used to display three widgets.
To manage layout blocks, select Layout in the left panel.
For detailed information, see the following article:
Manage widgets
Add content to the Landing using widgets. A widget is an interactive block of content that typically showcases one or more content items. Pangea CMS lets you build a wide variety of widget types that serve different purposes. For an overview of the different widget types, see the following article:
To build and edit widgets, select Editor in the left panel.
For detailed information about managing widgets, see the following article:
Add a connected Category
Each published Landing must be connected to one TV or Radio Category. If no Category is selected, it will not be possible to publish the Landing. For detailed information about the purpose of Landings, see the following article:
Via General > Category (Zone), add one connected Category.
The following conditions apply:
- You can only select a TV or Radio Category.
- You cannot select a Category that already has a connected Landing. Each Category can have only one connected Landing.
Preview the Landing
Under Preview in the left panel, you can check how the Landing will look when it is published on the public site. Select Desktop, Tablet, or Mobile to preview the Landing on devices with different screen sizes.
This option is useful to preview unpublished changes while the Landing still has the Draft status.
Save and publish
While the Draft status is selected, hit Save or Save & close to save your changes in Pangea CMS. The Landing is not yet accessible on the public site.
When you are ready, follow the steps below to publish the new Landing:
- Select Published in the top drop-down menu.
- Select Publish or Publish & close.
The Landing is now published. This means it is available via the "Home" tab on pages from the connected Category.
NOTE: You will not be able to publish the Landing if it is not connected to a Category.
The Save / Publish buttons are only active while the Landing includes unsaved changes. If all changes are saved, you see the label Saved / Published and the buttons are inactive.
NOTE: Changes made via the Editor and Layout views are saved / published automatically. It is not necessary to save / publish these changes manually.
