You can choose your landing page to be created as a page with stories from a single collection, or with stories from multiple collections.

1. A Landing Page with all stories from a single collection

Pictorially represented:

2. A Landing Page with all stories from separate collections from bold. Each row of data will take stories from different collections within a single collection.
3. To create a new landing page template:

Step#1:

Step#2:

Post Step#1 and Step#2, you have an option to i. select the landing page from the list of landing pages, or ii. to create a new landing page. In Step#2, you can see that the name of your landing page can be set.

The first time you create a landing page for your website, it defaults as the section page template and is assigned to all landing pages on your website (except for the home page?).

If this is not the first time you are creating a landing page, you have an option to set this created/chosen template to any landing page on your website.

The same template can be assigned to multiple pages. The last assigned template will override all other templates.

4. A Landing Page with all rows as separate collections

Page-Builder Release Note - July 28 2025

Enhancement: Magazine Landing Pages Now Support Vernacular Slugs

Magazine landing pages now fully support vernacular slugs, allowing publishers to create and display magazine content in multiple languages for a more localised experience.

Page-Builder Release Note - 29th June 2023

Loading related stories from the same Magazine issue

Behaviour before the change: Earlier when the user used to open any story linked to the Magazine for infinite scroll related stories used to load from a section or collection as per Page Builder settings(Collection of stories/Collection of collection).

Behaviour after the change: Upon loading the initial story it will call story API with story id and attribute which will throw related stories from the same Magazine issue.

Page-Builder Release Note - 25th Jan 2024

Child sections not picking up while creating Custom Section Landing Page

Prior to the update: When generating a custom section landing page, the Page Builder previously used to pick sections based on their Section slug. This approach led to an issue when there were two sections—a Parent section and a Child section—with the same section slug. Consequently, the Page Builder used to display the same layout for both the parent and child sections.
 
Following the update:  The Page Builder now selects sections for custom section landing pages based on both the section slug and section ID. This approach ensures accuracy, particularly in cases where a Parent and Child section share the same section slug. By considering both the section slug and section ID, the Page Builder ensures that the appropriate layout is rendered for each specific Parent or Child section.

Page-Builder Release Note - 6th June 2023

Configuring Section Page in PB 

Behaviour before the change: After creating the section landing page by default page type selected was the collection of stories and the layout was not effective even after assigning the section to layout. The value of default page type value was not getting passed and resulting fallback value of the default section landing page. Toggling to the collection of collections and reverting it back is used to fix the issue.

Behavior after the change: We have added default values on the landing page and page data type which has fixed the issue. Now immediately landing page values will be passed and changes will reflect without any issue.

Page-Builder Release Note -  July 2nd 2025

Feature: Summary for section pages

This feature lets you add short summaries or introductions to section collection pages, similar to magazine-style introductions. It helps readers quickly understand what the section is about.

To enable:  

Go to Page Builder > Section Page template > Section Page Settings > Layout Settings, enable ‘Section Page Introduction Card’ → then go to the corresponding Collection in Bold, add the summary, and save and publish the changes.

Page-Builder Release Note - September 3, 2025

Session Limiting Feature on Page Builder:

We have introduced a session limiting feature that allows publishers to restrict the maximum number of concurrent logins per user. When the limit is exceeded, users can either terminate previous sessions and continue login or cancel the attempt.

This ensures better security, prevents account sharing, and gives publishers greater control over active sessions across web and mobile apps.

 Page-Builder Release Note - 23rd March 2023

Feature: Option to load Daily Motion / Youtube videos in iframe

Problem Statement/Feature request: 

Currently, Ahead websites utilize lazy loading for all videos and JS embeds to enhance user experience, improve performance, discourage ad-blocker installation, and minimize data consumption on costly or limited networks.

However, this approach requires users to manually click on videos to play them. Autoplay videos generate significantly more revenue than display ads and have been shown to boost engagement, ad clicks, sales, and revenue.

Expected outcome: To address this, Ahead is proposing a toggle option for publishers to choose between lazy loading for a performant website and eager loading for a feature-rich experience. This feature will only be implemented for DailyMotion videos. 

With this change, if the option for “Disable Lazy Load for JS Embed” is checked on PB, the videos from Daily Motion will Autoplay.

To enable autoplay, the following settings need to be configured in Bold and PageBuilder:

In Bold, the client must set a valid player ID by navigating to Settings > Integration > Add Integration > DailyMotion.

For PageBuilder, the client must go to General Settings > Manage > Performance and select the checkbox for “Disable Lazy Load for JS Embed” to activate autoplay.