Developing Content

You know what the hardest part about writing technical documentation is? Or really writing anything professionally? It’s polishing the content.

Yeah, actually writing words is easy. I’m doing it half asleep while I lay in bed right now. But is it good? No, not really. The reason?

Well that’s an easy one: I’m not taking the time to polish this crap up before I put it in the front window for the whole world to see. The documentation that I’ve been writing for work though, that needs to not only read well, but look good too. It needs to have lots of pictures and sound right. It needs to be professional, yet carry a hint of personality.

So yeah, it’s hard. It is making me want to write more though. I think I want to make writing in my blog here a daily thing. Even if I do nothing more than make the title the days date, I want to at least make a post. really as more of a record of my life, like a journal.

So, look forward to what I hope to be an every day thing!

Technical Writing Galore

The past few days I’ve been working on all the technical documentation for Ivinex. It’s a pretty big project, but one that I’m actually very excited to tackle. Of course, I set up the documentation site using WordPress. It’s amazing how capable this little piece of software has become over the years.

I’m taking a two-fold approach to attacking this project. First I’m going to flesh out the technical manuals (the ones that say, this is for that, this does this, blah blah blah). Then I’m going to take on the tutorial side of it. That’s the part that will give how-to’s on specific tasks.

I’m pretty happy with how it’s turning out so far, but there’s still a long way to go. I have the next week and a half to two weeks to get it a good portion of the way done. I’ll keep this blog updated with my progress as time goes on.