events
Brief: Mark-Up your tutorial + …
February 7, 200812:00 pm to 3:00 pm
First we’re going to practice some html. Towards what will become your online tutorial:
- Open a word processor (like Open Office, Text Edit or Word) and write down the text for your tutorial. Try to break it to titles, subtitles, lists, links, different elements or whatever you might think is relevant.
- Collect images, videos, audio, whatever media you would like to involve in this tutorial. Try to think how to take a similar approach like the one you took in your analog tutorial, but this time, make a webpage out of it.
- Install Firebug in your computer.
- Use your preferred text editor (like Emacs, Dreameweaver or Coda) to edit your html page. When in doubt use Firebug to check and steal code from other pages.
- When you’re done (or through the process of your work) try to validate your code through the W3C validator. Try to understand the feedback it gives to fix your errors, and strive to keep your html valid.
- when the html page is done (only html, no styling what so ever!!!) upload it to our blog and provide the link in your post. Your pages will be ugly, but will be pure data, which would look much better the week after.
- Post at least two HTML tutorial references that you found useful (not just any ones you’ve found), post it to our del.icio.us tag ‘osdp’ (which stands for Open Source Design Parsons) so we can start to share some resources.
Second, we’re each going to learn something new:
- Go through the tutorial you were given by your classmate, try to go through it while taking notes on your process, your experience, your challenge, your difficulties.
- Turn these notes with pictures (when it fits) to a post reporting on your experience. This would be valuable feedback for us to work with in the rest of the assignment.
- Try to not break anything…
- Enjoy.
See you next week.
