Content Structure Overview: Explanation Plan

Created by Felipe Hermosilla, Modified on Thu, 12 Mar at 2:32 PM by Felipe Hermosilla

The purpose of this plan is to clearly explain how content is structured, organised, and made visible on the platform. Each area plays a specific role within the overall content ecosystem. Understanding how these components connect ensures content is built and published correctly.


1. Module – The Primary Content Container

This is the starting point for building structured content.

  • A module is the main item users see and click on.

  • It acts as the container for all related learning content.

  • It controls key settings such as the title, description, thumbnail image, and publish status.

  • Modules contain units.


2. Unit – The Organisational Layer

Units help break content into manageable and logical segments.

  • A unit sits inside a module.

  • It groups related lessons together into structured sections.

  • Every module must contain at least one unit.


3. Lesson – The Core Content

Lessons are the fundamental building blocks of the learning experience.

  • A lesson contains the content users engage with.

  • It may include video, formatted text, PDFs, assessment questions, or external links.

  • Lessons live inside units.


4. Content Rail – The Display Grouping

Content rails control visibility and organisation on the front end.

  • A content rail is a horizontal collection of modules and content.

  • It determines how modules are grouped and presented to users.

  • If a module is not added to a content rail, users cannot see it.


5. Homepage – The User Access Point

The Homepage as the main page view for users.

  • The homepage displays content rails only.

  • It does not display modules directly.

  • For content to be visible, the content rail must be added to the homepage.

This ensures users can navigate content in a structured and intuitive layout.


6. Page Builder – The Layout Controller

Page Builder is the final step in making content live and accessible.

  • Page Builder determines what appears on the homepage.

  • It is where content rails are added, arranged, and published.

  • It controls the order and presentation of content.

  • If a content rail is not published, it will not be visible.



Summary Flow

To reinforce understanding, conclude with the structural hierarchy:

Lesson → Unit → Module → Content Rail → Homepage (via Page Builder)

This sequence demonstrates how content is built from the smallest component to full user visibility.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article