mobile content – TechCommGeekMom

sarahjane-crystalball — Sarah Jane Smith of Doctor Who is gazing into her crystal ball, trying to figure out why the 3rd Doctor and the Master aren’t going at it with more mobile tech.

Happy New Year! Welcome to 2014!

I had set several goals for 2013, and for the most part, I achieved many of them. Due to finally having a job this past year, I was able to pay for my new kitchen outright (okay, we saved on labor costs because my multi-talented husband installed everything–and I mean everything–except the Silestone countertops), so I have a new kitchen that I love. I definitely travelled more, as I visited Atlanta for the first time in 21 years due to the STC Summit, and I got to visit Portland, Oregon again for Lavacon. I didn’t get to go to the UK, however. And I still don’t look like a supermodel yet.

My 2014 goals are still fairly ambitious, I think. I would like to build upon my web publishing experiences at work, and figure out how to become a content engineer, rather than merely a content manager. I’m hoping that attending the Intelligent Content Conference in San Jose, CA this February and attending this year’s STC Summit in Phoenix, AZ will with help with that. I’m not sure if I’ll be able to make it to Lavacon again until later in the year. I still want to go to the UK, but I think I may have to wait a little longer for that. If there’s a way to combine a vacation and a conference there at the same time, perhaps I can pull it off later in the year instead of going to Lavacon (just to vary things up a bit). I had hoped to become a certified Muse expert last year, and that didn’t happen. Perhaps I can try this year. I also got the “WordPress for Dummies” book this year, which has inspired me to become more expert at using WordPress. I currently use the version hosted by WordPress itself, but I think it might be helpful to understand how the independently managed version works, too. If I can achieve some weight loss in the process during all of this, I will consider 2014 a success. 😉

As for predictions for 2014 in tech comm, I decided that I would be a little more analytical about it. Two years ago, it seemed that the push in tech comm was that we needed to think more carefully about content management reuse of content, and think in terms of mobile content. This past year, that was extended to translation and localization of content, taking it a step further. So with those concepts in mind, what’s the next step? In my mind, it’s implementation of all of these with more vigor. Some companies are on top of this, but it wouldn’t be surprising to me if many companies–even large, global companies–are not on top of any of this yet, or on top of it in an effective way. I think about companies that I’ve worked for in the past, and how, despite their size and availability of resources, these companies wouldn’t be cutting edge in distributing content for desktops or mobile, and regional sites were not as localized nor standardized as they should be. So, in my mind, this is the year of implementation.

Another thing to consider is technology changes. Over the past few years, we’ve been adapting not only to desktop or laptop interfaces, but we’ve also been adapting to more mobile devices like smartphones and tablets. Marta Rauch, a technical communicator friend of mine who is part of the Google Glass beta testing, pointed

out that 2014 is due to be a year in which even more portable, wearable mobile devices will become relevent. These devices would include something like Google Glass or similar products, but it also would include devices like Samsung’s wristband device or devices that are synchronized with car components. She’s got a point. Components are getting smaller, and technological portability is becoming more and more mainstream all the time. How do we decide what content is most user-friendly, reuseable, streamlined, and pertinent for these kinds of mobile devices? It’s something we need to start thinking about now.

riker-commbadge — “Riker to the Tech Comm community–are you there?”

So there you have it. At least in my mind, if we aren’t all wearing Comm Badges like in Star Trek by the end of the year, I don’t know what this world is coming to. 😉 But it’s hard for someone like me to figure out where the future is going. I’m grateful there are those who are on the cutting edge that can help me figure that sort of thing out, and can educate me on the latest and greatest so that I can bring it to my own workplace, as well as talk about it here on TechCommGeekMom.

I’m sure that there will be plenty of surprises coming up in 2014. As I said, I have three conferences that I’ll be attending in the first half of the year, and I know with the continuation of this great work contract I have, I will probably be learning a lot of new things through that opportunity, too. My philosophy is to never stop learning, and I plan to continue to learn a lot more going forward in the coming year.

