The types of sites that drove the evaluation are, ordered by scale:
- personal (personal or family website) -- mostly simple hierarchical structure with 1-2 levels, mix of static and standard dynamic content (e.g. image gallery) + blog; one or two content authors with access to the whole website.
- company (SME company or departmental presentation) -- quite rich hierarchical structure with 2-3 levels, a lot of static contents that needs to be updated at times, but otherwise should not move or change very often, some standard dynamic content (polls, news), plus quite a lot of domain specific dynamically generated + updated contents, may include shop and news as subsites; includes intranet accessible only for a defined set of users, half a dozen of content authors/managers with responsibilities for (mostly disjoint) parts of the website.
- community -- mostly simple hierarchical structure with 1-2 levels, some static content, some blogging, plus standard dynamic content (file uploads/sharing, polls, discussions, galleries); includes intranet accessible only for a defined set of users, one or two editors + a bunch of content authors.
- news (news site, webzine) -- mostly simple hierarchical structure with 1-2 levels, frequently updated content consisting of multiple articles in each node of the hierarchy, article comments and rating, additional standard dynamic content (galleries, polls, forums, ...); one or two editors + a bunch of article authors.
- shop (web shop) -- quite rich hierarchical structure with many levels, a bit of static contents, some standard dynamic content (search, news), plus heavy use of domain specific dynamically generated + updated contents, may include added functionality for registered set of users; requires backend accessible only for a defined set of users, one or two content editors/managers.
For the most desired kinds of websites (personal and company), one needs the following generic structure: tree hierarchical organization, the first level nodes are "sections" of the site, each section has an index page (intro text, configurable contents) plus a set of content pages (static or dynamically generated content) inter-linked via their contents (hypertext, remember that?). The node's index page is static content, not a concat of all section's pages like in a blog. The content pages can have content and structure either static, blog/articles based, or application-specific.