A TechCommGeekMom Milestone: A baby blog is now a toddler

Posted on April 19, 2013 by TechCommGeekMom

WOW!

I think my little blog just grew up a bit. I not only reached the 10,000 all-time hits mark, but even passed it. For a niche blog that’s 13.5 months old, I think that’s pretty amazing! I’m a proud TechCommGeekMom!

Thank you to every person who’s a regular reader, who just popped in once in a while, or who came only once for a visit. 10,000 all-time hits is a lot! Now, I know of blogs that have definitely had more traffic than me, mostly because they are much more hyper-focused on a particular segment of technical communications, like everything you want to know about a particular type of software, everything you want to know about a particular strategy, or else they’ve been around for a long time, so they’ve built up a following after a while. I do not begrudge these people, as they are my inspiration, and in some ways, they have contributed to this blog too through curated content now and then. TechCommGeekMom wants to be like those blogs as it grows up!

I trust that you enjoy what you read, and that you keep coming back for more. I’d like to think that the variety presented here, mixed with my own eccentric flair, brings about a lot of different perspectives of what technical communications is and what it can be. As I’ve said in the past, this blog started out very small, as a grad school project to build a community via social media, and I chose to work on building my tech comm/e-learning/m-learning community. I’m guessing that perhaps–just perhaps–I may have achieved my goal of creating a TechCommGeekMom community, and yet I hope the family will continue to grow. If you have any suggestions or ideas of things you’d like to see here, or if you’d like to contribute a guest post, please let me know!

Many thanks from the bottom of my heart for helping me reach this milestone! This blog is a labor of love, and it has opened so many doors for me, which I hope continue to open! I truly appreciate the support!

Uncategorized

For Technical Writers, The Future Looks Bright | MindTouch

Posted on April 4, 2013April 4, 2013 by TechCommGeekMom

See on Scoop.it – M-learning, E-Learning, and Technical Communications

Danielle M. Villegas‘s insight:

This comes to me via @Nancy_Coppola through LinkedIn. This is good news for all technical communicators and writers! I remember Nancy telling her students three years that things would be picking up in this field–and she was right! There are more job opportunities in tech comm now than when I started my journey into tech comm three years ago. The flexibility and agility of tech comm workers makes us great candidates for many positions. Going forward, the trick will be keeping up with technological trends and making sure that those who are entering the field have a chance to not only be trained on certain software products and practices, but that they have the chance to continue with career development to keep tech comm relevant.

–techcommgeekmom

See on www.mindtouch.com

Uncategorized

“A Fear Stalks Our Profession…”

Posted on March 5, 2013 by TechCommGeekMom

The STC posted this on Facebook today (I was so busy today, that I don’t know if they posted it elsewhere), and I was struck by how focused it is in the message. Credit goes to Rick Lippincott who gave this presentation, and to the STC for posting it!

This Lightning Talk from the 2012 STC Summit in Chicago expresses exactly why I get so excited about technical communications. It’s an fantastic time to be a technical communicator! Enjoy!

Uncategorized

Instant Mobile Apps? Not quite.

Posted on February 11, 2013 by TechCommGeekMom

Last week, I was in contact with one of my former professors at NJIT‘s MSPTC program. We talked about several things going on, and in the process of the email conversation, she mentioned that she is starting another semester of the PTC 601 (Advanced Professional and Technical Communications) classes, and she asked me a question about mobile, because she wanted to add a new component to an assignment.

I remember doing the assignment well just three years ago. Essentially, the student is given a manual for a fictitious coffeehouse franchise’s espresso machine, and the student has to rewrite the manual into a quick reference guide, preferable something that included visual images that could the learner/user can learn from it or refer to it as needed. Conceptually, it’s an easy enough assignment (or at least it was to me), but creating it with the tools I had at the time proved challenging, even if I did pull it off.

Adding a mobile component to this assignment makes a lot of sense to me. This is a perfect example of what m-learning is, what it looks like, and what it can be! Taking a simple how-to manual and creating a mobile app for it is highly logical, especially in this scenario. I mean, think about it…how often do people whip their smartphones out of their pockets to look up any kind of information, let alone have a how-to app on their phones? So having a special app that could be downloaded and instantly used as a reference guide for that newbie coffee barista would be ideal!

