Page Designer pages in the content library and storefront search
Key Takeaway
Content search and search suggestions each apply a folder filter. To let shoppers find Page Designer pages that aren't in a folder, call setFilteredByFolder(false) on the ContentSearchModel for search results and on the SuggestModel for suggestions.
Page Designer pages and components are saved in the B2C Commerce database as content assets in a content library. They don't behave exactly like ordinary content assets. Content search and search suggestions filter by folder, so a developer must change search code and meta definition files before shoppers can find Page Designer pages and their content.
Pages and components as content assets
Page Designer pages and components are persisted in the B2C Commerce database as content assets and stored in the content library. Processes like replication and indexing generally work the same for them as for other content assets.
Unlike regular content assets, pages and components don't appear in the content asset list in Business Manager. You also can't edit them directly from there. Instead, merchants design, schedule, and publish them in the Page Designer visual editor in Business Manager.
You can't use the OCAPI SHOP and DATA resources to access Page Designer pages and components as content assets.
Pages and components reuse content asset attributes but give them a page-specific meaning. For example:
- Page title becomes the SEO title.
configholds the visibility definition.- Content links hold the components for each region.
The searchable flag and searchwords apply to pages, not components. The searchable flag is site specific. The searchwords attribute is localizable.