syllabus
|
resources
|
IRL Chicago
|
Web Editor



epilogue
( beyond wwwired )





polishing up our wwweb game



if you’re interested in continuing to work with the wwweb as a medium beyond this course there’s a handful of things to consider...



1. get your own domain + hosting



there’s some serious limits to the school’s server, so the most important next step is to buy a domain name && pay for hosting on a serious server. if you don’t plan to keep making web based work at the very least you want to have a homepage, paying for hosting is like paying “rent” on a professionally maintained server ( usually goes for $2 - $5 a month for the basics ) and registering a domain name is roughly $14 a year ( depending on the extension you want, .com? .net? .guru? .xxx? .pizza? ...yes, that exists ). to the right are just a few places you can register a domain and pay for hosting



browsers && devices



to keep things under control in class we’ve stuck to one browser, chrome. but the reality is that you won’t have any control over what browser a user is using to access your web work… and unfortunately all the browsers interpret HTML && CSS a tad bit differently, so it’s important to check your work on multiple browsers before uploading it to the Internet.

similarly, theses days folks access the web on all sorts of devices ( laptops, phones, tablets, etc ) all of which have very different screen dimensions and resolutions. There’s a web design philosophy known as “Responsive Web Design” which is all about coding designs that are flexible and adjust to these various screen resolutions.



separate CSS && JavaScript files

as your website/projects begin to grow file management becomes extreamley important. for intro purposes we’ve been including CSS && JavaScript directly on our HTML pages, which is perfectly cool for small, single page projects, but once you get into multiple page projects ( all of which are using the same CSS or JavaScript ) it can be a pain to have to go back and change the same line of CSS code across multiple pages. Instead, it’s common practice to save your CSS code on it’s own file saved with a .css extention, then you “include” in the head tag of all your pages like this:

<link rel="stylesheet" href="css/styles.css" type="text/css">, you can have different CSS files and you can include as many as you want on any of your pages. the important thing is that when you edit this file it will update on all of the different HTML pages that include that link to it.

similarly, you want to save your javascript code as a separate .js file, and then include it in your html page ( either in the head or the body ) this way: <script src="myscripts.js"></script>