Monday, October 27, 2008

like falling off a log


An assignment for the subject: Monitor traffic and compile website traffic reports.

Write a few pages outlining which reports you would recommend from a web log analysis program for the following 3 groups: web owner, system admin & web developer.

Include some screenshots of each report and some information on how often they should be accessed; what information they are showing and why it is important to the viewer; and what problems might be indicated by the report (along with some ideas about how to solve them if they do come up)

Also include some analysis of a web site - particularly what times are the busiest and the slowest and when it might be best to schedule updates to the site.

Image: 'Log Texture'
http://www.flickr.com/photos/82518118@N00/2313754224

Monday, September 15, 2008

more validation


I was thinking of u all fondly today and thought you deserve a little present:

fValidator is an open source (free) unobtrusive javascript tool for easy handling form validation. It allows a user to more easily enter fixed width input where you would like them to enter the data in a certain format (dates,phone numbers, etc). It also displays error messages right where you want them - just the ticket for your form validation needs.

Image: 'My plane ticket'
http://www.flickr.com/photos/44124300615@N01/2432095214

Sunday, September 14, 2008

absent note

first up, please accept my apologies for being absent today. I did a pretty stupid thing on Saturday and need to lie around feeling remorseful for a bit (the pic here isn't my bike, but it's a pretty close approximation - I lost a little skin, sprained a few joints, cracked a rib, may have broken my thumb... and got off pretty lightly, all things considered).

On the Javascript front, I believe we just finished looking at form validation. To practice a bit I'd like you to create a contact form which prompts for a name, phone number, email address and comment - checking validity for each before submitting. For bonus points add an age field and check for a valid age (say between 5 and 105). Errors or omissions should be flagged by revealing an error message beside the relevant field using CSS and DOM magic.

Finished? Read through and try out some more advanced DOMination

CU soon, Peter

Image: 'Picture073_11Sep04'
http://www.flickr.com/photos/89689539@N00/373976620

Wednesday, August 27, 2008

loopy


This week saw us trying out some JavaScript looping

Read through a little intro and try out the exercises I've uploaded here:

http://bathurst-tafe.nsw.edu.au/~pshanks/javascript/loops-exercises/

Image: 'loopy'
http://www.flickr.com/photos/86176561@N00/273326027

Monday, August 11, 2008

making choices


Inclement whether prevents my attendance in person, but I'm with you in (e)spirit.

Today we're looking at conditional statements in JavaScript (if/then/else). These are described in the handout, page 14. Unfortunately that's not quite the whole story - you really need to know a bit about multiple if statements (and their clever cousin, the switch statement). See the web cheat sheet for a fine explanation/demonstration.

If you're keen to become a real JavaScript geek you might also want to know about the 'conditional operator' described about half way down this page by the Washington center for environmental visualisation(?).

Fully read up?

