Now and again I read a comment to the effect that some WSB member would like to insert a graphic into her post, but she doesn't know how.
Fear not, Blogizens: I'm going to tell you how to do it. But first you must promise to read my caveats following the step-by-step instrux below.
Do you promise?
OK, good.
Step 1) Find the "address" of your chosen graphic on the Internet.
Step 2) Type the following line of html code, using the specific info for your image file:

Type everything exactly as you see it above, changing the text between the quotation marks to the exact location and name of your image file. Note: generally, the location of your image will start with http://www. but this is not always the case. Not all Web sites begin with "www" for example.
Step 3) View your post to verify that you put in the html correctly, making corrections as necessary.
Example:
For the example below, I uploaded an image file called "zaius_cowboy.jpg" on my personal Web site (roominate.com), in a directory called "blogg." To insert the image into the current post, I typed a line of html code pointing to the image file's exact location.
The specific line of html code I typed looks like this:

— and when I saved my post, the Blog software automatically inserted the graphic, which looks like this:

It's as simple as that.
The key points to remember are that you have to point the line of html code to the exact location of your graphic, and you have to use the exact syntax I listed above. If you leave out the quotes, or the angle brackets, or if you get just one of the letters in the directory or file name wrong, the insertion will fail and the Blog software will either display a little red "x" (indicating that it can't find your picture at the location you listed) or it will delete your line of html code all together (indicating that you have a fatal error in your html code).
The good thing about the WordPress blog software is that you can make a mistake inserting a graphic and it will leave the rest of your post intact. The bad thing is that it won't tell you where you went wrong with your code.
That's enough info for one post. Stay tuned, and I'll give you some caveats and additional info below. Then I'll be taking questions from the audience.
Apologies in advance for anything I might have overlooked at this point.
–David
























































































