Comments on: Avoid content delays – treat content like code http://contentcontentblog.wordpress.com/2008/08/13/avoid-content-delays-treat-content-like-code/ Content and SEO discussed Sat, 27 Jun 2009 22:30:40 +0000 http://wordpress.com/ hourly 1 By: Dan http://contentcontentblog.wordpress.com/2008/08/13/avoid-content-delays-treat-content-like-code/#comment-129 Dan Wed, 13 Aug 2008 16:12:03 +0000 http://contentcontentblog.wordpress.com/?p=522#comment-129 Thanks for the post. Hopefully issues like this are drawn out in the wireframes, but it still happens. Usually when everyone realises they need to start thinking about the easy content bit - it is just words after all. Well, actually it isn't. Don't get me wrong, it's great that everyone starts throwing around ideas for new content areas once they do catch on, but it's normally too late and is suggested when functionality can't easily be changed. Hence the importance of thinking all this through at the very beginning. Thanks for the post. Hopefully issues like this are drawn out in the wireframes, but it still happens. Usually when everyone realises they need to start thinking about the easy content bit – it is just words after all. Well, actually it isn’t.

Don’t get me wrong, it’s great that everyone starts throwing around ideas for new content areas once they do catch on, but it’s normally too late and is suggested when functionality can’t easily be changed. Hence the importance of thinking all this through at the very beginning.

]]> By: PM Hut http://contentcontentblog.wordpress.com/2008/08/13/avoid-content-delays-treat-content-like-code/#comment-126 PM Hut Wed, 13 Aug 2008 15:41:16 +0000 http://contentcontentblog.wordpress.com/?p=522#comment-126 I remember in the first job I had, the main project was developing a website for food products. The programming was fine (I was doing it with someone else), but the main issue (or at least we thought) was the design. The client kept on changing and changing the design. Finally, he agreed on one design. When we started adding the content, we discovered some major programming/interface/design issues that we needed to handle on both the backend and the frontend. The project was eventually canceled, but it was a good lessons learned for everyone, treat content as part of your code. One the same note, I have an article on PM Hut for getting technical requirements on web projects: http://www.pmhut.com/the-technical-requirements-specification-trs-in-web-projects I remember in the first job I had, the main project was developing a website for food products. The programming was fine (I was doing it with someone else), but the main issue (or at least we thought) was the design. The client kept on changing and changing the design. Finally, he agreed on one design. When we started adding the content, we discovered some major programming/interface/design issues that we needed to handle on both the backend and the frontend. The project was eventually canceled, but it was a good lessons learned for everyone, treat content as part of your code.

One the same note, I have an article on PM Hut for getting technical requirements on web projects: http://www.pmhut.com/the-technical-requirements-specification-trs-in-web-projects

]]>