So, you say you have developed a new cutting-edge app, and now you want it to rock the tech world? Don’t want to dash your hopes, but it takes more than that to succeed. Let’s take a closer look at one of the TechCom trends–user adoption. Once you finish this article, you will understand what user adoption is, why it is so important, and how it can boost your production.
As an Information Developer, I often ask myself what our biggest fear is. In my opinion, that’s the fear to create useless technical content that no one reads, miscommunicate information, or fail to assist your readers when they need help the most. This fear may come true when we don’t analyze deep enough who our readers are, their needs, and how they access our content.
In this article, I would like to have a closer look at how writers create accessible content and a multisensory experience for readers with disabilities.
We all strive to bring our projects to life with high-resolution images that inspire, excite, and propel audience to action. But where do you find high contrast images rich in beautiful detail that can make your project memorable and inspiring?
Here is a list of searchable photo repositories for commercial use with no attribution. Continue reading
Here in Lviv, we were lucky to invite Patrick Keegan, Principal User Assistance Developer at Oracle, and enjoy his talk “Free your mind! And your docs will follow”. It took me some time to digest the whirling ideas and grasp the insights.
In this post, I would like to share two approaches Patrick discussed during his presentation and how I plan to adopt them in my routine as an Information Developer.
Here we go.
The phases of project initiation and project closure are substantially covered in blog posts, talks, and other resources across the TechComm society. Today, I would like to address a less frequently discussed phase – replacing a technical communicator in a project team.
Have you ever been assigned a task to write API documentation, and then you got lost in tools for creating it?
If yes, I would like to share with you amazing research by Diána Lakatos who analyzed loads of info to provide us with a magnificent overview of open-source tools for documenting APIs.
Is storytelling the same as writing well? How to write a concise yet interesting API guide? Is there a way to keep a help system offhand and casual without using humor? All this and much more in my presentation!