argh! I feel frustrated not being able to explain it good enough .... :) I guess the best explanation is to be found in the media repository PDF manual of GX:
http://www.gxdeveloperweb.com/documentation/GX-WebManager-9.8/Connectivity-Management/GXD0031_en-GX-WebManager-9.8-Media-Repository-20081014.pdf The process works like this: - you switch to the media repository tab, just like the data module tab - there you can create, filter, browse, page through all the items in the repository, this is a flat overview, no nested structures or whatever, just one big list - you create a new media repository item, which basically is the same as a regular GX webpage-type. The powerfull thing of a GX webpage type, just as wih magnolia's templates, that you are not forced into a fixed template of fields, but can add all the types of paragraphs, in the order you like, into the page, ie unstructured or composite content. - you assign some terms/categories to this item and now you can use them through a special component (= magnolia paragraph) where you can filter on terms/categories, order stuff, limit it, etc. (like Plone collections criteria) The powerfull thing here, and some of our customers have really big websites that are filled for 90% with media repository content, is that you don't need to define templates for all the content that is or will be available, it's up to the editors to mix and match the content-items (= paragraphs) in the way they see fit. If you look at it real simple, it's just like another main website tree that is not accessable from a browser, but only from a manager, with a more advanced interface for searching and filtering. The content is only 1 level deep, no structuring there, but the editing and creating of the content is done like a normal webpage, with 1 template type. Olaf On Thu, Jul 30, 2009 at 8:19 AM, Jan Haderka <[email protected]>wrote: > > On Wed, 2009-07-29 at 17:49 +0200, Olaf iLink wrote: > > Hello Jan, > > > > thanks for your thoughts on this! I agree about the added complexity > > of a to granular control. Thats why i love the way it's implemented in > > GX Webmanager so much, basically when you create a new item in the > > mediarepository you create a new webpage, where you can add the > > content-paragraphs and re-order them just like you do with a regular > > webpage, only the pages in the mediarepository aren't displayed in the > > website and have a different management module where you can easily > > filter, browse and page through all the items. > > Is there a way to "frame" the front-end inline editor into the manager > > back-end interface to create new pages? > > Hmm, I probably got your last sentence completely wrong ... do you mean > FCK Editor by "front-end inline editor"? And how would adding ability to > create new page to it solve your problem? > > When I wrote my original answer I assumed (and maybe that was wrong), > that you first create the news items and only then you organize them in > the pages. Or better that there are two different people doing the job. > First job is someone I call web-editor (for the sake of the discussion), > who organizes web content, create news page and defines where and what > kind of the news entries will be displayed on this page. The second > person is a news-editor who will be adding news entries independently of > how/when/if those entries are being displayed on the web or not. The > second person would be most likely (at least partially) replaces by > periodically running ImportHandler fetching the news from other servers > or from agencies providing such info in real news example. > > Anyway, reading what you wrote above, I have the feeling that you work > this the other way around ... you prefer to create a webpage and > paragraphs on this page as a news items, but want those to be stored in > the data module as entries of special type ... is that correct? If so, > this is also possible. all you have to do is write a custom SaveHandler > for the paragraph, that would create new entry of given type in the Data > Module repository and in the paragraph node itself store only location > to the data entry ... honestly though, at this point i have problems to > see any benefits in such an approach, except for ability to browse such > entries later without having to go through the website tree ... maybe > that's all you are after :) > > Cheers, > Jan > > > ---------------------------------------------------------------- > 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. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
