Quote:
|
Originally Posted by Max Lobovsky
Its not a service, it's a piece of software. And yes, it definitley qualifies for the award. Disallowing any non-custom code for the website would be as stupid as requiring the robot to be built entirely from raw materials with the only purchaseable items being aluminum ore and petroleum.
|
Read that and wanted to play devil's advocate. Making robots out of ore and petroleum is more like writing an http server, and a language. My (limited) experience with build is that you order parts, not a complete grasping arm. I view PHP-nuke and alot of the larger CMS projects as similar to an arm, and not a screw or even aluminum ore.
There is a middle ground between having teams do everything themselves and nothing themselves. Not trying to bash any of the teams who have posted, but you do see sites here made using premade templates. Could we apply the same logic here? The look of the website is the aluminum ore! Its the special people who took the effort to open dreamweaver, or download a theme! What, then, would the website award honor? Is it an award for writing complete cohesive paragraphs? Or is it learning about how websites are built, and then applying it? I would hope that the emphasis is on teams putting together websites with as much done "internally" as possible.
Disclaimer: This was written by someone who actually enjoys sitting in photoshop or with his texteditor, and has been doing "web development" for years, so he doesn't really quite remember what it was like to put together websites the first time around.