Gdes2000 Example Site Maps - Nov, 2010

Site maps are an important stage in the production process when planning a website. When I used to freelance on a regular basis I used them all the time and they not only acted as a visualisation of the potential site [that was clear to both myself and the client] but also like a visual 'contract' in many ways. These don't replace formal contracts obviously but once the site map is signed-off by your client then you have a clear mandate to work to that structure/size/scope of site [I used to put notes on them too from client meets so that I was aware of all of the refs mentioned from early stages of devt]. Below is a couple of examples of site maps and associated devt/construction thoughts.

Andystevo example: [Click to enlarge]

Click to enlarge.

Roz Port - Andy Stevensons group, Thurs evening

1. I used colour to identify the three levels, Homepage, Main Page and Subpage, and then used the brief as a guide for pages on my site map. I added notes about possible issues I should take into account for my future reference and also begun to generate ideas whilst doing this.

2. Although my site map is incredibly useful for my reference with the notes, I am planning on producing a simplified version, showing the pages planned only, which I would present to the client. As Andy pointed out to me, the site map is an incredibly useful record of your agreement with the client, and I think it will be useful to begin working in this way now.

Click to enlarge.

Creative Ben [Andystevo Group - Thu Eve]

1) I tend to try to maintain simplicity when dealing with any piece of planning the client is going to be viewing,  in this case a site map. 

This method makes it easier for the client to add to, change or amend anything we discuss during the client early meetings by drawing and making notes on a printed a draft site map. 

Once this meeting is over I would then draw up a master version of the site map and make sure that all the changes are confirmed and then this is the version that is signed off and kept on record.

2) A useful area that helps bring simplicity forward is the use of colour coding. 

Keeping the colours relevant to the corporate colours of the client is always a nice touch. 

The colours should also demonstrate a clear division between the multimedia elements, external systems and the various levels of internal pages.

Also, avoid long labels for elements. Try to keep the number of words on the page down when it comes to the actual names of pages etc but try not to abbreviate.

This allows you to set out your site map in an eye-friendly way, making use of whitespace to separate different elements, the more clear and easier to understand you can make the site map appear the better.

Click to enlarge.

Feedback on Gdes2000 Briefs Chosen

We're interested in knowing more about your choice of brief.. Now that there's been a visit to the Hurd Library and Jean has met those that are keen to undertake the storytelling brief, please answer the following questions each [as an 'anonymous' comment - click on the pencil icon or 'comments' at the bottom of the post]. This way we start to build-up a slow but sure picture of your individual interests and sensibilities

[Your name] from [either Andy Screen's or Andy Stevo's group - you put here].

A) Which brief did you choose?

B) Give two reasons why you thought this brief the more interesting one. [this could be "I went to the visit" or maybe "I liked it more when Jean explained it" etc].

C) What initial research and examples are you looking at? Give two examples [these could be descriptions of what you've looked at or maybe websites that aren't already given you on the brief].

D) What is your next step?

2010 > 2011 Cohort - Welcome

Hullo to all the new cohort this year who either have myself or Andy Screen as tutor. We'll be using this blog to post images of work ongoing, comment on these and for occasional session-related tasks.

Bockleton Website - Final Prototypes

Tom Willis

Tom Cudworth

David Yanez

Sam Roberts

Nick Lyons

Luke Smith

Leon Li

Amy-Michelle Downey

Adam Hinchcliffe

GDES2000 Storytelling Fest 2010 Shortlist

Timothy Berry

Timothy Berry

Peter Fox

Peter Fox

Paco

Paco

Nicki Hughes

Nicki Hughes

Justin Byrne

Justin Byrne

James Duffield

James Duffield

Jack Ryan-Phillips

Jack Ryan-Phillips

Greg Day

Greg Day

Content Management Systems - Joomla

Web designers today have a multitude of options to create a working website. one of the main benefits of a CMS or Content Management System is that once built - the site can be easily edited by the client [similar to InContext Editing]. This is very common today with web site design but.. designers don't tend to have that much control over site construction via a CMS system.

A CMS is more the domain of coders and developers and uses templates to create pages. To add your own bespoke design [like the sites you've created in Dreamweaver] it gets complicated though - ideally you'll need quite a lot of experience with languages like PHP and databases..

See more details [here] on the Joomla site. There's also videos on Joomla setup and use online via YouTube.

Adobe InContext Editing

As well as the more complicated Content Management Systems [CMS's] for displaying web content like Joomla [see other post] there are other new ways to update static websites. One notable system becoming more and more commonly used is the InContext Editing system.

Adobe uses [and is still evolving] one of these called 'Adobe InContext Editing'. Essentially it's a way of updating a completed website without getting involved with Dreamweaver or code[s] -in fact it's all done in a web browser window and looks no more complicated than creating MS Word docs. It's great for those with clients who want to update their own websites after the designer has created and updated them. Have a look [here] at Adobe's website to find out more and see a demo.