Portal Page Architecture
Before we get acquainted with Portals' page hierarchy, it's important to understand some key elements that people will encounter in all areas of the Portal site.
Page: Any individual webpage on Portal. If Portal is a book, then this specific area of documentation is a single page in the book.
Cards: Cards act as previews for pages and can be found on almost all areas of Portal. They consist of a Card thumbnail image and Card text, which will help Portal users differentiate between distinct content.
Resources: A series of hyperlinks that will be displayed on the right-hand side of a Portal page.
Sidebar Items: Similar to resources, as sidebar items will display on the right-hand side of a page and act as a hyperlink. Sidebar items differ, however, by providing a field for an image to display in conjunction with the link.
Parent/Child page: All Portal pages are organized within a parent page/child page relationship framework. Each child page is created underneath a parent page and may have child pages of its own.
Home Page: The first page that a user will see when accessing going to https://portal.cca.edu. This is also known as Portal's Dashboard.
Landing Page: All the links in the Portal banner will direct a user to a Landing page. To use the book analogy once more, Landing pages are like the first page in a chapter.
Section Page: Section pages are any of the first pages a user will encounter when clicking on a card in a Landing page. Every stakeholder/content owner/editor/department is represented by a Section page.
Basic Page: Where the bulk of your content will live - your copy, images, documents, embeds, links, everything. Basic pages comprise nearly every page on Portal.
Streamfield Block: A piece of content on a Portal page.
Still a little confused on what all these terms mean? Each element term is hyperlinked to the specific page in our Wagtail documentation that will provide further information on its purposes and capabilities.
Now that we know what all these different terms mean, we can get into how Portal is structured.
So, from the top, most “overarching” level to the bottom, basest level, Portal is made up of:
A home page, which is made up of landing pages, which is made up of section pages, which is made up of basic pages.
This means that if a content editor were to make a child page of the Home page, they could only make a Landing page. They would not be able to create a Section or Basic page, because Section pages are children of Landing pages and Basic pages are children of Section pages.
These relationships are sometimes difficult to understand right off the bat, so please refer to our infographic about Portal page architecture.