The list of topics or issues to be covered for our individual web site project appears daunting at first glance: maybe even second glance. Today's class is a look at how to wrestle the project to the ground by creating a simple framework to manage all the information requested.
The underlying objective of this project is to see each of you plan a viable web site that will apply the various Internet marketing principles we've discussed over the term. To do that we start by using the most basic planning tool of all: a list.
Let's start with a hypothetical site (in class we used a b2b telecommunications company). We know it has the following sections (each requiring a landing page):
- Home
- Services
- Products
- News
- About Us
- Contact
There we go, six main pages and the beginning of our site framework or architecture. Let's expand the list:
- Home
- Services
- Request a Service Call
- Product Manuals
- GE
- Mitel
- NEC
- Nortel
- Installation
- FAQ
- Products
... and so on
By creating a simple list where we indent sub-pages from their parent page we will eventually build a list of all our pages organized in a way that we can use both as our hierarchial site map and as our site architecture planning document (see attached).
The next step, and the next, is to increment each page's description with additional information as it is prepared or determined. Eventually, we'll have a complete outline of the planned site with key content items, asset requirements and specification for interactive elements—all from the framework of a simple list.
Found this interesting, its community over content. I know we covered this at the start of the semester but since doing my own website and having to go over this information again,figured this article was rather appropriate. http://www.emergencemarketing.com/2008/03/13/community-vs-content-adage-and-the-ipa-get-it-wrong/
A good blog post for those interested in website design. Explains some specific reasons that consumers give-up when trying to buy stuff from a website. My group encountered problems like this when we were working on our good, better, best. Worth reading.
Thanks Charles.
A good read and it's worth tucking away the bookmark for future reference.
D