Try these interesting exercises (in groups, or as a hard old loner)...

  1. Open http://bathurst-tafe.nsw.edu.au/~pshanksjavascript/conditionals-exercises/conditionals1.html in your favourite editor.
    In this exercise, you'll write a function called guessAge() that, oddly enough, lets the user guess your age. The user's guess is in document.ageForm.ageGuess.value. The guessAge() function should pop up an alert box telling the user whether or not s/he guessed correctly.

  2. Open http://bathurst-tafe.nsw.edu.au/~pshanksjavascript/conditionals-exercises/conditionals2.html in your favourite editor. You can copy your completed conditionals1.html to conditionals2.html if you'd like to edit your existing work rather than starting from scratch.
    In this exercise, you'll modify your age guesser from exercise #1 to provide some additional feedback to the user. The guessAge() function's alert box should let the user know if s/he guessed correctly, if you're younger than the guess, or if you're older than the guess.

  3. Open http://bathurst-tafe.nsw.edu.au/~pshanksjavascript/conditionals-exercises/conditionals3.html in your favourite editor.
    Everyone knows that flowers need water to grow. This HTML page has a watering can and a flower. This particular flower needs to be watered three times before it can grow. When the user clicks on the watering can, it should change to the image shower.jpg. After one second, the watering can should stop watering the flower. (We provide this code for you; read the comments in the program carefully.) The third time the user waters the flower, the flower should bloom. (There's an image of a bloomed flower in flower.jpg.)


Image: '"It is our choices. . . that+show+what+we+are,++far+more+than+our+abilities."'
www.flickr.com/photos/12596956@N06/2699207704

Sunday, August 10, 2008

JavaSkipped


suddenly realised that I've been very remiss about posting relevant JavaScript links here. Time to make amends.

First up, we've been working from a document I found on the interweb: a JavaScript tutorial. Thanks to the wonders of modern science this plain web page is now available as an open office document (37k) or a microsoft word doc (180k).

So far we've worked through the following sections:
1. Introduction

2. Embedding JavaScript into your HTML document

3. Variables

3.1. What are Variables?

3.2. Values of Variables

3.3. Data Type Conversion

4. Literals

4.1. Integers

4.2. Floating-point literals

4.3. Boolean literals

4.4. String literals

4.5. Escaping characters

5. Arrays

6. Operators

6.1. Selected assignment operators

6.2. Comparison operators

6.3. Selected Arithmetic Operators

6.4. Logical Operators

7. Using JavaScript Objects

8. Functions

8.1. Defining a Function

8.2. Calling a Function


We also applied ourselves to the following exercises:

Variables: open document (33k), word (101k); and functions (grab the contents of http://bathurst-tafe.nsw.edu.au/~pshanks/javascript/function-exercises/ and fix the html pages: functions1.html through functions6.html).


Image: 'Zion and Tracy jumping'
www.flickr.com/photos/81859405@N00/260323975

Wednesday, July 30, 2008

SQL has a new home

to celebrate our combined CertIV SQL class I've created a new blog just for our database subject. You can see it and read all about our subject on:

http://certivsql.blogspot.com/

Wednesday, July 23, 2008

SQL like a stuck pig


Yahoo. Back for a new season of coding!

This semester we're going to spend a fiar slab of time learning structured query language (SQL to its friends).

To get into this we need to install a local web server, database server and database manager. Luckily someone has already put a package together for us to download and install. Xampp (38 MB from Apache friends) has everything an aspiring SQL guru could want.

After downloading and installing start the xampp control panel (it will be something like: C:\xampp\xampp-control.exe) and start up apache and mySQL by clicking on the start button for each.

Now open your web browser and test the installation by entering http://localhost into the address bar. You should be seeing something like this (you may need to click on the 'English' link first)...


click on the phpMyAdmin link in the tools section of the left hand menu to start up our database manager.

Before we can start entering SQL statements we need to create a new database to work with.

In this screenshot I'm about to create a new database called fred (you can click on the image for a larger version).

Now that we have a database we need a couple of tables and some data to play with. I've put together a little file to make this as panless as possible. Download ICAU4205A.sql and save it on your computer.

Once you've got it, click on the 'Import' tab at the top of the phpMyAdmin screen, browse to the file and click on the 'Go' button on the bottom right of the screen.

phpMyAdmin should do its magic and report back that "Import has been successfully finished, 16 queries executed." You should also see 5 new tables listed in the left hand column.

Time to get down to business.

For the next couple of weeks we're going to work through James Hoffman's Introduction to SQL

This week, everything up to the section on joins. Click on the 'SQL' tab at the top of the phpMyAdmin page and type in each of the examples in the document. Play a bit, have fun, and tune in here next week for another exciting installment...


Image: 'OINK! OINK!'
http://www.flickr.com/photos/49968232@N00/51679641

Monday, June 23, 2008

Debugging challenge


Spot the fault...

Assessment for the subject: Locating equipment, system and software faults will consist of a document listing various JavaScript faults, how they present themselves, what caused the error and how to fix it.

Run through this list of debugging challenges and choose 2 or 3 from each section: Lexical Errors; Syntactic Errors; Execution Errors; Logic Errors. Write up a short description of the problem (how it presented itself), what you found and how you fixed it. Screenshots would be handy.


Original image: 'Fixed' http://www.flickr.com/photos/27384730@N00/109566859
by: Mike Fernwood

Tuesday, June 10, 2008

fine tuning

We finished automating processes last week, looking at breaking down larger programs into sub-routines and procuedures. Next week we'll put the final nail in with a short quiz.

We followed that up with a look at functions and objects in JavaScript (which wasn't all that interesting), and revisited variables and data types (which was more relevant, if no more gripping)

We finished up with another look at locating equipment, system and software faults specifically, task 2: obtaining fault finding tools. To be honest, I'm not all that happy with these course notes (the readings are fine, but the activities seem too nebulous) - so I'm going to revert back to my original plan for this subject - concentrating mostly on debugging code, with a passing nod at equipment and some discussion of systems.

So, for task 2 I'd prefer that people investigated options for debugging JavaScript - either in the browser or using a stand-alone solution. Write up a blog post that discusses the options available for your platform of choice. Don't forget to include a description of that platform - versions and types of operating system and browser (if applicable).

The report should be about 500 words in length and should be ready for comment by next week.

Speaking of next week - we're going to make a start on 'Run standard diagnostic tests'. I had planned on testing web site performance, but have been told that the Cert III I.T. class will be attending the class too - and they've got no prior experience with web technologies, so we might need to take a different approach. Given that we've only got two weeks to cover the subject this will be a busy lesson - so don't be late :-)



Image: 'scroll & peg'
www.flickr.com/photos/46534015@N00/1899595427

Monday, June 02, 2008

looping

Last week saw us spiraling out of control... exploring loops.

Try these revision questions, and a new, improved cloze test on while loops.

We also learned how to use JavaScript to validate a form on a web page, looking at form fields and loops in the process!

Finally, we started on the first task for Locate equipment, system and software faults... Identifying appropriate information gathering techniques



Image: 'Vatican Museum Spiral Stairs'
www.flickr.com/photos/57954193@N00/202549889

Sunday, May 25, 2008

thinking back on it

revising last week's programming lessons...




Image: 'thinking'
www.flickr.com/photos/83476873@N00/110993877

Wednesday, May 21, 2008

good news


... also: for those of you keen to start on the module 'Locate equipment, system and software faults' I've uploaded some material for you to play with. See http://bathurst-tafe.nsw.edu.au/~pshanks/ICAT4221A/index.htm (or http://192.168.201.2/~pshanks/ICAT4221A/index.htm if you're trapped inside the firewall)



Image: 'untitled'
www.flickr.com/photos/88997175@N00/104197534

Monday, May 19, 2008

need... more... oxygen...



Today's epic journey started in the plains of if-then-else before ascending the foothills of datatypes. It finished with an attempt on the icy peaks of JavaScript selections. This was a tough climb, but what a view there is from the top!

Believe it or not, this is as high as we're going to ascend. Next week we'll stay at this altitude for a short while, exploring the whacky world of loops before descending back to sea level.



Image: 'Peak of Snæfellsjökull in clouds'
www.flickr.com/photos/25147065@N00/506183053

Monday, May 12, 2008

exercise


Some calisthenics for your brain...

1. Cut and paste the JavaScript code from the 'she's apples' entry below and then format it so each block of code is correctly indented.
2. Try out the Cloze test for IPO Models
3. Attempt the 'Develop an algorithm' quiz
4. Click randomly on terms and definitions in the JavaScript cloze test




Image: 'My name is Charles Atlas'
www.flickr.com/photos/37912374286@N01/98379123

she's apples



Today we looked at developing algorithms.

This was followed by a quick look at JavaScript in JavaScript Basics, Part 1.

Extending the lesson a little we came up with the following super-apple-eating algorithm...

<script type="text/javascript">
var apples = 5;
alert('there are currently ' apples ' apples');
var eat = prompt('How many apples would you like to eat?', '1');
if (parseInt(eat))
{
if (parseInt(eat)>apples)
{
alert("don't be greedy!");
} else {
apples -= parseInt(eat);
if (apples > 0)
{
if (apples == 1)
{
alert('There is only one apple left!');
} else {
alert('Now there are only ' apples ' apples!');
}
} else {
alert('no more apples for you!');
}
}
} else {
alert('there are still ' apples ' apples');
}

</script>




Image: 'Granny Smith'
www.flickr.com/photos/90581837@N00/78379799

Sunday, May 11, 2008

making a splash - refreshing your knowledge


Time to reinforce those little lessons we learned last week. Try out these questions on trainingo2.net, and then take a few minutes to pit your wits on the cloze test for pseudocode.





Image: 'Grapefruit Splash'
www.flickr.com/photos/11419506@N08/2272752165

Monday, May 05, 2008

today's exciting installment

This week we continued our exploration of the programming landscape.

After a quick bash at a cloze test on syntax, we created and worked through a new page on algorithms (including the creation of our first bit of javascript).

Wasn't that all fun? \*(^_^)*/



Image: '2008-03-04 (Field Guide to GP photos) - 05'
www.flickr.com/photos/68457656@N00/2322867309

Sunday, May 04, 2008

pop quiz


To recap what we covered last week in our first automate processes lesson, jump on over to trainingo2.net and try out this quick quiz



Image: 'Jellypops'
www.flickr.com/photos/99136715@N00/51613644

Thursday, May 01, 2008

buried treasure


I know you're all very busy, but if you get some time you should check out the resources on Smashing Magazine's Best Of April 2008 page - some of this stuff is gold.



Image: 'buried treasure'
www.flickr.com/photos/35468137797@N01/64228609

Tuesday, April 29, 2008

intro to programming

Hope you all had a good break - I certainly did. It was totally unsullied by any menial tasks like marking web development assignments - but don't panic, I'll have some nasty comments for you by next week... I promise :-)

