TechComm handy resources: Free images

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

Advertisements

Ideas for quality content (summary + video)

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.

Continue reading

TechComm handy resources: Free fonts

From a TechComm newbie to a well-experienced pro, we all have hundreds of useful resources saved to our browser bookmarks, read-it-later apps, and bookmark managers. The series of posts TechComm handy resources is a humble try to organize my resources into a single easily accessible depository.

Continue reading

Leading by example in legacy projects

One of the typical ways for agreeing to have project documentation in place is this:

  1. Customer voices the need for documentation (on a side note, product-based software companies are not considered in this discussion).
  2. Documentation team provides the estimates.
  3. Estimates are adjusted and approved.

This works well for new projects and new features in existing projects. On a side note, this also assumes that the people who give the final approval for documentation do understand why documentation is needed.

But what about legacy projects, the ones that are poorly documented or not documented at all? How do you convince the company (or the customer) that documentation is needed?

Continue reading

Operation Cleanup: CSS refactoring for InfoDevs

Hey, fellow writers who work in MadCap Flare! Have you ever opened your CSS style sheet in a text editor and checked if it contains conflicting entries, style duplicates, or empty style definitions? Maybe there are unnecessary repetitions of a property assigned to child elements, but this property is already assigned to a parent element? (I had this problem with fonts and colors).

Being unsure of what is going on with your CSS, you might be surprised to find that, for example, after you changed one property, half of your document inexplicably changed its color or indentation level. And there you are wasting time trying to apply a quick fix that most probably breaks something else. It is only then that you finally realize that the CSS refactoring time has come. Continue reading