Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If it's as much a learning exercise as anything then take an iterative approach. Build revise. Build revise. My (very) rough guideline below:</p> <p><strong>Client</strong> </p> <ol> <li>Start with the structure of a website and concentrate on the client.</li> <li>Use notepad and build a bunch of static pages for your band. i.e. Hand code initially. Try to build all your pages with CSS. No table markup. Then play around with some Javascript to bring things to life. (Navigational menu\ Calendar selections\etc). Learn about how to import and link to Javascript and CSS files.... and how these files are treated re:caching etc.</li> <li>Try to learn up to the limits of what you can do on the client (generally). Factor in the nuances of 3-4 browsers (Firefox/IE6/IE8/Chrome) re:DOM and client side eventing.</li> </ol> <p><strong>Server</strong></p> <ol start="4"> <li>Then start looking for what you might want to change across pages/sessions. i.e. what needs to be manipulated server side. And pick a server side technology.</li> <li>Start with basic post-back processing. Forget databases at this point. Learn how your framework of choice maintains state..... not just the name of the technology but the real nuts and bolts of it. One of your single greatest assets as a web developer is understanding the state model(s) of the technology you're using. </li> <li>Then go for a deep dive on the web server technology of choice (and in general). Understand the full request pipeline from client to server and back. This will teach you forms, http and its verbs, web server, filters and modules, server to framework hand off, page and control life cycles, back to the client. </li> <li>Now start working on dynamic content injection and the like. How to make and use reusable components in your web pages.</li> <li>Databases, caching, performance and diagnostics.</li> <li>Then get into into all the fun stuff like ajax, etc. Replace your javascript with jQuery, etc.</li> <li>Then you got the whole Webservices\XML\JSON\etc side of things to discover.</li> </ol> <p><strong>Resources</strong></p> <p>Well the web obviously. For client side stuff, going to the sites of companies who make third party web controls can be quite interesting. Asking how the hell they did that? Viewsource is your friend. Look at how they structure and build their pages. Pick a couple of good web designer sites, and you find a plethora of rants about browser wars etc that will give you good (under the hood) info.</p> <p>Once you hit server side, I'd go for white paper type learning from your vendor of choice for your technologies.i.e. webservers/frameworks/etc. Again find a 3rd party howto/evangelist site (I used to use a lot of "4 guys from Rolla" for example) that will demonstrate how to do various things. Language learning is ongoing. Basically just do the best you can till you find a better way.... and always be on the lookout for a better way. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload