Resources

Blogs or White Papers or Corporate Profiles or Case Studies? Or Blapers?

All these documents have their own objectives and audiences. The document structure is different, the content varies and the publishing calendar is planned separately for all such documents. However, sometimes the content overlaps though it is conveyed differently.

For example, we can talk about vhite’s technical documentation process in a blog post, and in a White Paper as well. It also means that while writing a blog post, we are helpless if a reader wants the same information in a formal document. And, what if a user wants to add comments or thoughts on a White Paper?

vhite has blurred the line that separates these documents and we use *blapers*. A Blaper is a document that is a *paper* extension of a blog post. A blaper may or may not be the complete version of the corresponding blog post. Readers can post comments on the *blog* version or they can download the PDF form for their reference.

Title

 

Our Technical Writing Culture

Download here

Technical Writing Brochure

Download here

Technology Development Brochure

Download here