This week we're launching into programming proper, working through Robyn's excellent notes and converting them to web pages, which should give us plenty of html and css practice along the way. So, create a week1a page with some extra scripting and compiled languages on the relevant table, also create a home page linking to your week1a page and upload both new pages to your web space on the bathurst-tafe sever.

Images can be created from screen captures (hoversnap might be handy for this) or you can find creative commons licensed images via flickrcc (don't forget to add the attributions at the bottom of your web page)



Image: 'the only flow-chart you will ever need'
www.flickr.com/photos/55847834@N00/1229271594

Monday, April 07, 2008

taking shortcuts

Today we're looking at a CSS template: blueprint
and an online grid editor for the same.

Tuesday, April 01, 2008

validation


^ This is what you want to see. To test a page that's been uploaded to the server you can use the validation options on the firefox web developer toolbar (found under 'tools').

You can also go straight to the W3C validation page. Note the tabs on the page which allow you to enter a URL, upload a file or cut and paste code.

Finally, if you enjoyed yesterday's PMOG mission, there's another one on validation that you could take.

At the end of the day I'd like you to validate one or more pages on your Bathurst TAFE web site and include the little validation link that the W3C give out when you pass their test.

Sunday, March 30, 2008

Image mapping

Today we're giving PMOG a bash, with a little image map mission that I've put together for your learning pleasure. You'll need a login (send me an email if you need an invitation - I think they're out of beta now, but I could be wrong). You'll also need a firefox addon (there's a link on the PMOG site). Have fun.