What are you predictions for the coming year? Am I on target, or off-base? What did I forget to mention? Let me know in the comments.

Ladds_1 — Ladd’s Addition Rose Garden
Photo from http://www.rosegardenstore.org

Val Swisher was the next to last individual to speak at the Adobe Day at Lavacon 2013 event. For those who are regular readers of this blog, you know that my love for all things Val Swisher has no bounds. I’ve always been able to take her easy-to-digest information, and absorb it quickly into my brain, as well as relay her knowledge to others. When I looked at Portland Gardens to compare her to, I chose Ladd’s Addition Rose Garden. While it’s not as well-known (unlike Val, who is very well-known), this particular park, according to The Rose Garden Store, was one of four rose gardens especially built from the Ladd estate, in which the design included these gardens coming together to form the points of a compass. I often think of Val as my compass, as she has never steered me wrong with her information or with the wisdom and fun that she’s shared with me one-on-one.

Val’s Adobe Day presentation centered on talking about source English terminology in a multi-channelled, global world, and how terminology affects structured authoring, translation and global mobile content. She started the talk by reminding us that historically, we’ve always created content, whether it’s been on cave walls, through stenography, through typewriters or eventually on word processors. In every instance, consistent terminology has been essential for structured authoring and content. Managing terminology is also essential for translation and for reuse. She stated that prior attitudes used to be that the more complicated the writing was, the more “fancy” the product was. Today, that’s definitely not true. She used the example that I’ve heard her use before, but it’s so simple itself that it’s a classic. Her example involves writing for a pet website. If multiple words meaning dog are used, there can be problem with reuse, because you can’t reuse content if you use different words.

Val_example_dog — Here’s the example Val showed.

Val pointed out that it would be an even worse situation if technological or medical terminology was used instead.

Val continued by saying that when it comes to XML, reuse , and terminology, you cannot realize the gains of structured authoring if you’re not efficient with your words. Terminology is critically important to gain more opportunities.

ValSwisher — Val Swisher explaining how to approach content from a translation perspective.

Translation comes down to three elements– we’re trying to get better, cheaper, and faster translation output. We MUST use technology to push terminology and style/usage rules to content developers. In order to make it cheaper, we need fewer words, reused words, and reused sentences. It’s impossible for writers to know or even know to look up all term and usage rules. We MUST automate with technology. For example, “Hitting the button” is not translatable, but “Select OK” is fine! She said, “Say the same thing the same way every time you say it.”

For better translation, translation quality needs to improve and meanings need to match in order for better machine translation to be a possibility. Bad translation comes from the source itself. If the source information is problematic, then the translation will be problematic. The best way to save money and time is to say the same thing, every time, using the same words, and use shorter sentences. For machine translation, don’t go over 24 words in a sentence.

Faster translation is seen as content that takes less time to translate, needs fewer in-country reviews, and gets to market more quickly. The key to delivering global mobile content is responsive design, global mobile apps, text selection is key, and terminology is the most important element. Val showed this example of how translation in responsive design isn’t working, where the Bosch websites are not exactly in synchronization:

The mobile website on the left looks nothing like the English language version on the right.

The simpler the design is for the website–especially in mobile, the less you have to tweak it. This is especially true where consistent terminology is important, because consistency is needed for structured authoring. Creating truly faster, cheaper, and better translation enables a true global responsive design. This is not a simple task, as there is no such thing as simple, even when writing about complex concepts. Even if you think you’re not translating, your customers are, so the content needs to be very clear. The scary part of this is that some companies use Google Translate as their translation strategy, which is risky at best. To use something like Google Translate as the translation software, the content had better be tight, clear, and consistent.

One of the things I enjoy with Val Swisher’s presentations is that it all comes down to common sense, and she breaks it down into easy manageable parts for those of us–like me–who might not have thought about the context of language for structured authoring, and the consequences for not strategizing content to include translation considerations.

I highly recommend checking out Val’s blog for other great insights.

(As always, Val–if you’d like to add or correct anything here, please do in the comments below!)