Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Dave Woestenborghs 3203 posts 10697 karma points MVP 4x admin c-trib
    Nov 02, 2017 @ 08:36
    Dave Woestenborghs
    3

    What is the difference compared to Nested Content

    Hi guys,

    Just curious what the difference is compared to Nested Content except for the UI changes ?

    Dave

  • Michaël Vanbrabandt 849 posts 3292 karma points c-trib
    Nov 02, 2017 @ 08:45
    Michaël Vanbrabandt
    0

    Also curious about this!

    /Michaël

  • Lee Kelleher 3874 posts 14552 karma points MVP 9x admin c-trib
    Nov 02, 2017 @ 09:31
    Lee Kelleher
    3

    In a nutshell, StackedContent differs in that the content is edited in the modal (similar experience to DocTypeGridEditor) and offers a preview feature.

    If you're happy using NestedContent, that's great, carry on with it. We weren't 100% happy with using inline editing for all use-cases, so we've added another option to our toolkits.

    Cheers,
    - Lee

  • Matt Brailsford 2217 posts 10804 karma points MVP 6x c-trib
    Nov 02, 2017 @ 09:56
    Matt Brailsford
    108

    For us NC was just about managing lists of structured data and wasn't really meant for layout (think lists of team members, or company offices rather than full on page layouts).

    SC is designed to be somewhere inbetween the grid and nested content and is geared to fit that gap where users have been using NC for content blocks. Using SC you get block previewing in the back office, and you can have more complex data structures as the modal supports tabs.

    Ultimately you could do the same thing with NC, but SC just gives you more of a visual view of that data,

    For us its NC for lists, SC for simple stacked content blocks, the Grid for full control page layouts.

    Hope that helps.

  • Matt Brailsford 2217 posts 10804 karma points MVP 6x c-trib
    Nov 02, 2017 @ 10:00
    Matt Brailsford
    2

    PS And of course NC plays nicely with SC so for example you could have a "carousel" content block in SC that has a NC "caoursel items" property.

    As Lee has put it before, it's about having a tool set for different purposes, rather than seeing NC as a "one size fits all".

  • martin griffiths 780 posts 1177 karma points
    Nov 02, 2017 @ 14:03
    martin griffiths
    0

    Is there any way SC and NC could be extended to allow for re-usable (pre-populated) property data? A way of picking pre-filled nodes based on the chosen doctype? It's a problem in Umbraco which still has to be solved with a repository in the node tree linked via the MNTP.

  • Craig100 971 posts 2082 karma points c-trib
    Nov 23, 2017 @ 01:20
    Craig100
    0

    @Martin,

    Would the new "Content Templates" functionality in the latest 7.7.6 do that for you?

    Just a thought.

  • martin griffiths 780 posts 1177 karma points
    Jan 25, 2018 @ 15:05
    martin griffiths
    0

    @Craig100 in short no because Content Templates only cover entire page and not a composition upon which you would largely base your NC / SC items. So i'm looking for the ability to have reusable fragments.

Please Sign in or register to post replies

Write your reply to:

Draft