On Wed, 2009-07-29 at 09:13 +0200, Olaf iLink wrote: > Hello everybody, > > to bring my original question back to the attention :)
Yeah, it somehow got lost in the follow up discussions, didn't it? :) > I'm still not clear how i can bring the flexibility of a page, where a > user can add different types of paragraphs to the page-content, and > thus creates flexible content, to the data module? Taking if from what you explain below ... there are multiple ways how one can approach this. The most simple is to have one "newsItem" type with controls for all possible content - text, video, audio, images. When creating (or importing) news item, user (importer) fills only the fields for which values exist. In the website then, you create your own paragraph that (same as done for news and events in STK) this paragraph executes search query over Data Module repository and retrieves only the content that contains video or text or images or whatever combination of items you desire and renders it on the page. The more complex approach is to look at the extension to the data module I recently put in the sandbox [1] that allows creation of the multiple data types in same hierarchy and their display alongside in same tree. Then you can have multiple types e.g. videoNews, textNews, etc. still to show the items from the webpages you need to have a paragraph that retrieves the items and displays them. Only this time you will always search in same subpath and limit results by the node type ... there's no much difference here ... actually the former approach would yield better response time (shorter query) in case of big amounts (tens of thousands) of items of each type. The benefit of second approach is that editor can see what is the type of the news entry without having to ever open it, but on the other hand, editor has then choose type of the entry upfront before creating it and can't change it later (e.g. you can't add video to the textNews item, if you defined video content to exist only for videoNews). Of course with the extension to the data module, you can also choose 3rd approach and have generic "news" type and for the entry of this type editor would add sub entry of "textNews" or "videoNews" or whatever. There you gain flexibility and have nice hierarchical structure and make it easy to see what each item contain too, without having to open edit dialog (just need to expand the tree). In my experience, too fine grained approach later leads to very complex hierarchies which are then also cumbersome to work with. You need to find a balance, based on the experience of potential editors, need for searching, expected amount of items and need to extend the types in the future. Still whatever you do in the data module, you need to have something upfront to expose those entries on the website. The simplest is having paragraph that fetches the data from Data Module as I explained above. Other options are writing your own filter or servlet that would do so if you think that would be for some reason more appropriate in your case. Regards, Jan > > Cheers, Olaf > > On Fri, Jun 26, 2009 at 12:04 PM, Olaf iLink <[email protected]> wrote: > Hello Jan, > > f.e. with a news item, i can lots of different types of > paragraphs, > some news items have a video item, some only text, some a > combination > of both etc. > With the data-module this is not something i can do, i define > the > dialogue for a news data-module type, with it's properties, > and this > is what i have to use for that type. > Maybe scanning the PDF makes it a littlebit more clear. > > Basically it's how the STK uses news and events, only the news > and > events items are managed from another tree in the repository, > outside > the website repository, and also have a different > management-menu item > in the authoring environment. > > I guess i can explain it best by saying that is a more generic > version > of news/events in STK, with filtering on terms, and displaying > as a > paragraph type using these terms, and a seperate management > interface > like the data modules in the authoring environment. > > I hope this makes it a littlebit more clear? :) > > Olaf > > > On Fri, Jun 26, 2009 at 10:48 AM, Jan > Haderka<[email protected]> wrote: > > > > On Fri, 2009-06-26 at 10:09 +0200, Olaf iLink wrote: > >> Hello Boris, > >> > >> because the data module has a fixed structure, The power of > the Media > > > > Hi Olaf, > > I don't really understand what you mean when you say "data > module > > structure is fixed". > > - You can have any kind of folder structure there, > > - you can even have multiple different types along in the > same folder > > structure. > > - If you write your own tree configuration you can have even > content to > > be child/parent to another content of the same or even of > different > > type > > > > ... what is it missing that you still see the structure as > "fixed"? > > > > Thanks, > > Jan > > > >> Repository in GX is that it's flexible in it's content, > like Magnolia > >> webpages with their paragraph objects. > >> > >> Olaf > >> > >> On Fri, Jun 26, 2009 at 9:08 AM, Boris > >> Kraft<[email protected]> wrote: > >> > > >> > Why not simply use the data module? Look at the address > book for an example; > >> > or, for a different example, check out the references > section on > >> > magnolia-cms.com, which is completely powered by the data > module. > >> > > >> > - Boris > >> > > >> > > >> > On Jun 24, 2009, at 7:26 PM, Olaf iLink wrote: > >> > > >> >> > >> >> Hello, > >> >> > >> >> in a CMS that some of our customers use (GX Webmanager) > there is > >> >> something called a Media Repository. This is a very > powerfull, elegant > >> >> and flexible way to manage data-objects with > unstructered contents. > >> >> Basically it's a repository that is much alike the > website repository, > >> >> where you can create articles (like webpages), which can > have flexible > >> >> content (like paragraphs added to the pages). You then > can assign > >> >> "terms" to the media repository items. You can then use > a Media > >> >> Repository item (like a specific media repository > viewer/paragraph) in > >> >> your webpages, where you can filter, sort and show > content from the > >> >> Media Repository, mainly filtered on terms. This way you > can f.e. > >> >> create news-items, vacancies, etc. which can have > unstructured > >> >> flexible content, and show these in pages, f.e. the > latest X news > >> >> items etc. > >> >> > >> >> In Magnolia this is a littlebit like how the news-items > in STK are > >> >> done, but more flexible, and especially more easy to use > for a > >> >> end-user, as they have a specific menu-tab out of the > website pages > >> >> tab to manage this kind of content. > >> >> > >> >> What would be the best approach to create something like > this in > >> >> Magnolia? Create a new repository, duplicate the website > management > >> >> admin interface settings to have a specific author menu > button to > >> >> access this new repository, and modify the latest news > STK > >> >> module/dialogue to add terms to look for, ordering, > sorting, > >> >> direction, and make it only look in the new media > repository? > >> >> > >> >> cheers, Olaf > >> >> > >> >> > ---------------------------------------------------------------- > >> >> For list details see > >> >> > http://www.magnolia-cms.com/home/community/mailing-lists.html > >> >> To unsubscribe, E-mail to: > <[email protected]> > >> >> > ---------------------------------------------------------------- > >> > > >> > > >> > > ---------------------------------------------------------------- > >> > For list details see > >> > > http://www.magnolia-cms.com/home/community/mailing-lists.html > >> > To unsubscribe, E-mail to: > <[email protected]> > >> > > ---------------------------------------------------------------- > >> > > >> > > >> > > >> > >> > >> > > -- > > Best regards, > > > > Jan Haderka > > Magnolia International Ltd. > > > > Meet us at the Magnolia Conference > > http:/www.magnolia-cms.com/conference > > > > Magnolia® - Simple Open Source Content Management > > > > > > > ---------------------------------------------------------------- > > For list details see > > > http://www.magnolia-cms.com/home/community/mailing-lists.html > > To unsubscribe, E-mail to: > <[email protected]> > > > ---------------------------------------------------------------- > > > > > > > > > > > > -- > > Met vriendelijke groet / Kind regards, > > Olaf Molenveld > ---------------------------------------------- > Interactive Link > Keizerstraat 31 > 3512 EA Utrecht > T +31 (0)30 634 32 66 > F +31 (0)30 634 32 65 > www.interactivelink.nl > [email protected] > > INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL > PANEL > EN PARODOS DEEL UIT VAN DE HANSNEL GROEP > ---------------------------------------------- > De informatie in dit e-mail bericht is uitsluitend bestemd > voor de > geadresseerde. > Verstrekking aan en gebruik door anderen is niet toegestaan. > Door de elektronische verzending van het bericht kunnen er > geen > rechten worden ontleend aan de informatie. > > > > > -- > > Met vriendelijke groet / Kind regards, > > Olaf Molenveld > ---------------------------------------------- > Interactive Link > Keizerstraat 31 > 3512 EA Utrecht > T +31 (0)30 634 32 66 > F +31 (0)30 634 32 65 > www.interactivelink.nl > [email protected] > > INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL > EN PARODOS DEEL UIT VAN DE HANSNEL GROEP > ---------------------------------------------- > De informatie in dit e-mail bericht is uitsluitend bestemd voor de > geadresseerde. > Verstrekking aan en gebruik door anderen is niet toegestaan. > Door de elektronische verzending van het bericht kunnen er geen > rechten worden ontleend aan de informatie. -- Best regards, Jan Haderka Magnolia International Ltd. Meet us at the Magnolia Conference http:/www.magnolia-cms.com/conference Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
