Supressing Global Components?

[zampino]

I've upgraded our Miva to 10.5 and started looking at the new PageBuilder. I'm impressed with the interface, but unable to generate pages because our older design relies heavily on components from the Global Header and Global Footer that lay themselves across the generated pages.

Is there a way to suppress those components in a page built through PageBuilder? I've read through the doc and don't see any switches to do so, and without that I don't see how we could integrate PageBuilder wtihout a full rewrite of our site.

phil

[Brennan]

I would likely need some additional information about this, but if you have stuff in the global header/footer that you don't want on your PageBuilder pages you would need to wrap the code you don't want to display in conditional statements.

You could do somethings like this to hide the global components you don't want:

<mvt:if expr="l.settings:sequence_item:enabled EQ 1">
//hide code you don't want on PageBuilder Pages
</mvt:if>

[lesliekirk]

I've upgraded our Miva to 10.5 and started looking at the new PageBuilder. I'm impressed with the interface, but unable to generate pages because our older design relies heavily on components from the Global Header and Global Footer that lay themselves across the generated pages.

Is there a way to suppress those components in a page built through PageBuilder? I've read through the doc and don't see any switches to do so, and without that I don't see how we could integrate PageBuilder wtihout a full rewrite of our site.

phil

Hey Phil, Your question sort of sounds like mine. I'd like to be able to plug & play the PageBuilder Components onto an existing site. Right now all I'm finding is ways to insert them into a header or footer component. I don't want to have to wipe out the entire existing page layout.

[lesliekirk]

I would likely need some additional information about this, but if you have stuff in the global header/footer that you don't want on your PageBuilder pages you would need to wrap the code you don't want to display in conditional statements.

You could do somethings like this to hide the global components you don't want:

<mvt:if expr="l.settings:sequence_item:enabled EQ 1">
//hide code you don't want on PageBuilder Pages
</mvt:if>

Will there be a way to "plug & play" the Flex Components? It would be fantastic if I could take one of the components and place it exactly where I would like it on an existing page versus just in the current header_sequence and/or footer_sequence.

[Brennan]

lesliekirk what is the use case your trying to solve here with a single component where you don't want the sequence to be controlling the display?

[lesliekirk]

lesliekirk what is the use case your trying to solve here with a single component where you don't want the sequence to be controlling the display?

Working within an existing layout. For example - a SFNT may already have everything the way they want it except for their Hero Carousel. Their Hero Carousel isn't in the "header" location but is sandwiched in between other content. rather than needing to redo the entire SFNT just to have the Hero Carousel why not be able to plug & play it?

Another example - say on the category page - a banner in the page header but other components after the sub-categories?

Something slightly different - back to the SFNT - what about being adding a navigation set within a Component layout? I have a site that has a custom navigation component in a section in the middle of the page? How would that be added in PageBuilder?

[Brennan]

The location of the sequence is entirely up to you. So it does not need to be in the header/footer. We just have the defaults named that way for the pages they are used on.

But you can achieve exactly what you want today. Just place the <mvt:item name="sequence" /> anywhere on the page you want to output your component. Then you can add your hero component or whatever.

The only limitation I can think of is you can't just limit the component to just one. So once the merchant is in PageBuilder they could add additional components above or below your hero component, but that is likely not a bad thing if it help them add a banner or other content to their page.

I think long term you should be thinking in a PageBuilder first methodology where the entire content of the page is controlled by PageBuilder. Its a much better experience for merchants and allows them to self manage their main pages and content.

[lesliekirk]

The location of the sequence is entirely up to you. So it does not need to be in the header/footer. We just have the defaults named that way for the pages they are used on.

But you can achieve exactly what you want today. Just place the <mvt:item name="sequence" /> anywhere on the page you want to output your component. Then you can add your hero component or whatever.

The only limitation I can think of is you can't just limit the component to just one. So once the merchant is in PageBuilder they could add additional components above or below your hero component, but that is likely not a bad thing if it help them add a banner or other content to their page.

I think long term you should be thinking in a PageBuilder first methodology where the entire content of the page is controlled by PageBuilder. Its a much better experience for merchants and allows them to self manage their main pages and content.

Yes, I too am trying to strive for PageBuilder only but right now there are a lot of things that need to be tweaked. Take a look at some my other posts for other items that are needed like being able to control the size of the video box to say half page and then be able to put another component to the left or right of it. Not every site may want to have a full-sized video. I use a website builder theme in WordPress that I explain to the site owner - think in terms of Lego blocks. With Legos you can put the block anywhere you want it and you can also use any size blocks you want. Granted as a kid I also tried to build my walls for strength, but the creative kids would stack all the same size blocks together and do also sorts of stuff (ps...I never hand any of the fancy kits, just a box of Legos). I am truly hoping that this same flexibility is being considered for PageBuilder because that would make the options for a store owner almost limitless. (And notice I have not asked for drop and drag?) I'm also trying to avoid telling store owners that to use the full power of PageBuilder is going to take a rebuild.

So as for placing the <mvt:item name="sequence" /> - am I to understand it can only be put on the page once?

[Brennan]

That flexibility does exist today as the components are intended to be customized. Miva will keep building and adding new components however, we'll never solve every use case for ever customer. That is why we made the components themselves so flexible. Any developer can edit our default components and modify them as needed. If you need a video next to a text box, you can edit our existing components and build your own.

https://docs.miva.com/miva10/referen...flex-component

We have a MivaLearn course on building/customizing components coming out later this month.

The <mvt:item name="sequence" /> should only be used once per page however you can create your own sequence item, by click add item and mapping it to the mv-cmp-sequence module. Then using the code you give it, you can output it like: <mvt:item name="custom_sequence" />

[lesliekirk]

Any developer can edit our default components and modify them as needed. If you need a video next to a text box, you can edit our existing components and build your own.

Sure, but can a store owner?

[Brennan]

These are two different things. A Store Owner will only ever edit the content of a component. We don't want store owners trying to modify the code behind a component. That is intended for Web Developers. The normal path if you need to modify the structure of an existing component would be for the developer to make the necessary changes one time, then hand it over to the Store owner who has the ability to modify the content as needed.