Visual Page Builder

Webinar Q&A

How long would it take a non-technical content editor to build a page like the one shown in the webinar?

The Visual Page Builder has an intuitive, user-friendly interface with drag-and-drop functionality. Once components have been set up by a developer, a non-technical editor with little to no page building experience would be able to build a custom landing page in under an hour. With content already drafted, this can be done in less than 15 minutes. During our Beta program, Squiz clients, account managers and marketing team (non-technical users) were able to draft and build custom landing pages in under an hour.

What types of pages can content editors build with Visual Page Builder?

Content editors can build any type of page – a homepage, campaign page, landing page, or pages with longer-form content/articles. The page builder can accommodate all these different styles of pages, and the core component library has components that can be used across all of them.

Can we preview how a page would look on different devices and screen sizes?

Yes you can! You can easily adjust the preview width to see what your page would look like across different screen sizes. You can do this by entering a pixel width value, or using the slider to adjust the width.

Upcoming enhancements will allow your organization to create preset screen sizes in a dropdown menu. This will make it easy to quickly preview your page on the specific device types most commonly used by your audience.

Is there any image editing, resizing, or optimization in the platform?

Image resizing is on our roadmap. We're building this functionality directly into the Visual Page Builder's asset browser. This will allow content editors to resize and optimize images without needing to switch to other tools, making their workflow more seamless.

Is there any drag and drop reordering of content blocks?

Using Visual Page Builder, you can easily drag and drop components within the page outline to reorder how components appear on your page.

Is there improved HTML sanitization of pasted content in the text editor?

HTML sanitization is on our roadmap. We've introduced a new formatted text editor with richer formatting controls in our page-building experience, but we're still working on improving HTML sanitization to ensure clean pasting of content.

Can there be health checks on these pages before a content author publishes, such as expected page speed, load speed, or image size?

These pre-publication health checks are on our roadmap, to be introduced to the Visual Page Builder in a future update.

How does the Visual Page Builder and inline editing enable workflow approvers to focus on changes, or compare before/after versions?

Currently, the Visual Page Builder doesn't offer visual comparisons of content changes for workflow approvers. However, we are looking at adding visual comparison functionality in upcoming enhancements. This will likely be developed alongside our planned version history and rollback features mentioned in the roadmap, and the same approach will be applied to enhance content approval workflows.

Can you share more about components? How can I get started with components?

The easiest way to get started is with our DXP core component library, which has 30 pre-built components available for download to your instance. These include banners, pull quotes, image galleries, accordions – covering about 80-85% of what you'd need for a typical web page. You'll just need some front-end developer time to apply your branding and styling. We're also building 13 additional core components that will be available soon.

Alternatively, you can also develop your own components by building them in-house, or by working with our services team or a partner. These would be designed specifically for your organization. You can learn to build components by enrolling for free in our self-paced eLearning Plan: Building and managing components for developers.

No matter which option you choose, your developers have the flexibility to use languages and frameworks of their choice – so you don’t need to have specialized knowledge of Squiz to get started with components.

How easy is it to customize the styles of components to tailor the output to our company's style guide?

This is a simple process with no back-end development required – just some time from a front-end developer to take those components and apply your organization's styles.

Have a look at the documentation here to see how this can be done.

Are the components on Squiz marketplace only compatible with Squiz DXP, or can they also work with Squiz Matrix CMS?

Components on Squiz Marketplace are compatible with both Squiz DXP and Matrix. All of the components that have inline editing features enabled are backward compatible with Squiz Matrix, so they can be used in both Squiz DXP and Matrix.

How does the page builder and new components work alongside existing pages that use Matrix component templates?

The new Visual Page Builder content pages can coexist seamlessly with your existing Matrix standard pages that use Component Content Templates (CCTs). You can maintain a mix of both page types in your instance without compatibility issues.

Additionally, any components designed for the new Visual Page Builder will also work with your standard Matrix pages that use CCTs.

Do I need the Customer Data Platform (CDP) and Optimization in order to use the Visual Page Builder?

No. You’ll still be able to use the Visual Page Builder to launch pages really quickly with components, inline editing, the search-based resource browser, and responsive experience. But without Optimization and the CDP, you won’t be able to apply personalization or A/B testing to your pages.

We do encourage you to consider exploring personalization and A/B testing as a way to make your content more relevant to your audience.

How is A/B content success measured? Is it analytics within Matrix, or do we need to use Google Analytics?

You can view the results and measure success of your A/B tests directly within Squiz DXP. Watch this demo to see the end to end experience.

How is this new iteration different from the previous version of page builder in the DXP?

Based on customer feedback and usage data, we've made several key improvements:

• Inline editing replaces the previous form-based editing approach, allowing content editors to edit directly on the page preview. Form-based editing is still available for those who prefer it.
• Search in the resource browser replaces the navigation-based approach, making it much faster to locate images and assets for your pages.
• Near-instant, background refresh of the content preview eliminates the need to manually save to see changes, creating a smoother editing experience.
• Improved speed and performance with faster load times for preview and editing interfaces.

We have a great video on Youtube that highlights the differences between the legacy and new page builder interface – watch it here.

Why would I choose Squiz's page builder over another competitor or solution?

Squiz DXP’s Visual Page Builder offers:

• A streamlined interface, as opposed to fragmented tools. You can build pages, personalize content, and create A/B tests in a single interface.
• A low- and no-code experience where non-technical teams can work efficiently with everything they need in one place, with less need for developer support.
• True real-time preview, as opposed to back-end/front-end switching. You can edit content directly on the page and see exactly how the page will look for different audience segments. This differs from many competitors that make it painful to switch between edit and preview modes.
• Fast setup and starting time, as opposed to complex implementations. This is enabled by our out-of-the-box core components that can speed up your implementation.