When would I use one over the other? Seems like they do the same thing. Is one deprecated now that components are available?
A component is far more powerful as you can define settings and so make variation to make it reusable in different scenario.
Multi-page section was mainly built to handle navigation in your app. It’s now doable with a component too.
I’m not sure but maybe one remaining advantage for the multi-page section is it will not be rerender when navigating between page if both use the section. I don’t remember if its the case with components. I’m asking the product team to clarify if there is still a point for multi-page section over components, it’s a great question.
Edit : Yes, a multi-page section is still the only way to have part of your UI persisting during navigation (a linked section will not be rerender, and so it will not blink for example)
3 Likes
I had a similar question, and wanted to clarify the difference between a “linked section” (screenshot 1) which shows up when duplicating a page, and a “multi-page section” (screenshot 2) which shows up when “adding” an element/component. I have a feeling they are the same but I wanted to double check.
How about a “multi-page section” with a “component” within it?
Is that not the best of both worlds? I like the idea of the page nav not re-rendering each page change. But perhaps it has to load the component each time anyway?
@archenia_jsanchez They are the same yes!
@what.gift Yes you can use both together for maximal benefit 
1 Like