ContentGroup content type

[KO]

Few times I wished that it would be nice to have contenttype that would not contain actual page content but would open first it's first child page. So something like "section header" but opens it's first child automatically. Or maybe even has selectable child page that it opens. If no childs present it just gives out "No content given".

br, K

[SimonSchaufi]

you can do that with the ContentAliases module

[KO]

ContentAliases is nice and I used it before but I think this is bit different and I'm not sure if Content Aliases can do that. What I mean is something this.

1. Product
    1.1 Product info
    1.2 Product Specs
    1.3 Product accessories

So if you click on 1. Product it becomes as Active Parent and opens 1.1 Product info page which becomes current page.

I believe ContentAlias leaves 1. Product as current page if you link it to 1.1 Product info.

You can do this manually with link. I've seen few other inquiries for something similar than this. Having different content name could also make it possible to create subnavi to some other place in pages and make menu call bring menu items when parent is "ContentGroup" regardless of it's level in menu tree I believe.

[Maticomp]

I would suggest another rendition of ContentGroup content type. That's one of thingies I like about "typolight" cms (which I acctually don't use because of it's crappy template system and not intuitive extensibility). What I mean is that there is a page of "ContentGroup" type (it's displayed as a single menu item, and represented as a single alias - just like a single page), and inside of ContentGroup you may put as many other content elements as you want. For example:

ContentGroup named "Holidays", and there:
-- content type "text" - welcome text about holidays
-- content type "album" - photo gallery shown below
-- content type "feedbackform" - contact form about my holidays

That's what I sometimes miss in cmsmadesimple. Adding photo gallery below certain text content is not that easy as it could be.

[calguy1000]

2.0 will have 'block types' which will be similar..... you'll be able to put content, image, news, type blocks in your template.

[SimonSchaufi]

what is the sense behind this type of content? I dont understand that. could you explain it briefly?

[Maticomp]

I think I already did? As for now it's impossible or at least inconvinient to easily put on the one single page (visible as a single page in the menu structure) some text content (edited with TinyMCE) mixed with news, photo gallery and other stuff. I personally find much more logical to put image block below content block, instead of putting images _into_ the content. For example because it's often logical to use markdown or textile to edit content in which putting images is hell of a problem for typical end-user.

[KO]

So template for content? What {content} gives out in page template. I see this also nice feature as some "editors" see this current "freedom" bit too much and they also make mistakes by putting image bit too large or something which cannot be controlled by system now. As well as those thing you mentioned. Maybe that's those "blocks" in 2.0.

Originally I had an idea of content type that would behave as section header but when you click it, it would redirect to first child page automatically. Or maybe even selected child in that "contentGroup" or "contentParent". So it's more navigation thingy.  I've seen few questions in this forum that how to open child page automatically with clicking top menu item, but only way I see is to manually link them. ContenAlias reads content which is a bit different but nice anyways.

[Maticomp]

Yup, I'm exactly speaking about editor's freedom. WYSIWYGs are nice, but give no control over produced code. I would much more appreciate blocks stacked one below other, such us "plain text" (edited with some kind of textile markup, *for bolds* and so on), "image" giving the ability to insert a image/set of images directly with CMS MS (giving the CMS control over image size and behaviour), and else.

I'm looking from the point of view of end-user such as a secretary in small business company. For me it's no problem to edit directly in HTML, but she can only manage TinyMCE. And TinyMCE, when abused, gives code almost as crappy as FrontPage, therefore I can't guarantee validation and layout.

[KO]

Here is actually one post that just came.

http://forum.cmsmadesimple.org/index.ph ... cseen.html

So in a way like CMS-link feature.

Br, K

[Ned Nowotny]

For something that automatically navigates to a particular child page, see the following reply and it's reference to my original post:

    Re: Moving pages out from under parents

The rest of the discussion suggests another idea.  Today, a page can have multiple content blocks (these are text blocks though they could be nothing more than an HTML or CMSMS link) per page, but every content block in CMSMS belongs to a particular page.  For more flexibility (and potential complexity for many users), it would be useful to be able to access content from multiple pages and broaden content to include images, links, "code" (i.e. straight PHP), etc.  In fact, CMS has that now, but does not have a way to compose a page from other "pages" because of the tight coupling between the concepts of "page" and "content".  Of course, caching or a mechanism along the line of what I talk about in the following is critically necessary as you go to a system that can compose pages containing one or more content items that can themselves be generated from "templates" or straight code:

    Using Content Management to Assemble Static Content as well as Dynamic Content