Sunday, March 23, 2008

happy easter

I know you'll all miss our weekly get together - the same way I know you probably wouldn't do any exercises that I post here. So here's a compromise... an excellent CSS cheat sheet. Print it out, memorise it and then eat it so that it can't fall into enemy hands.

Monday, March 17, 2008

tables and backgrounds

Today we worked through the backgrounds tutorial on tizag

If you want to experiement there's a background image library on http://www.grsites.com/textures/

We finished up with some work on creating tables, followed by a table exercise on the wikiversity.

If you're feeling chirpy, try the harder advanced table exercise

Image: 'buena vista'
www.flickr.com/photos/70825417@N00/358756373

Monday, March 10, 2008

CSS for layout


This week we're looking at how to use CSS to lay out a page. To kick off, work through this tutorial on subcide called 'Creating a CSS layout from scratch' (up to, but not including page 10, the navigation).

There are some interesting techniques used here to ensure the divisions stay in the right places. And some not-so-interesting uses of graphics instead of text (did you spot them? What would you do differently?)

One thing I noticed was a lot of code in this tutorial that set the padding and margins for various elements to zero. If you're wondering why, there's a good article on the subject called 'No Margin For Error'

Taking the idea of stacking DIV boxes to make a page layout one step further, here's two more web pages to look at:

  • layout-o-matic - which lets you plug in some variables and automagically generate some CSS
  • Little boxes - which has a set of templates ready to download

