Build yourself a library of additional extensions to even speedup your development. This all in a framework of approximately 250Kb of binary code. Why an XMLSpider. If we look at how we used to write ASP pages. We started by creating a database model and based on that model we create a bunch of components, mostly these components where based on collections and item objects.
E.g. customers hold a collection of customer objects .
This is correct if you are building a state-full application but not for a stateless application, as an internet application should be. After we had build our components we had to combine the design and the data of presentation. I as a developer am not a designer and a designer is not a developer. Here you will have to make sure to give both persons a environment that they feel comfortable in. This because XSL is very easy readable and if presentations are build a minimum of XSL is required to build up that presentation.