Hi Alla

There are a few ways you can achieve that.
a) You can use the "Data Module". E.g. you can create a nodetype for "footer text" (like copyright, impressum, etc.). In your template paragraphs you can reference that content. So whenever there is a change (e.g. copyright year) you change it in the data module and the other pages get updated accordingly (well, delete the cache...). b) You can also create so called "Microsites". E.g. for the META keywords I create a hierarchy in the microsite. For each keyword create a new page and use the "title" property to store the keyword. Then you create a small paragraph which lists all the keywords and allows the author to select them. If you store the UUID (not the keyword value!), then you can change the keywords anytime in the microsite and your templates will always use the current value.

So there are always two parts: A dialog/paragraph to store the content and another dialog/paragraph to retrieve the content and store a reference (e.g. UUID) of the node/page.

Does that help?
Cheers
Giancarlo


On Feb 6, 2009, at 5:39 PM, <[email protected]> <[email protected]> wrote:

Hello,

Does anyone know if and how I can create a template that would allow an editor to load text from a document stored in the repository?

Here's the scenario - we'd like to re-use content in multiple places on our site. Whatever content we reuse will be stored as documents or pages in the JCR. When creating a new page, we'd like to be able to say "grab content from x document or x page" instead of typing it in. Is this possible in Magnolia?

Thanks!

Alla


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to