Why?
Abstract
Why to use Blogreen? This document aims to answer to this question as completely as possible, considering various aspect of the strengths of the complete framework.
Today's problems for web integrators
A typical professional website is composed of static pages describing the company and it's buisness, a client area, and administration area and various tools intended to be used by the customers.
A personnal website will commonly be composed of a single tool (such as a weblog) and some static pages.
If we carefully look at those last kind of websites, we can see that the static pages management is generaly done by the dynamic content system itself: most of the webblog systems provide a facility for handling static content such as a page describing the owner of the weblog.
This solves the problem of the integration for websites composed of only one tool and that do not provide various services. But professional websites are commonly far away from being composed of only one weblog system.
An association website will provide for example:
static pages describing the association activities,
a wiki for the members,
mailling lists and a tool to browse the sent mails,
a tool to manage members and subscriptions.
An electronic shop website may rely on another service set:
a few static pages describing the shop,
an dynamic virtual shop system,
a customer area,
a support area to answer customers questions.
Website organization
As shown in the previous examples, a website is composed of different independant areas likend more or less strengthly together.
Why writting recommandations?
Why Blogreen?
Edit
Up