17. January 2013 21:54
by Troy
0 Comments

Website (Re)Design - What is Important Today?

17. January 2013 21:54 by Troy | 0 Comments

Mobile devices.  More on that later.

I decided that it was time to update my website with a new design.  The previous one had been around since 2002.  Since then, the site had seen some content updates and a few technology updates, but nothing major.  Nothing architectural.  Nothing visual.

I began the process of redesign by doing some research and identifying some requirements.  I also identified some specific technologies that I wanted to use, mostly out of interest, since this simple site could be completed successfully in many ways.

The requirements:

  • Mobile device compatible
  • Responsive UI design (related to mobile device compatibility)
  • new look and feel - new design, something different
  • adopt HTML5 and CSS3
  • adopt MVC (Model-View-Controller) with extension-less URLs (like /Resume instead of /Resume.aspx)
  • support proper redirection of URLs that changed because of above, so that old links to my site would not return a 404 Not Found
  • support for canonical URLs
  • custom 404 Not Found page
  • update blog to use latest version of BlogEngine.NET
  • provide a printer friendly version of my online resume

If you are redesigning an existing site or application, the size and scope of the work has to be analyzed to determine the best implementation strategy.  In my case, the site was small enough and simple enough that a complete re-write was the logical choice.  For larger projects, a phased approach might make more sense and would probably deliver business value sooner than attempting a complete re-write from scratch.

I started with site architecture research.  I wanted an HTML5 site that used CSS3 and supported mobile devices.  Mobile device support is important.  It is no secret that mobile device adoption is soaring.  The typical options for mobile support currently include building:

  • a native application (an application designed specifically for each device type such as iPhone, android, BlackBerry, Windows Phone, etc.)
  • a website with a Responsive UI design that works well with mobile devices or a site designed specifically for mobile
  • a hybrid - a site built mostly with HTML5 and javascript that is then wrapped inside a native application using a tool like PhoneGap to create the wrapper

My simple site did not warrant a native application, nor a hybrid solution.  I did not want to create a separate site or design to support mobile devices, so I opted for a Responsive UI design that "adjusts" itself as the screen size changes, to provide an optimized view of the site content at different resolutions.  To implement this, I reviewed HTML5Boilerplate and Twitter Bootstrap, eventually choosing the latter.  Both are very good based on my testing so far and are an excellent way to get started with a responsive layout using HTML5 and CSS3.  Bootstrap includes Glyphicons which are cool, but I switched to FontAwesome, which uses a custom font instead of images.  Using a font is cool because changing the icon size and color is as simple as changing font size and color using standard CSS.  No photoshop required to get a blue version of a white icon.

I am not a web designer, my strength lies more with software architecture, so the new look and feel was developed with help from some Bootstrap themes and my desire to move towards a clean, simple site that focused on functionality and readability. In some respects, moving toward a Microsoft Modern UI (formerly Metro) style look, but without going all the way there.

I implemented the site with ASP.NET MVC3. I used a Legacy Route Handler to accomplish the redirection of old links to the new extension-less URLs in a way that provides a proper 301 Moved Permanently response to help search engines update their indexes.

Support for canonical URLs was implemented using the IIS7 URL Rewrite 2.0 extension.  It allows the definition of simple rules to manipulate URLs.  In my case, it was used so that multiple domains (like troyfarrell.ca) get redirected to my primary .com domain.  This is also important for search engines, to avoid duplicate indexing of the same content.

So that sums up what was important to me, when considering a site redesign this time around.  What do you think?  What did I forget?

9. November 2008 02:27
by Troy
0 Comments

PDC 2008 Scott Guthrie @ Open Space

9. November 2008 02:27 by Troy | 0 Comments

After returning from PDC 2008, I've finally had a chance to process some video that I recorded of Scott Guthrie who participated in an Open Space meeting for about an hour.  Unfortunately, I only recorded about 15 minutes of the action before my memory card filled up, but I guess that is better than nothing.

I did my best to clean up the audio, which had alot of ambient room noise.  I wish it could be better, but I think it is clear enough now to be understandable, if not somewhat enjoyable.

The video is hosted on YouTube and due to time restrictions on uploaded video, the content is split into 2 parts. 

In the first part,  Scott talks about:

  • ASP.NET and MVC Framework - the future of both and them co-existing with each other
  • Data Access - LINQ and the Entity Framework

In the second part, he discusses:

  • Functional Programming - programming WHAT you want done, versus the more typical HOW to do something, citing LINQ as a simple example
  • Moore's Law - gradually being replaced by new rules where the number of machine cores will begin doubling
  • Parallelism - efforts to make it easier for developers to take advantage of multiple cores through explicit APIs and implicitly through improvements to the CLR
  • F# and .NET 4.0
  • Dynamic Languages
  • WPF and Silverlight

Part 1
http://www.youtube.com/watch?v=9-62sSDTIMY

Part 2
http://www.youtube.com/watch?v=lXm60VnyZwo