Once you've explored these a little, revisit your '10 things' page and apply some CSS layout so that there's a column on the left of the content. Put an unordered list of links to each detail page in this column. For bonus playing time, decorate your left hand column list using some CSS from the listamatic.

At the end of the day you should have some html that looks like:

<html>
<head>
<title>title</title>
<link rel="stylesheet"
type="text/css"
href="css/default.css" />
</head>
<body>
<div class="breadcrumbs">
<a href="index.html">Home</a>&nbsp;.
</div>
<div class="title">
<h1>Title</h1>
</div>

<div class="sidebar">
<ul>
<li>
<a href="index.html">Home</a>
</li>
<li>
<a href="thing1.html">Thing 1</a>
</li>
<li>
<a href="thing2.html">Thing 2</a>
</li>
<li>
<a href="thing3.html">Thing 3</a>
</li>
<li>
<a href="thing4.html">Thing 4</a>
</li>
<li>
<a href="thing5.html">Thing 5</a>
</li>
<li>
<a href="thing6.html">Thing 6</a>
</li>
<li>
<a href="thing7.html">Thing 7</a>
</li>
<li>
<a href="thing8.html">Thing 8</a>
</li>
<li>
<a href="thing9.html">Thing 9</a>
</li>
<li>
<a href="thing10.html">Thing 10</a>
</li>
</ul>
</div>
<div class="content">
<div class="pic">
<img src="xxx.gif" alt="a picture" height="200px" width="150px" />
</div>
<div class="wikiquote">
<p>some text from the wikipedia</p>
</div>
<div class="backgroundinfo">
<p>why this item made my list</p>
</div>
<div class="credits">
<p>Flickr Image: <a href="#">pic name</a></p>
<p>Wikipedia Article: <a href="#">wiki article title</a></p>
</div>
</div>
<div class="footer">
<ul>
<li>
<a href="index.html">Home</a>
</li>
<li>
<a href="thing1.html">Thing 1</a>
</li>
<li>
<a href="thing2.html">Thing 2</a>
</li>
<li>
<a href="thing3.html">Thing 3</a>
</li>
<li>
<a href="thing4.html">Thing 4</a>
</li>
<li>
<a href="thing5.html">Thing 5</a>
</li>
<li>
<a href="thing6.html">Thing 6</a>
</li>
<li>
<a href="thing7.html">Thing 7</a>
</li>
<li>
<a href="thing8.html">Thing 8</a>
</li>
<li>
<a href="thing9.html">Thing 9</a>
</li>
<li>
<a href="thing10.html">Thing 10</a>
</li>
</ul>
</div>
</body>
</html>

