...
Initial Page Generation
Pages should will be generated using when creating a button new member on the manage-showrooms customers page in sitemanager. Once the Plumb Club admin who is setting up the member has added enough details, the pages can be created with the member’s customerID as the groupID, and using stems from the showroomURL field for all 4 pages. showroomURL, showroomURL + ‘-about’, showroomURL + ‘-products’, showroomURL + ‘-media’.
...
Keep headers static among each of the 3 pages within in each template choice
Header will can be a widget in pagebuilder that uses an html file, so that it isn’t editable. Most likely, there will be a global header that exists at the top of all pages.
If we need to tweak a single header, we can save the html to a different file, and then update the pagebuilder data to point to the new file. For member pages, a member-specific static header will be injected using a template file in html/pages/members/templates/memberHeader.html.
...
Initialize each page with the default template for that page upon creating a new member. While editing, inject different data examples into the 3 sections of the body, based on what they choose. They get 3 choices for each section (3 headers, 3 bodies, 3 footers). They will be able to edit these on the page itself using a custom PB2.
...
Members will be able to choose between 3 options of top, middle, and bottom – also known as sections 1, 2, and 3 by making selections in the PB2 sidebar. Dragging and moving sections won’t be permitted in pageBuilder to keep things simple. Control over which pages are editable is explained here: https://punchmark.atlassian.net/wiki/spaces/T/pages/116424705/SiteManager+Access+Control#Limiting-PageBuilder-Access under the “Limiting PageBuilder Access” heading.
Microsite Page URLs
Microsite pages will be shown by their URL in the pages table. The pages, when generated, will all be stems of the showroom URL.
eg. Showroom URL: citizen, About URL: citizen-about, etc…
...