It looks like FW pro can’t nest master pages. Pity. I am right? Can someone confirm me?
The only workaround I found to this is to design separated master page chunks (not inherited from any site page) that I manually copy/paste to the real master pages (inherited by the site pages).
Does this make sense to anyone? Did I miss something?
You can also use the Simple Include Pro action to create include
snippets that can be included back into your site later in the
publishing process (all within Freeway); http://www.freewayactions.com/product.php?id=018
It is a quick and simple method of adding and maintaing common items
(headers, footers, etc) over multiple master pages.
Regards,
Tim.
On 31 Aug 2010, at 00:15, DeltaDave wrote:
You can create the item to be included as a separate FW page and use
the actions to prepare them and include them in other pages.
Now let’s think this in a very specific and consequent way. Assumed that I build my sites in 99% as a boxmodel, we do have often the problem of broken links between master and child pages.
Dan Jasker is building his sites for that reason complete on the master page section. So far so good. The disadvantage of this is: If you have basic changes for example in the css-menu, you have of course to change this manually on every other masters as well (in consequence to update the child-pages).
So the logic wish would be (as here described) to cut your master section into pieces like css-menu, basic boxmodel construction, footer, mybe some other parts like an accordion or whatever. All those are sometimes tricky things to input into a boxmodel (div into div into div …).
To build them each on single master-pages and include them finally into the “use-div” on its final position would be a master piece, isn’t it?
Normally I test by following the instructions pedantic before I post a request or a statement. But with the simple include and create action, it will not be transported for example css-menu-action settings and for each “master-page” it should be created a child page that would prolong my child page section with the simple content.
The basic way and basic thoughts are brilliant, Tim - but in fact - the practice makes me doubt. But I won’t will complaint, it’s maybe just the beginning of a process where I’m personally maybe to shorthanded to understand the complexity of thematic. Maybe there are actions that can do yet, but I feel myself overwhelmed in sorting them out or even understand the proper use of it.
It smells like predistinated to Walter Davis, to hit me into a direction?