Fork me on GitHub

Generating Static HTML of Selected Pages, Modules or Blocks?  Bottom

  • A lot of attention has been given to caching to speed up dynamic content and it can make a big difference. But what about going one step further and generating static content on a module by module, block by block and/or page by page basis? That would be very interesting.

    While this might not be viable or desirable for some sites with constantly churning content, it'd be great for others. For example, the content of a site that changes only a few times per week. Ideally you'd have have a panel. like pnMeta, which allows you to set up rules for what will be static and what will be dynamic and when.

    Slugger
  • How would that be an advantage over a good caching system?

    I mean, with caching what we're really talking about is displaying static pages that are updated dynamically according to when content is change in the database or by some other algorithm.

    Am I missing something here? If so, please feel free to whack me with a clue-bat...
  • Slugger,

    When we're talking about a site updated this infrequently this is ideal for Xanthia's full page caching. Design and deploy your site with a Xanthia theme and you can bypass almost all of the module code. We know the result of the page is cached and can serve out the result without asking PN to do so. The only question would be forums and the like but since you say the site is only updated infrequently then we have an ideal solution.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • My fault, I guess I should have stated more clearly. My intent is not to debate the benefits of caching versus static HTML. I'm thinking more about accelerating performance including a better way to mirror websites. Full page caching is nice to have but there's more to it than that.

    Slugger

This list is based on users active over the last 60 minutes.