Hi, (iPhone)
> On 25.10.2013, at 22:42, "Joe Szurszewski (via Magnolia Forums)" > <[email protected]> wrote: > > If I have pages that are defined in Magnolia, but which are static in the > sense that they will always render exactly the same for all visitors to the > website, my understanding is that Magnolia is still doing the work to render > these pages from the corresponding page and component templates for every > request. > On the author instance this is true. On the author instance everything is rendered fresh, that is necessary when developing or editing content. > Is there a way to tell Magnolia to cache rendered pages, so that it doesn't > have to do all the work of rendering components and pages for every request? > In other words, after a static page is rendered once, it keeps the fully > rendered HTML file stored somewhere so subsequent requests just result in > returning this HTML file? Magnolia has awesome caching - see the docs for the cache module. Content is cached exactly as you describe, and it's very fast... Regards from Vienna, Richard > > -- > Context is everything: > http://forum.magnolia-cms.com/forum/thread.html?threadId=46986f30-55a5-4a64-820c-d1892f19ccf7 > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
