Re: Fluid template in 3.0
My site http://www.thyon.com uses the 960px grids inside articles and you can also look at my client site http://www.willowalks.co.za that uses 1140px, which uses a percentage/px hybrid system. In both cases I don't touch the fe_page template in any way. All the work is done using Articles, ce_wrap, ce_break extensions, which articles are used to create the rows and ce_wrap the column wrappers (if you can't apply the gridxx class directly to the CE.
Re: Fluid template in 3.0
Hi John
Why do you prefer the use of ce_break instead of a CSS code like:
Code:
.xxx:after {
clear: both;
content: " ";
display: block;
height: 0;
visibility: hidden;
}
The ce_wrap responds perfectly to the problem I submit for an article.
Is there a way (without modifying the original template) to use it in the header?
Let imagine that I have 3 blocs, 2 of them will be fixed over the pages (image, menu for example) and the third will be specific part of the selected page.
<?php echo $this->header; ?> will call the different elements. I thought I could create an article with what I need, include it in an insert tag in a module and place the module in the template of the page, but then I need to embed the article of the actual page and I don't really know how to do it.
Is there a solution, or do you have an other idea ?
Thanks
Re: Fluid template in 3.0
ce_break creates a visible item to move and manipulate independently of CSS code. Clients love that, instead of fiddling with CSS code.
For the header, I create a special hidden page called "Site Content" on that I create two articles called "Header Article" and "Footer Article". You then add content to each article.
Then you use my other extension called includes to create a module that includes the article. Then you can use these modules in your layout. Te benefit of this round about way, it to give permission to clients to edit these articles, so they may change header and footer content.
Re: Fluid template in 3.0
You even can unpublish this page with those articles. Only the articles have to be published.
Without an extension you can build modules type html with this code
Code:
{{insert_article::header}}
{{insert_article::footer}}
Re: Fluid template in 3.0
Yeah, but it's nasty to make a module that's HTML and then type this stuff, when you can rather just use my extension and select the article from a list.
And yes, I always have the Site Content page unpublished and un-navigation as well.