I was happy to hear about this addition to the assignment. The professor knows how enthusiastic I am about promoting mobile solutions, and I was thrilled to hear that she is making an effort to include mobile solutions in the MSPTC curriculum. So, she asked me if I knew any software programs that could convert text into some sort of mobile output. The first thing that came to mind was Adobe’s Technical Communications Suite 4, especially with Framemaker and Robohelp. But, the school doesn’t have a copy of that for students yet (they are working on it), and even with the short trial, there’s a big learning curve for an assignment that would be due fairly quickly.

So, I began to do a little research to help the professor out. There were a few things–a few parameters–that I had to keep in mind as I looked for a tool for her to use. It has to be easy to use for someone who didn’t have too much or negligible programming skills. It has to be free or at the barest minimum of cost. And it had to have an easy ramp-up to have a project done on it in a week or so. I knew, from experience, that people from all walks of life come into this program, with a true mix of web expertise. I remember helping some of my fellow classmates by providing a crash course in HTML, and the quest for the free or cheap web editing software or site where an e-portfolio could be created. So, I understood the parameters well.

The sad thing I discovered was that while there are dozens of places to set up and create free or cheap websites with web editing available that anyone could use to set up a good looking site, the same can’t be said yet for creating mobile sites. There are a few sites that do help a person create a mobile app easily, but it’s not cheap. Or, if it’s cheap, it requires some programming know-how. It was tough. the other thing to keep in mind was whether the mobile app being created was for a “native” app, a “web” app or “hybrid” app. The differences between these is that a native app is saved on the mobile device and can be used offline. The web app is one that is essentially a mini website and needs an internet connection to access the app. A hybrid is…well, you can figure that out. If you’ve ever tried to access an app on your phone, but couldn’t get it to function because you didn’t have wifi or 4G, then that’s a web app. If it only partially worked, but you still needed wifi/4G to connect for part of it, it’s a hybrid. You get the idea. In the end, I gave the professor a few suggestions that I found.

The first was something called Viziapps. I think I had heard of Viziapps because I believe (just off the top of my head) that this was the software being used in an STC class on how to build mobile apps. Viziapps allows individuals to create a mobile app without knowing any or little coding, but they would have to have some idea of information architecture (which is part of the project assignment–understanding what’s important, what’s not, what comes first, content structure, etc.). It’s mostly a visual editor that allows the user to build the apps online, then publish on the web for free, provided the creator has created a web app. If it’s a native or hybrid app, then that has a price. It seems like it might be a viable choice as a tool that would allow for a quicker ramp-up for someone seriously trying to create a mobile app.

Other more creative choices would be using their mobile devices to make something. For example, there is an app called SnapGuide, in which an individual can take photos or video to demonstrate how to do something. Mobile by Conduit might be another possibility, as it’s free, and supposedly has an interface style similar to WordPress.

But then I thought about WordPress, and I realized that might be another option. TechCommGeekMom is a WordPress website, after all, and it can be read on mobile devices. Basic WordPress accounts are free and fairly easy to use. You can create a “blog” or website on WordPress, and then there’s a setting to create a mobile interface. Here’s a little bit of info about it: http://en.support.wordpress.com/themes/mobile-themes/ It seemed to fit the criteria needed for a mobile app creator/editor, in that it’s free, it has a mobile output (as well as a regular web output), and it provides a primer for content management in the experience. I thought that if I was still in the class, I’d create several pages on a single WordPress website for different parts of the Guide–similar to the pages and navigation I have here, and then promote the mobile access to the website. It’s not a perfect system, but for quick ramp-up purposes for a fairly small assignment, it seems like it would fit the bill.

