To recap: Kobot is at The Works Festival working away at the Graphic Designers of Canada tent on a website for Nuit Blanche, the international, all-night contemporary art party that will make its first appearance in Edmonton this September.
As part of the GDC’s outreach through The Works, the tent features designers working in their natural habitat, creating design work and helping to explain the value and necessity of good design. So this blog recounts the steps toward a finished website, and shows the process we go through when we make something.
- Set up the “grid” within the browser. The grid is the organizing principle around which we’ll place objects: a grid-based design makes sure that everything within the design is placed and scaled relative to the other objects. Not only does it help make a balanced and pleasing design, it will come in handy when we start scaling the design for phones and tablets.
- Base colours, base typography are in the code (in the style sheets) ready to go. Style sheets (CSS or cascading style sheets) let us load elements like colours and type once and have them “cascade” through the whole site, instead of having to code them into each page individually.
- Created space on Kobot’s development server so that we can develop the site on the web but in a private spot away from the prying eyes of search engines. We could develop locally, but because both the developer and the designer need to access the site’s database (and it would be much harder to keep two separate databases the same throughout the design process) it makes sense to develop right on the web, where they can share a database.
- Set up a Git Repository that holds bits of code and allows the developer and designer to share them.
- Set up custom post types in the site’s content management system (CMS). Custom post types are places where we put content that need custom parameters that go beyond out-of-the-box post types already present in the CMS we’re using. So if a page’s content needs to be edited in a specific way, we need to build these post types.
- Collected content from the client/input into the back end. We’re in the enviable position of having content ready to go on this build—typically we go through an interview process with clients that lets us create content by getting to know their needs and messaging and voice.
- Established with the client a hierarchy of information.
- Out of that hierarchy, created the content architecture for the site.
And that’s all for day 1. We also met a number of interesting people (as well as some interesting people) down on Churchill Square. If you want to come visit, ask questions, bring Slurpees, please do!