I'm looking to do an advance level of content control for our editors, but I can't find the right terms to describe the action. If someone could help point me in the right direction I'd be very appreciative. The goal is I want to explicitly control how the data content editors add is displayed, but allow editors to add new data sections as needed, without limit.
My thought is to add adaptive property controls in certain page tabs so the editors won't have to access the Settings section. Such adaptive property controls would then be read to add a new section in the site, and control the display so editors can't break the design.
E.G. A products page editors would select inside the existing "Content" tab a property called, "Add new item" which would then populate the three new property fields: textbox, upload, and richtext editor. So that clicking "Add new item" would create these new property fields each time.
That is the ideal solution, but I'm also interested in other work arounds. This wouldn't actually be for products as that control is managed by adding new document types (like a blog), but for more modular data displays. Think of a content editor deciding, "I'd like to add a call out on this page to advertise downloading our product demo."
Right now what I know how to do is allow the editors to create new Document Types that would append themselves to the page, like a blog posting system, but it's wrong conceptually for the type of data being added.
Thank you for reading, and I hope y'all have a great day
Typically the strategy is to create a new document type to store your "adaptive" content (let's call them callouts for now?) and allow these to be created somewhere outside the root node of your website. Then, you can add a Multi Node Tree Picker to your Product pages to select the callouts to show on the given page. This is nice because it lets them build up a "library" of content and pick/choose which pages to use them on, as well as giving them the ability to add as many as they want (or you can limit them using MNTP).
Hendy has a nice blog post on this, although it's a bit outdated, the general concept is the same. The main difference is that you should use Multi Node Tree Picker instead of the Ultimate Picker.
Alternatively, there's a few datatypes out there that allow you to add "composite" content inline on a content page. So you could define a "widget" as a Textbox, Upload, RTE, and users can add them right inside the content page. These do have a few issues though - they don't support all datatypes (not sure if any support RTE or Upload right now - you could likely use DAMP instead of Upload though), and they don't always "feel" like the Umbraco UI. But if you're interested in checking them out, here's a few links:
Thank you for the speedy reply, I've been working on some of these solutions.
I've hit a curious (and simple) snag with MNTP that I'm hoping someone can help with: I can't find where to see the XML the Multi-Node Tree Picker is outputting. I can kind of guess what the XML tags are going to look like, but it's not the best way to write any xslt for the content I'm bringing it to each page.
Adaptive properties in tabs for editors?
Hi All,
I'm looking to do an advance level of content control for our editors, but I can't find the right terms to describe the action. If someone could help point me in the right direction I'd be very appreciative. The goal is I want to explicitly control how the data content editors add is displayed, but allow editors to add new data sections as needed, without limit.
My thought is to add adaptive property controls in certain page tabs so the editors won't have to access the Settings section. Such adaptive property controls would then be read to add a new section in the site, and control the display so editors can't break the design.
E.G. A products page editors would select inside the existing "Content" tab a property called, "Add new item" which would then populate the three new property fields: textbox, upload, and richtext editor. So that clicking "Add new item" would create these new property fields each time.
That is the ideal solution, but I'm also interested in other work arounds. This wouldn't actually be for products as that control is managed by adding new document types (like a blog), but for more modular data displays. Think of a content editor deciding, "I'd like to add a call out on this page to advertise downloading our product demo."
Right now what I know how to do is allow the editors to create new Document Types that would append themselves to the page, like a blog posting system, but it's wrong conceptually for the type of data being added.
Thank you for reading, and I hope y'all have a great day
Hi Nathan,
Typically the strategy is to create a new document type to store your "adaptive" content (let's call them callouts for now?) and allow these to be created somewhere outside the root node of your website. Then, you can add a Multi Node Tree Picker to your Product pages to select the callouts to show on the given page. This is nice because it lets them build up a "library" of content and pick/choose which pages to use them on, as well as giving them the ability to add as many as they want (or you can limit them using MNTP).
Hendy has a nice blog post on this, although it's a bit outdated, the general concept is the same. The main difference is that you should use Multi Node Tree Picker instead of the Ultimate Picker.
Alternatively, there's a few datatypes out there that allow you to add "composite" content inline on a content page. So you could define a "widget" as a Textbox, Upload, RTE, and users can add them right inside the content page. These do have a few issues though - they don't support all datatypes (not sure if any support RTE or Upload right now - you could likely use DAMP instead of Upload though), and they don't always "feel" like the Umbraco UI. But if you're interested in checking them out, here's a few links:
Tom
Hi Tom,
Thank you for the speedy reply, I've been working on some of these solutions.
I've hit a curious (and simple) snag with MNTP that I'm hoping someone can help with: I can't find where to see the XML the Multi-Node Tree Picker is outputting. I can kind of guess what the XML tags are going to look like, but it's not the best way to write any xslt for the content I'm bringing it to each page.
Again, thank you very much for the help,
Best Regards,
Nathan
Check your /App_Data/umbraco.config - this is where all published data gets stored. You should be able to find it there :)
is working on a reply...