ok ... the most important thing is to completely abstract your output mechanism (this may seem trivial to you, but, in truth, too many people disobey this rule and too few tutorials emphasize this point), so in a compressed API you have the rendering mechanism (rely on HTML, XML, JSON or something similar), most likely using templates ... this is one of the fundamental aspects of request -based web applications , this is the real difference with desktop applications for me) and are covered by any best infrastructure ... using Using MVC architecture is the next step ... There are tons of MVC frameworks for almost any server language that do a lot of work for you ... and MVC is ideal for query-based applications ... the separation between business logic and performance the output works roughly with PERFECT ... the key point for a scalable web application is to implement your business logic, which usually includes databases ... this is also what you will have to work with a lot of ... creating good templates HTML is damn and work, but I would argue that it is relatively easy, as soon as you actually get it ... no need to come up with super-creative solutions and new approaches here ... plus, for me, style and skinning are interchangeable ... it’s much more difficult to create a good user interface that maximally reveals your functionality than to implement it or even invent it ..
if I were you, I wouldn’t be too much into CSS if you really don’t want DESIGN pages (to find someone else to do this, maybe even HTML templates). seriously, you will learn to hate it VERY fast, especially if you are trying to get it to work in IE7 or lower). rather, try creating awesome semantically well-structured HTML (good for SEO and accessibility) (see progressive improvement ) and learn JavaScript. look at some nice frameworks ... jQuery, Ext ... whatever ... don't reinvent the wheel here ...
haxe may also be of interest to you ... many useful libraries on haxelib ...
well, hope that helps ...;)
Greetz
back2dos
source share