* create two XHTML documents, e.g. /shared/header, /shared/footer
* set navigation visibility to "false"
* add the include statements to the page template (site:/shared/header)
Thanks Andreas, got your point :-)
Andreas Hartmann wrote:
Anish schrieb:
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'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).
I'm not sure if I understand your question.
ToDo:
* create two XHTML documents, e.g. /shared/header, /shared/footer
* set navigation visibility to "false"
* add the include statements to the page template (site:/shared/header)
Maybe you need to add a particular format for the XHTML resource type
to prepare your header and footer documents for inclusion. You find
more information on this subject on the website.
In the next step you can use meta data to store the reference as
suggested by Thorsten.
HTH,
-- Andreas
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]
