Comments for siteworthy - web consulting, design, development, seo, usability, information architecture http://siteworthy.com innovate.create.stimulate. Sat, 03 Oct 2009 00:12:22 +0000 http://wordpress.org/?v=2.9.2 hourly 1 Comment on Do you measure your website by the yard? by Kurt B http://siteworthy.com/website-planning/do-you-measure-your-website-by-the-yard/comment-page-1/#comment-3 Kurt B Sat, 03 Oct 2009 00:12:22 +0000 http://siteworthy.com/?p=8#comment-3 This is actually an extremely accurate analogy, and one that my application developer would be amused by (his lawn is exquisite). The dark and nebulous nature of the 'backend' of websites is often the most overlooked and under-appreciated part of the development process, and that's saying a lot coming from a designer who tends to run screaming away from code. But there's a crucial connection between a tidy 'frontyard' and a clean, organized backyard. I'll call it 'code appeal' for the purposes of this post. What differentiates your yard from your neighbor's is attention to detail and a fundamental grasp of lawncare mechanics. It's visual, yet it's simultaneously functional. Successful website architecture is really no different, it's a proprietary, harmonious blend of design flair and intuitive functionality. But let's face the facts: at the end of the day, it all boils down to how much gas you've got for the mower and how big a budget the client has for the project. Without either, nothing's getting mowed. If the backend is a custom CMS, then usability and flexibility should be of primary importance, and it's part of our job to sell the client on the importance of having a backyard big enough to work in. The landscaping is flexible! If every developer would pause during each phase of their website project and assess whether this harmony is still in place, the final result will inevitably be fresher, greener. More healthy. Best of all--the backend will be free of chinch bugs! This is actually an extremely accurate analogy, and one that my application developer would be amused by (his lawn is exquisite). The dark and nebulous nature of the ‘backend’ of websites is often the most overlooked and under-appreciated part of the development process, and that’s saying a lot coming from a designer who tends to run screaming away from code.

But there’s a crucial connection between a tidy ‘frontyard’ and a clean, organized backyard. I’ll call it ‘code appeal’ for the purposes of this post. What differentiates your yard from your neighbor’s is attention to detail and a fundamental grasp of lawncare mechanics. It’s visual, yet it’s simultaneously functional. Successful website architecture is really no different, it’s a proprietary, harmonious blend of design flair and intuitive functionality.

But let’s face the facts: at the end of the day, it all boils down to how much gas you’ve got for the mower and how big a budget the client has for the project. Without either, nothing’s getting mowed. If the backend is a custom CMS, then usability and flexibility should be of primary importance, and it’s part of our job to sell the client on the importance of having a backyard big enough to work in. The landscaping is flexible!

If every developer would pause during each phase of their website project and assess whether this harmony is still in place, the final result will inevitably be fresher, greener. More healthy. Best of all–the backend will be free of chinch bugs!

]]>