so in quebec ui builder is a page builder the thing that it builds our pages and as you saw in the demo pages can be quite complex or they can be quite simple but pages are just a collection of components that are configured and laid out in whatever way you want with whatever components you want the key pieces of pages are that they have a name and then they have a url path and that url path is what you use to go ahead and get to that page so go ahead and go to the next slide please um and a really important concept for quebec and this is a pretty big change from some of the past is that pages are just pages um and so as we talk about the new world of ui builder and ux framework um there is no difference between a workspace page and a portal page they're just pages the only difference between them is how the components are are configured and that's a really important concept to understand as we move into this new future next slide please and similarly the difference between a landing page and a record page is just simply what components are are configured so gone are the days where you can only have one landing page for a workspace you can configure as many pages and variants as you want for that workspace and and kind of uh come up with lots of different interesting ways uh to create experiences for our customer um speaking of pages let's go to the next slide and talk a little bit a little bit about page templates so you can certainly start a new page from blank with nothing on it but in quebec we're also shipping a collection of page templates to users these page templates are largely around the workspace use cases so a customer can start with a page template um like record or landing page or list or several others 404 for example and when they do they actually start with a page that gives them a starting point rather than starting from blank they have two choices when they create a page from a page template they can either reference the original page which is useful and better for upgrading or they can copy the contents of that page template into the new page thereby taking ownership of that page which means that they're responsible for upgrades next slide forrest touched on this a little bit in the demo talked a little bit about page variants but page variants are different you can kind of think of them as sort of like views but they exist at the same url and so here i have a page that has a default variant but it also has a manager variant and maybe you want to put different components or a different layout on the content for different audiences and that would be how you would set that up speaking of audiences there was a question in the chat about this a little bit more and so we're going to go into a little bit more detail here you pair a variant with an audience and an audience uh can be composed of an allow or a deny list that includes roland domain by default and so you could come up with um an audience called managers you know folks who have the role of manager um you could also you know set it up so that it would also be domain specific if you install the ux framework user criteria plug-in audiences get super powers and so you can expand the capabilities of audiences to include role group user company department location and even script and so you could even set up something like uh some user who has the itsm role in the location of europe who is not a manager you can create an audience like that um you can apply multiple audiences to a variant uh and they will be reflected in order and uh that's that's basically how audiences work a very very powerful use case