standard page

This is a standard page asset.  It can contain standard elements and bespoke content containers from 5.5 (WYSIWYG  nested assets, code blocks etc), as well as Squiz 6/DXP components which are essentially standarised and supported container templates that come with the system.

Examples of each standard custom component can be seen below. The Squiz Design System project is intended to identify the need for other types of components required by all Parks. These will need to be accessible to WCAG 2.2 / GDS standards.

Also available through the DXP are Content Page assets which can include new personalisation and A/B elements, but not legacy features such as conditional keywords..

The Content Page doesn't yet work on this DEV system and you will get the following error: "This page cannot be edited due to a missing Component Service API identifier on the site asset."

We hope to resolve this following the completion of the migration project but that remains the priority.

Demo accordion component for this

Demo accordion header 1

Demo accordion header 3

Demo accordion header 3

Demo accordion header 4

Demo accordion header 5

Demo call to action hero

Read more

This is a demo hero banner

It can contain HTML as text over a picture

Read more

This is a demo image slider

This is Column 1 of a multi-column content block

This is Column 2 of a multi-column content block

This is Column 3 of a multi-column content block

This is Column 4 of a multi-column content block. 4 is the maximum number of columns available in this demo

This is a demo Tabs block

Here's my first tab

And my second tab

col 1col2col3col4
row 1 Arow 1 Brow 1 Cdemo image 
can this include html?looks like it

Looks like we can include embedded content

Clicking the pen icon in hte component allows us to change the tab headings.

This is a code block

This is a markdown block

Markdown uses characters instead of HTML tags to format text e.g. this bold text uses two stars either side.

This is a WYSIWYG block - below are a nested content block and a snippets block  athough I don't have access to any Squiz snppets so this doesn't show anything

WYSIWYG block for a standard page asset.  

Most legacy pages will just look like this block when the new design is applied.  It's possible we'll add additional blocks above or below to Design customisation (outer walls) or Paint layouts (inner walls and wallpaper) templates  to improve usability and visibilty of less popular content.

Standard page asets can contain multiple standard elements and bespoke content containers from 5.5 (WYSIWYG  nested assets, code blocks etc), as well as Squiz 6/DXP components which are essentially standarised and supported container templates that come with the system.

Examples of each standard custom component can be seen above and below.

The Squiz Design System project is intended to identify the need for other types of components required by all Parks. These will need to be accessible to WCAG 2.2 / GDS standards.

Also available through the DXP are Content Page assets which can include new personalisation and A/B elements, but not legacy content containers.  Unfortuantely Content Pages don't yet work and show the error "This page cannot be edited due to a missing Component Service API identifier on the site asset."