and some CSS that includes:

.content {
margin-left: 150px;
}
.sidebar {
float: left;
}

Monday, March 03, 2008

godzilla vs. filezilla


Today we looked at installing and setting up our own ftp client - filezilla (the client not the server). For the full scoop on ftp, including the all important difference between active and passive modes, check out this little wikipedia entry.

Now, I need you to write a blog post on your ftp experiences so far. If you haven't tried your second ftp client yet, pick one from the list, install it, and take it for a spin - then post an entry on your blog comparing it to your first client (core ftp-lite).

In the blog post tell me which one (if either) will you be using from now on and why. Some other things you might mention include:

  • The name of your ftp client
  • The URL you got it from
  • any installation woes you encountered
  • some comments on its ease of use
  • $
  • the platform(s) it works on
  • the install file size
and any other interesting bits of information you came across. cu next week. bbb





Image: 'Houston, we have a problem.'
www.flickr.com/photos/76074333@N00/301015327

more on lists and CSS


We re-visited our template today, looking at how we could apply CSS to the blocks on the page in more detail.

A couple of the areas we covered were:


Here's how the html template looked like when we'd finished with it:

<html>
<head>
<title>title</title>
<link rel="stylesheet" type="text/css" href="css/default.css" />
</head>
<body>
<div class="breadcrumbs">
<a href="index.html">Home</a>&nbsp;.
</div>
<div class="title">
<h1>Title</h1>
</div>
<div class="pic">
<img src="xxx.gif" alt="a picture" height="200px" width="150px" />
</div>
<div class="wikiquote">
<p>some text from the wikipedia</p>
</div>
<div class="backgroundinfo">
<p>why this item made my list</p>
</div>
<div class="credits">
<p>Flickr Image: <a href="#">pic name</a></p>
<p>Wikipedia Article: <a href="#">wiki article title</a></p>
</div>
<div class="footer">
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="thing1.html">Thing 1</a></li>
<li><a href="thing2.html">Thing 2</a></li>
<li><a href="thing3.html">Thing 3</a></li>
<li><a href="thing4.html">Thing 4</a></li>
<li><a href="thing5.html">Thing 5</a></li>
<li><a href="thing6.html">Thing 6</a></li>
<li><a href="thing7.html">Thing 7</a></li>
<li><a href="thing8.html">Thing 8</a></li>
<li><a href="thing9.html">Thing 9</a></li>
<li><a href="thing10.html">Thing 10</a></li>
</ul>
</div>
</body>
</html>


and here's the final CSS:
.backgroundinfo {
background-color: pink;
text-align: center;
margin-left: 20%;
margin-right: 20%;
border: 2px;
border-style: dotted;
border-color: purple;
}
.breadcrumbs {
background-color: red;
padding: 5px;
border: 0px;
border-color: blue;
border-style: dashed;
margin: 5px;
float: left;
width: 10em;
}
.breadcrumbs a:link {
text-decoration: none;
color: yellow;
}
.breadcrumbs a:visited {
text-decoration: none;
color: yellow;
}
.breadcrumbs a:hover {
text-decoration: underline;
color: blue;
}
.credits {
background-color: #eeeeee;
padding: 5px;
border: 1px;
border-color: blue;
border-style: dashed;
margin: 5px;
float: right;
width: 25%;
margin-top: -45px;
font-family: sans-serif;
font-size: x-small;
}
.footer {
clear:both;
}
.footer a:link {
color: white;
text-decoration: none;
padding: 3px;
}
.footer a:visited {
color: white;
text-decoration: none;
padding: 3px;
}
.footer a:hover {
background-color: skyblue;
color: navy;
text-decoration: none;
padding: 3px;
}
.footer li {
display: inline;
padding-right: 7px;
list-style-type: none;
}
.footer ul {
background-color: navy;
color: white;
padding-left: 0;
margin-left: 0;
font-family: sans-serif;
font-size: xx-small;
}

