Personally, I do not think that the layout tool should be in stacks, layouts should be defined in the pagetype 99% of the time, if you want a layout in a stack, then (In my mind) you are doing something wrong.

I would instead suggest creating a new pagetype.

Mnkras, I too have thought this suggestion would be nice. For example, I have a group of 3 blocks side by side in a 3 column layout that I would like to duplicate globally on a page type. But with stacks, I can only "stack" them vertically. Creating a new layout doesn't help because I can't use "add layout" in a page type either. Is there a feature or function that I'm not aware of that would provide this capability? If it is not easy or wise, for some reason, to put "add layout" in stacks, then maybe putting it in page types would be better. Your thoughts?

Respectfully,

Steve

I agree layouts could be convenient. I have been able to do everything necessary with adding CSS to elements in the stack through the "Design" area, however, certainly not everyone can make this work as easily as using a "layout".

It seems silly to me to make a whole new page type, or a single page to make a small change to a stack. For instance, for my "search" page, I do not want a search bar in the header because then it populates my header with search results. I use a header stack to fill my header area with logo, menu and search bar. I remade the entire stack, but had I been able to copy, I could have simply deleted the search element from the duplicate stack.

I could potentially make things easier for myself in the short run by using stylesheets more heavily for the elements in the stacks, but I am trying to make things as editable as possible for the end user.

I'll add my $.02 here.

I would like to see Layouts added to Stacks because some packages require Layouts. For example, I am using the Easy Tabs on a page and I need to deploy those Easy Tabs and their content to several other pages. I'd like to have those tabs in one spot to be able to edit them sitewide without the client having to go to each page to edit them.

You can put magic tabs in a stack.

Here is a work-around that might help:

Example: Let's say you want to have a global area in the Header, with 3 horizontal blocks next to each other. Here's the order you need to do it in.

1. Create individual stacks for each of the 3 blocks that you want horizontally next to each other. This seems redundant, but it will save you time in the long run instead of copying/pasting stacks every time you build a new page, and the MAJOR PLUS that managing the stack will carry the changes across the site.

2. Click the Header area and select "Add layout", choose 3 columns.

3. In each column, select "Add Stack" and choose the stack you built. Do the same thing for the rest of the columns.

Obviously it would be better if you could just create layouts for stacks themselves, but this is the quickest workaround I could think of without using CSS.

Hope that helps somebody! The answers in these forums have saved me many times, so thanks to everyone.

This works fine for small sites or unique pages.

But if you want to use the same structure throughout multiple pages and have it setup such that you can change it in one place, then you either need to be able to add the layout in the stack or in the page type. Neither is available at the moment that I have found.

Yea, that's true. It would be great if Concrete5 (or someone through open source) could build that function.

I would find this feature really handy too.

The style I'm using pulls in a stack for the page header, and I want to add content on the left, on the right and in the middle of this area. I would love to be able to define a 3-column layout for that stack, so I can edit it one place, and have those changes reflected across every page in the site.

I'm not so keen on having to add or edit each page individually to make this work.

Yes, please... it the C5 dev team is seeing this... Layouts in stacks would be great... thank you kindly.

definitely needed.

the most common scenario being you have a global area such as a footer where you want to have let's say 3 columns. you don't want to "hard code" these columns as different areas as they might change, you don't want to put the content in a table with three columns because it's semantically ugly and wrong.

the only workaround right now as i see it is to use the design tool to make them float etc next to each other.

I'd like to see layouts available in stacks.

If you can use them in a page you ought to be able to use them in a stack too. I know it's possible to achieve the same thing with CSS but the same it true if you're in a page, so why make them available at all if they're only going to be a half-way solution?

Good one. But the tricky thing is themes here. A theme can have theme specific layouts too and layouts can have the same handle. So which layout will be used then? This because you can also have different themes per page. I guess code-wise it's also a bit harder. But I can see it may be useful in some situations.