nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Autofill components

Bowker

This may be a "lack of understanding about templates and page layouts" issue, but I'm hoping someone can straighten me out.

I have a page layout that has about 10 areas. Some of those areas will always have the same components (header, footer, nav, social ...) is there a way when I create a new page such that all the components are already filled in?

My confusion comes from I don't understand "how to templates and page layouts play together."

As usual, if the answer is "RTFM" please tell me which manual and where in that manual. Thanks.

Find more posts tagged with

Comments

Adam Stoller

This may be a "lack of understanding about templates and page layouts" issue, but I'm hoping someone can straighten me out.

I have a page layout that has about 10 areas. Some of those areas will always have the same components (header, footer, nav, social ...) is there a way when I create a new page such that all the components are already filled in?

My confusion comes from I don't understand "how to templates and page layouts play together."

As usual, if the answer is "RTFM" please tell me which manual and where in that manual. Thanks.

I'm not 100% sure (since I've done very little [read: practically nothing] with SP/LS - but I believe the granularity is something like this:

One or more pages may be based on a page template; each page template is associated with a page layout; therefore if you define the template so that N-of-10 components are already established, any page using that page template should already have those N components set up in it.

I believe that you have options available to you when setting up the template as to what aspects of the component are user-configurable and what aren't, such that you should be able to pre-set the N components the way you want them.

All of the above is my guess based on what I recall from reading about SP/LS and what I recall seeing in several demos - I'm sure someone else will correct me if I'm wrong in any (or all) respect(s).

nipper

The answer is with templates. A template will be based on a certain page layout. That template will have a set of components which can have preset data, some of which may be user modifiable.

You can get quite fancy with that. In my current gig, we are using LSCS to determine which DCR is used to populate a specific component.

interDev

This may be a "lack of understanding about templates and page layouts" issue, but I'm hoping someone can straighten me out.

I have a page layout that has about 10 areas. Some of those areas will always have the same components (header, footer, nav, social ...) is there a way when I create a new page such that all the components are already filled in?

My confusion comes from I don't understand "how to templates and page layouts play together."

As usual, if the answer is "RTFM" please tell me which manual and where in that manual. Thanks.

Template is your friend. Create a template and drop resuable components (header, footer, nav, social ...) on that template. Template and Layout have many to one mapping. One layout can be used to create multiple templates but same template cannot be associated with multiple layouts. Template are always global i.e. templates are associated with a specific layout across all sites and branches.
HTH