.title {
background: gray;
clear:both;
text-align:center;
margin-top:1px;
}
.pic {
background: skyblue;
text-align: center;
display: block;
margin-left: auto;
margin-right: auto;
}
.pic img {
border: 5px;
border-style: ridge;
}
.wikiquote {
background-color: purple;
text-align: center;
font-style: italic;
margin-left: 20%;
margin-right: 20%;
margin-top: -20px;
border: 5px;
border-style: double;
border-color: orange;
}

body {
margin: 0px;
}



Image: 'consume now3'
www.flickr.com/photos/17949364@N00/202924682

Monday, February 25, 2008

making a list and checking it twice


whew, what a wild ride we had this week.

We started out by creating a new page titled "Ten things I want to do before I die" - saving it as an index.html file in a new directory called tenthings. On this page we created an ordered list of... 10 things we wanted to do before shuffling off this mortal coil.

Then we spent a little time designing a topology map of a site we could build around this page; 10 more pages with details of each of our ten things, links to each of these pages from our index, links from each detail page to the index page and to the next and previous items in the list.




Next we looked at designing the layout for a typical detail page. Paragon of page design that I am I came up with the following jewel...

What followed was a whirlwind of activity...

  • Locating and saving an image (into an images directory) from flickrCC
  • Inserting said image on the page (including setting the alt, height and width attributes)
  • Making the image into a clickable link back to the original page on flickr
  • Using CSS to remove the unsightly blue border using an embedded or internal style tag in our document's head section
  • Creating a CSS div and adding a class name of "quoteblock" for a wikpedia quote about our goal.
  • Putting an H2 and blockquote into that div and cutting and pasting some wikipedia text there.
  • Setting the border, padding, background-color and font-style for our quoteblock class
  • Giving the other blocks on the page a similar treatment
  • Removing the CSS and putting it into an external style sheet so we can use it in the other 9 detail pages too.


Image: 'Dead Can9t Dance'
www.flickr.com/photos/19487674@N00/407283421

Monday, February 18, 2008

Head first into web development


For this subject (and our CSS module) we'll be using the excellent text: Head First HTML with CSS and XHTML. It's not compulsory that you buy a copy ('though it wouldn't hurt), but you will need to visit their web site and download the example files.



Image: 'Freefall'
www.flickr.com/photos/17088109@N00/1157425229

Saturday, February 09, 2008

Welcome


Hello and welcome to the Bathurst web class for 2008. This will be a great year I think.

So that we can keep in contact, I'll be posting lesson notes here on the cert IV weblog which might be worth bookmarking (perhaps in a del.icio.us account).

During the course I'll be asking you to post material on-line; reflections, interesting finds and assignment answers (for a great example from last year's class, check out Sharlene's blog) If you don't already have one, I'd like you to create a blog of your own. Blogger is a good free offering, but there are many others.

Once you have a blog set up, bookmark it, write an introduction about yourself and what you hope to get from this course and then come back here and leave me a comment with the web address of your space (copy and paste from the browser's address bar) - when I get the URL I'll add it to the hall of fame on the right :).

Another tool we'll be using a lot this year is the Training O2 website. Create an account there and then search for htmldog. Visit the link that comes up for the html beginner tutorial and work through the first four lessons: getting started; tags, attributes and elements; page titles; paragraphs and headings. After you've worn yourself out go back to the detail page for htmldog on the training o2 site and leave a comment on what you thought of the tutorials. For bonus marks see if you can figure out how to vote for the htmldog web site.

Whew, that's probably just about a brainfull for the first day, but if you want to do more, post another entry on your blog about your impressions of the web course so far - I'd love to hear what you think.



Image: 'Entry into the Celaphopad'
www.flickr.com/photos/35034345972@N01/340449446