I think my former professor appreciated the help, but we both discussed the dilemma that it posed. Why must someone have a programming degree and some cash in order to create a mobile app–whether it be a native, hybrid or web app? Depending on the app, all three formats have their positive and negative aspects to them. But how does one learn how to use any of these mobile app writer/editor products quickly? There are some great tools out there, I’m not denying that, but for the true beginner or student on a budget who is trying to learn how to create mobile solutions skills as a technical communicator, it’s not that easy. I see a huge business opportunity here (not that I have the time, cash, or enough knowledge to start such a business), but creating a highly user-friendly software program that one’s grandma could create a mobile app for a very low cost would be a fantastic business. It would make even more information accessible to share with others.

It occurred to me later that for the average user, another possibility is another Adobe program that I’ve been using to create and maintain my e-portfolio, called Adobe Muse. It’s a cloud-based app that acts as a very easy UI interface to create websites and mobile apps. I’ve used the website editor, but I haven’t tried the mobile conversion yet there. I believe it’s about $14-15 per month, and you can set up an account at Adobe’s Business Catalyst and create your mobile site that way. It allows those who have next to no programming skills create something that looks great, but it also allows more advanced users some nice shortcuts to create great sites without having to do all the coding–Muse does it for you.

Perhaps, as mobile solutions become more mature like editing software for desktop interface websites, this mobile app creator problem will go away, and there will be more affordable options. In the meantime, we have to wait or muddle through it all…

If you know of any easy-to-ramp-up mobile app editors, please mention it in the comments below! Share, everybody!

Uncategorized

Is English an International Language? – Part 1

Posted on February 5, 2013 by TechCommGeekMom

I mentioned a while ago that I had several writing projects that were coming up, and the first of them is now published! I was asked by the STC-PMC to write a two-part article about the differences and similarities between American and British English. Of course, I think there’s much more to that simple debate, and this is a favorite topic of mine, so I gladly accepted the challenge. The bigger challenge was to try not to write an entire book!

To find the original article, see the January/February 2013 edition of the STC-PMC Newsletter here.

The article itself is below:

Is English an International Language?
Part 1

Is English an international language? Yes…and no. There is no question that English is a predominant global language. Half the world’s technical and scientific periodicals are written in English, as is eighty percent of the information stored in the world’s computers. There is no question that English is the most prominent language on the Internet, which has contributed to its continued spread around the world.

However, among English speakers, there can be huge differences, as if English speakers from different countries actually spoke different languages. The argument is often made that those who speak English do speak the same base language with just a few different spellings or colloquial idioms now and then. This is only partially true. While most of the world thinks of English in terms of American or British English, there’s also Canadian, Indian, Australian, New Zealander and South African versions of English to consider among others. Each version of English has further nuances that distinguish itself from another version. For the most part, an Australian can understand a South African, an American can understand a New Zealander, and someone from India can understand someone from the UK. But there will be moments that any one of those speakers could elicit a bewildered “EH?” amongst themselves in understanding.

Since most countries that speak English as the dominant language or a second language are former British colonies or Commonwealth countries, British English is usually the standard taught in schools. The exception to this, of course, is American English, which is usually taught in the United States and much of Central and South America as a second language. Even so, between American and British English, one would think that with a few small exceptions, they are essentially the same language, right?

What many Americans don’t realize is that British English has enough nuances that in several cases, we can’t understand our British brethren, and vice versa. For example, if a person came up to you in London and mentioned that he had a mate who sold so many crisps from his lorry that the crisps were falling out the boot and bonnet, would you know what that person meant? If you’ve watched a lot of BBC America or read enough books from the UK (as I have), then you might. An American would have to translate what the Londoner said, which was that he had a buddy who sold potato chips out of his truck, and the chips were falling out of the trunk and hood. Another example would be that if an American said that he would lose his pants over a financial deal, a Brit would misunderstand it to mean that the American would be losing his underwear over the deal, as “pants” is used to refer to underwear instead of “trousers” in the UK. Those are just two of many examples of how Brits and Americans don’t necessarily understand each other.

This divide is an important consideration in technical communications. Single-sourcing and translation are a large and continually growing component of technical communications. While software is becoming more intuitive about translating written content into different languages, it’s not flawless. Using a standard commonality in the language would be desired as a result.

See the March/April issue for Part 2.