I’ve been working my way through HTML, XHTML & CSS for Dummies which is all very exciting. It’s early stages at the moment, so most of what it’s told me so far isn’t new (apart from the fact that in XTML, empty elements must end with a slash before the closing greater than symbol and there should be a space before the slash like this <tag />).
Anyway, the book has a habit of mentioning useful links without really explaining them or drawing any attention to them. One such link is http://validator.w3.org. This is a free markup validation service which will highlight any errors or issues with your markup. (You can get it to check any webpage and it’s actually quite fun putting some of your favourite sites in and seeing how many errors they come back with!).
The next part of my challenge was to find a suitable text editor to replace the default Notepad the comes with Windows. I wanted something free so I tried 3 options:
I typed out the code that I had previously learned (from memory – yey!) and then played around with the editor to see what it could do. I found Notepad++ to be pretty user-friendly and clear. One of the features I particularly liked is that it draws vertical lines to show you how your code lines up, which makes it easier to get an overview of the structure and spot any errors:
I then chose ‘Launch in Firefox’ from the ‘Run’ menu to see how my webpage looked – easy!
Notepad++ also seems to be very popular with lots of documentation and plugins.
As a newbie, I found ConTEXT a bit less intuitive than Notepad++, although I did like the fact that the developer was happy to be paid in beer!
SourceEdit has a built-in FTP manager and support for previewing the HTML code in the web browser directly from within SourceEdit. However, I didn’t like the interface very much and it didn’t have line numbers.
Verdict: I am going with Notepad++ for now but reserve the right to swap to a new editor as my skills develop and I learn what all the functions are!
The next task after setting up a blog for the Webmaking 101 course is to write out some code by hand. This is the first time I’ve done this and I have to say that, even though I hate my handwriting, I found it a pretty rewarding experience.
One of my frustrations with HTML is that I’ve got a pretty bad memory and it just doesn’t seem to stick in my brain, so I’m constantly referring to cheat sheets when I could work a lot faster by knowing the code off by heart.
It’s a well known fact that writing things down – preferably lots of times – helps to embed them in the memory and I found that writing out the HTML by hand helped it to start to sink in. There’s a long way to go, but I feel like I’m starting to get to grips with the structure of an HTML document.
Posted in HTML
Tagged code, HTML
I decided that it was about time that I honed my HTML and CSS skills and I came across the excellent Peer 2 Peer University open education project to help me do just that. In this blog, I will chart my progress, hopefully connect with other learners and share experiences.
I have always been interested in web development and have my own website to showcase my photography. I also work in communications for Voluntary Arts England and my role involves developing the website and social networks. I have picked up bits and bobs of HTML and CSS on a need-to-know basis, but now I’m looking to take my skills to the next level.