Hi Thorsten

I agree with your thought. It is very common in the websites these days to
have more than one design templates(like different header and footers) for
the sites which are big and want to show page according to the contents.

Having such facility will be beneficial for us.

Regards
Sac

On Fri, Dec 4, 2009 at 2:03 PM, Anish <[email protected]> wrote:

> I'd recommend to use dedicated documents for the shared header and footer
>> information. This is a typical usage scenario. The purpose of meta data is
>> storing information about documents, but since the header and footer are
>> actual content, I wouldn't store them in meta data fields.
>>
>
> Thanks Andreas,
>
> I'm bit confused that how will I achieve editable dedicated documents. I
> want to go with two documents like one for header and one for footer and
> user will be able to edit these dedicated document (even with CMS editors
> like TinyMCE, Firedocs).
>
> Please suggest.
>
>
>
>
>
> Andreas Hartmann wrote:
>
>> Hi Anish,
>>
>> Anish schrieb:
>>
>>> Hi All
>>>
>>> I want to have editable areas in header and footer for the publication.
>>> For that I have considered following points:
>>>
>>>    * There will be editable components (like header background, logo
>>>      image, header text, footer text, links etc) in header and footer.
>>>      These components will be decided at the time of development.
>>>    * User will be able to change the logo, header links, footer, links
>>>      etc. using CMS.
>>>
>>
>>     * I'm considering meta data for storing this header and footer
>>>      information/data, this meta data will be editable by user (using
>>> CMS).
>>>
>>
>> I'd recommend to use dedicated documents for the shared header and footer
>> information. This is a typical usage scenario. The purpose of meta data is
>> storing information about documents, but since the header and footer are
>> actual content, I wouldn't store them in meta data fields.
>>
>> You can just reference the dedicated documents using Cocoon include or
>> XInclude statements, probably with the site: protocol, in the page template.
>> A subsequent include transformation will insert them in the rendered page.
>>
>>     * User will change this header/footer meta data once and new
>>>      header/footer will get reflected for all the pages (even on the
>>>      creation of new XHTML document).
>>>
>>
>> If you use dedicated documents, your users will be able to edit the
>> content of the header and footer using the existing WYSIWYG editors.
>>
>> HTH,
>>
>> -- Andreas
>>
>>
>>
>
> --
> Anish Sneh
> Software Engineer
> Techblue Softwares Pvt. Ltd.
> www.technologyblueprint.co.uk
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Regards
Sachin Sharma

Reply via email to