Just shuffled the text a bit to make more sense to the story :) > I think this is a pretty typical situation. It also happens to match my need. > > I have a tree of categorised content, and I'd like one UI for general > administration of this tree, and separately the public instance version.
Yes, I think so too. You'll use the author env. to manage the content tree, and activate the whole thing to the public instance, so your pages can grab the needed content out of it. > What would such a universal placeholder look like? I myself prefer layouts with imports in div's that use dynamic stuff, like menu's and articles. Such a jsp contains no more than a new bar with paragraph names (covered later on), a content iterator with nothing but an edit bar and an includeTemplate in it. This way the jsp knows nothing, except for the paragraphs in my situation. > I think one could say this information about possible paragraphs for a given > position is defined in the .jsp file. Through the use of the cms edit tags. > Are you moving this sort of information into the repository and using that > meta info through your dialog? I only use paragraph names in the newbar, and let magnolia figure out the paragraph that is used on edit. I DO set the contentcollection name in the edit tag, so nested content doesn't get mixed up. I haven't gone that far yet though. I've got no more than 10 paragraph types, so I usually make one editbar with all paragraphs in it. To make this dynamic, I guess it would be relatively easy to fetch all the paragraph nodes from the config tree, and put em in there. > Are you referring here to the dialog you get when editing page or paragraph > properties? Just to be clear: the dialogs are defined in 'dialogs', and the paragraphs are just a 'viewing layer' / 'container' for a dialog. A dialog is a collection of property nodes, a paragraph defines which dialog to use, and optionally, which jsp to use for viewing the dialog type. What I call a custom property is a node with controlltype 'include' which includes a form field rendered in a jsp, created by you. So in this case it would be a jsp with a dropdown of the content sources in your tree, by using the API. When rendering a page on the public site, the content tree path that was subbitted, must be loaded (that's where my brief loadPage tag comes in), and the jsp will do a includeTemplate of the content. You could do the same thing for the view paths you want to use. > Can you provide more details wrt how you are integrating to the existing > dialog principle in order to achieve this? Like described above, dialogs with property nodes that use included controltypes. Stored in '/magnolia/admintemplates/dialogs' if I am not mistaking. > Have you implemented this already? How does the user access the dialog for a > given node? I have implemented some parts of this story, catagorised content and view selection. It would be nice to have a whole content placing mechanism on top of a content tree, but our customers will lose their 'handy' inline edit tool if we do... And we just don't have the time.... BTW: I read a mail a few days ago about reusing content and a claim that it's implemented in 3.x... Maybe you should check it out, before building one yourself. ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
