I would store a reference as meta data to the docs. This way you can
have different header and footers on different pages without any pain.
Thanks Thorsten,
The problem I'm facing with this approach is I'm unable to have a
common header and footer as the information will come from individual
meta (page specific meta data)
Thorsten Scherler wrote:
On Fri, 2009-12-04 at 13:37 +0100, 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.
I would store a reference as meta data to the docs. This way you can
have different header and footers on different pages without any pain.
salu2
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
