Skip navigation

Category Archives: Technical Writing

Rory O'Connor's Caution: Blogging May Be Hazardous to Your Job reports that corporations now see blogging, message boards and instant messaging software, such as AIM, as taboo for employees.

O'Connor discusses the disciplinary measures employees face for inappropriate emails and how those measures now encompass other multi-media, such as blogging.

In an eerie echo of an earlier post here, O'Connor points out that it is often difficult to judge what is appropriate content and what is not. O'Connor goes a bit further explaining few companies provide employee training for multi-media interactions, yet many businesses will still fire online misconduct.

In the past, I have focused on email etiquette and web design rules of behavior, but I will obviously be including blogging in writing for the web. In the future, I also plan to discuss appropriate blogging and instant messaging in technical writing and professional writing as well. After the article, I have no urge to teach my students not to blog, just to weigh their words with a deep appreciation for the consequences of writing.

Advertisements

To begin, insert your image with the insert edit image button. Or, if you've uploaded it into WordPress, simply browse all until you find the image you want. Then click and drag the image into the post.

Now that the image is in the post, you will need to click on the html button to access the code. Once there, you will want to find the image in the coding. It will look like this:

<img src="YourImageName"

To align the image to the right, you would need to add: align= "right".

Fuseli

<img src="YourImageName" align= "right"

To align the image to the left, you would add align= "left".

img src="YourImageName" align= "left"

You may also choose top, middle and bottom.

If you are working in WordPress, when you use the image button it will ask for the alignment and automatically set it for you. If you are working with web pages, you might want to keep the code handy.

Lifehacker provides an excellent link to a site readability test provided by Juicy Studio. While I'm not sure if I'll use this in Writing for the Web (probably, though), I will definitely use this in Technical Writing if my students continue to create online documentation.

In fact, I think the all of the information provided by Juicy Studio might be very helpful to students.

In Stephen D. Krause's When Blogging Goes Bad, he speaks of his profound disappointment because his students' blogs didn't become dynamic sites. He suggests and as I learned at Purdue in teaching practica, blogging must essentially be used as a tool because they don't become dynamic sites replacing email or listserves. He advises us to forget the utopian idea of a thriving community. Ken Smith's experiences would seem to suggest otherwise, except for one or two students, and in a class of 20, I think the percentages are a strong indicator that blogs have the potential to "go good."

Simply using the blog as a tool may backfire and explode in what Michael J. Salvo terms "technorhetorical" in his article, "Teaching Information Architecture."  Salvo defines "technorhetorical" as not only communicating information to an end user, but also taking part in the process of how the information will be constructed. This is exactly what happened in my Technical Writing class last semester.

Read More »