Comments on: Scripps in Beta http://webiscope.com/2008/05/scripps-in-beta/ Internet Healthcare Collaboration Mon, 30 Jan 2012 22:49:20 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Marc http://webiscope.com/2008/05/scripps-in-beta/comment-page-1/#comment-432 Marc Tue, 08 Jul 2008 22:08:28 +0000 http://webiscope.com/?p=108#comment-432 Email'd. Email’d.

]]> By: Meghan http://webiscope.com/2008/05/scripps-in-beta/comment-page-1/#comment-431 Meghan Tue, 08 Jul 2008 20:24:57 +0000 http://webiscope.com/?p=108#comment-431 Marc, Very informative article. Thanks for the post. The decision-makers in my organization are pushing for a commercial WCMS solution (Oracle/Stellant or Vignette) to give order to our current web chaos. It's frustrating since we have in-house development staff that are willing and capable of using open source technology to develop a CMS; yet I get the impression that senior management thinks we may be biting off more than we can chew by implementing a home-grown CMS . Did you encounter any of the same issues when going through your re-design? -LOVE the new site by the way- Marc,

Very informative article. Thanks for the post. The decision-makers in my organization are pushing for a commercial WCMS solution (Oracle/Stellant or Vignette) to give order to our current web chaos. It’s frustrating since we have in-house development staff that are willing and capable of using open source technology to develop a CMS; yet I get the impression that senior management thinks we may be biting off more than we can chew by implementing a home-grown CMS . Did you encounter any of the same issues when going through your re-design? -LOVE the new site by the way-

]]> By: Marc http://webiscope.com/2008/05/scripps-in-beta/comment-page-1/#comment-390 Marc Tue, 13 May 2008 19:13:00 +0000 http://webiscope.com/?p=108#comment-390 I laugh at RevolutionHealth's 150 developers. We had one developer. One incredibly talented, incredibly dedicated developer. Bart - we devoted the first week of the Month Of Development (hereafter: MOD) to requirement gathering, analyzing the current CMS, site structure, user models, &c... Luckily our developer had a couple of recent CMS projects in his back pocket so he was able to pull from his code library and make appropriate modifications. The CMS represents the bulk of the code base (15K+ lines of code all told) but probably only a week or two of development time, plus the time after beta launch we've spent tweaking and improving it. Buy-in from the organization and the decision to go with Ruby came out of necessity. We just couldn't get it done in-house and the clock was ticking for a variety of reasons. Some significant decisions were made under pressure but I wouldn't change any of them if I had to go back and make them again. We had a month to get it all done, I don't think a team of people could have completed it in that time (too much bureaucratic overhead) and I don't think another language could have gotten it done in that time. I laugh at RevolutionHealth’s 150 developers. We had one developer. One incredibly talented, incredibly dedicated developer.

Bart – we devoted the first week of the Month Of Development (hereafter: MOD) to requirement gathering, analyzing the current CMS, site structure, user models, &c… Luckily our developer had a couple of recent CMS projects in his back pocket so he was able to pull from his code library and make appropriate modifications.

The CMS represents the bulk of the code base (15K+ lines of code all told) but probably only a week or two of development time, plus the time after beta launch we’ve spent tweaking and improving it.

Buy-in from the organization and the decision to go with Ruby came out of necessity. We just couldn’t get it done in-house and the clock was ticking for a variety of reasons. Some significant decisions were made under pressure but I wouldn’t change any of them if I had to go back and make them again.

We had a month to get it all done, I don’t think a team of people could have completed it in that time (too much bureaucratic overhead) and I don’t think another language could have gotten it done in that time.

]]> By: Drew Diskin http://webiscope.com/2008/05/scripps-in-beta/comment-page-1/#comment-387 Drew Diskin Tue, 13 May 2008 11:05:41 +0000 http://webiscope.com/?p=108#comment-387 Love the use of menus and the clean design. It definitely invites the user and puts them in control. I believe RevolutionHealth used Ruby in their development, too- they used NavigationArts for UI and over 150 in-house developers. Love the use of menus and the clean design. It definitely invites the user and puts them in control.

I believe RevolutionHealth used Ruby in their development, too- they used NavigationArts for UI and over 150 in-house developers.

]]> By: Ed Bennett http://webiscope.com/2008/05/scripps-in-beta/comment-page-1/#comment-386 Ed Bennett Tue, 13 May 2008 01:41:28 +0000 http://webiscope.com/?p=108#comment-386 Marc, Great job - the new site packs lot's of options and navigation choices without feeling overwhelming. Web 2.0 is now the new normal. I'm also impressed at how quickly you handled the development process, and got buy-in from the organization. As for us – we‘re going in a different UI direction. Here’s our inspiration: http://producten.hema.nl/ (it’s in Dutch, just give a page a few seconds to load) Marc,

Great job – the new site packs lot’s of options and navigation choices without feeling overwhelming. Web 2.0 is now the new normal. I’m also impressed at how quickly you handled the development process, and got buy-in from the organization.

As for us – we‘re going in a different UI direction. Here’s our inspiration:

http://producten.hema.nl/

(it’s in Dutch, just give a page a few seconds to load)

]]> By: Bart http://webiscope.com/2008/05/scripps-in-beta/comment-page-1/#comment-385 Bart Mon, 12 May 2008 21:03:40 +0000 http://webiscope.com/?p=108#comment-385 Ruby on Rails is an interesting choice. We're a big fan of FOSS solutions here, and I feel your pain on deployment. How much of the development timeline was dedicated to building the CMS functions editors use? Where there any particularly good CMS samples for Rails out there you could leverage. It was a bold move putting the design vote to the organization. But what a great way to get buy-in from everyone. Kudos! I see the development office had a strong voice in the layout. I bet there's a good story, there. ;) Ruby on Rails is an interesting choice. We’re a big fan of FOSS solutions here, and I feel your pain on deployment. How much of the development timeline was dedicated to building the CMS functions editors use? Where there any particularly good CMS samples for Rails out there you could leverage.

It was a bold move putting the design vote to the organization. But what a great way to get buy-in from everyone. Kudos!

I see the development office had a strong voice in the layout. I bet there’s a good story, there. ;)

]]>