> > Not that I know of. The development path as I understand it is moving > away from JSP altogether, in the direction of Manakin. I don't know > how I'd throw a Dreamweaver dev at Manakin; I suppose I might throw a > webcrawler at my Manakin instance and pass over the resulting HTML/CSS > to them, but I'm almost certain that would end up giving my Manakin > dev frothing-at-the-mouth fits. Anybody got any better ideas?
Our local process for developing a them: 1) Graphic design produces a composition, just a photoshop file of how the repository should look. 2) A web developer takes the photoshop file, splits it up into Manakin HTML + CSS. 3) The Manakin developer takes the CSS, installs it, interactive features like javascript, fixes any problems, browser compatibility On rare occasions step 2 and 3 are performed by the same person. Scott-- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
