Carefully consider context - there's little point in designing a minimal masterpiece if the site will be content heavy. Design based on real content, not tailored placeholders. These are incorporated into the design - where appropriate - without compromising the IA. This takes into account any brand identity guidelines - including fonts, house styles, assets & elements that may exist, or be created afresh, suitable for the organisation. I purposefully placed this second, though I know it is where a lot of designers start: how it looks.
Navigation labelling based on short, layman terms and verbs, rather than ambitious internal nomenclature.Consider theming and arranging content based on the user (we will get to that) rather than departmental silos. How it works. Look at the current site, the current content. I find the harsh reality is more a chaotic spinning of multiple plates, but I'll try to describe and put something on those plates: We hand these over to a developer to be built We create polished designs and get the client to sign these off We take these wireframes into Photoshop/ Sketch A typical 'design process' often looks like this:
They're likely drawing said picture in an attempt to describe their (or their companies') creative process to a client, or to demonstrate to their peers. If someone shows you a neat conveyor-belt design process diagram when they're describing designing a website, they're lying in order to draw a pretty picture. The process of designing websites at Substrakt, however, is not a neat production-line-style flow diagram it doesn't follow a linear set of steps. Everyone likes diagrams, and everyone likes lists.
0 kommentar(er)
