I worked on two new websites/webapplications these past two weeks, where I also helped working on the design.
On mondaymorning (18/03) we sat together to discuss the upcoming projects and create our weekschedule. I would work the next couple of days on the front-end of a company specialized in renovating bathrooms. The website contained only a few pages so I finished this job by the end of the day.
Creem & git
On thursday, Frederik gave me a walkthrough through the Creem CMS system and the code organisation. He also set up access to the private git repository of Creem CMS, for which I needed to generate an SSH key. He helped me to set up my favourite git client: Tower, and he also explained that I should fetch the repo and switch branches by checking-out. I needed to fix a few front-end bugs so I pulled the project, fixed a bug, committed the changes and pushed it back. Since I'm following the Software Engineering and not the Web & Mobile course at school, I studied the slides about git when I came home.
I never worked with private repositories before, but I'll try to use this in my workflow when creating website's on my own. I only used git (in particular github) for large (school)projects and not when I was coding a website for friends&family. By using BitBucket for all of my private repositories, I can use git for every project I'm working on. For my own projects I use shared hosting, so I don't have SSH access. Therefore I experimented with deploying a git repository over ftp by following these instructions. I actually deployed this blog on my ftp host by pushing the git repo :-) !
Creem CMS website
On wednesday a new challenge appeared. Jo asked me if I could make the new Creem website because the old one is outdated. This would mean that I also needed to design it first. We sat together to talk about the content and the layout. It would be a basic one-page website with the essential content and with some frequently asked questions for the customers. Luckely, I'm probably one of the few coders that actually enjoy designing interfaces.
I spent the rest of the day working on the design in Adobe Fireworks. There's an endless battle between Fireworks and Photoshop and there are many advantages to using Fireworks instead of Photoshop as a webdesign tool (unfortunately there are also many disadvantages because Adobe hasn't had major updates for Fireworks in the last three years). I also strongly believe that Sketch will become the webdesign tool of the future. But for now, I still use Fireworks.
The developers (a two man team) of Sketch are machines - since the launch of Sketch, they have achieved more than the whole Adobe Fireworks developer team have ever done. They release an update with tons of bug fixes and new features almost every week. It still doesn’t have such huge capabilities as Fireworks but they are getting closer with each update – I’m pretty sure if they continue working that hard on Sketch, it will become the major UI design application in less than 2 years. – @ivomyntinnen
On thursday I was finishing the Creem CMS website design. I took some screenshots of Creem 3 now that I have access to the repository and local database server. Jo approved the design and I started building the front-end. I used Twitter Bootstrap and I made the whole one-page website responsive. I also used SVG images with retina screens in mind and I used png images as a fallback for older browsers.
On monday 25/03 I finished the Creem CMS website. I used media queries to re-position some elements and make the responsive design look good. I also used a lot of CSS3 for some extra gimmicks.
The result can be seen here on this demo page.
Company visitations webapplication
Thinline is working on a webapplication where people can register when they want to visit the company we're building it for. It's a secure system with different steps according to the type of visitor (schools, dealers, invidivuals, ...). Once they are allowed to register, the person responsible for the group can choose a language for the guided tour and a timeslot. Then he can add every person to the guest list. In the last step he can pay the scheduled visit using Ogone and he gets a confirmation. There's a lot of backend processes to be done, like assigning a guide or merge small groups of people.
On tuesday, we started with an extended meeting to discuss the mockups, the flow and the usability of the webapplication. Jo asked me to help design and code the front-end of this webapplication. I started working on the design and the different steps in the registration process. I asked Jo a lot for his feedback, because everything has to be right as this is an important webapplication that Thinline maybe can re-use for other projects.
I fixed some changes Jo e-mailed me on thursday and I finished the design. I started working on the front-end in the afternoon. I emailed my design and code to Jo because I won't be at the office for a week (Easter holidays).