Stories are usually used for the front pages and news sections of brochureware type sites as well as longer pieces that don't fit into the blog format on Bryght sites that have blogs.
This work is licensed under a Creative Commons Attribution-Share Alike 2.5 License. This license applies to all text written by Bryght. All others retain full copyright to their text.
Maybe it would be good to hav
Maybe it would be good to have with each part of your web site (each page, or other piece of content) a small explanation, how it is actually made - which modules are used, how they are configured etc. It is much easier for me to see a result and, if I like it, to read how it is done, than to read how something is done, but can't imagine for which purpose to use exactly that approach actually (or, if this is the easiest way to achieve the desired result). The fact is, I am playing a few days with different modules, but somehow have a feeling that a lot of goals can be achieved in more different ways - just don't know which is the best on a long term. Just for few test pages, the "manual approach" would probably be the quickest one, but you usually see a difference when things start to grow... ;-)
It is hard to do as you sug
It is hard to do as you suggest because the purpose of a support site is very different from other types of sites. That is, the purpose of the site drives its design. We are doing "best practices" write ups in our articles section that aim to cover general scenarios and how best to implement them.