Katipo Project Survival Kit

Backend Database for Content Storage

While Kea has a meta-database to manage all the pages on a site. It doesn't use a database to store the basic HTML and PDF files. This allows Kea to manage the pages effectively, but still publish "regular" HTML pages to the production server.

We think that this has a number of advantages for sites that don't necessarily have homogenous content.

  • You get "real" URLs - ie www.chbdc.govt.nz/council/ rather than www.chbdc.govt.nz/1234hjiiufsd?jeroiufd making them easier to publicise and remember.
  • You don't have to be a programmer to change things - average HTML skills are all that's required to make significant changes to the structure of a site.
  • Your production server can have a very simple set-up, leaving all the "trickery" behind the scenes on the Kea server.
  • Kea is low risk - Because it is non-invasive you are able to easily "retrieve" your site should circumstances change and you wish to move to a new content management system in the future.
  • You can use databases for the things that "need" databases, and not be constrained into developing a "database" site.
  • The load on your production server is lower making pages faster to serve, and quicker for your visitors to download.
  • You still get the advantages of a database driven site - consistent style, able to change templates, dynamic content that changes as soon as new content is added, without the restrictions and cost involved.
    If having your content entirely in a database is a "deal breaker" we could simply expand the Kea database to accommodate this requirement.