December 31, 2014

Performance of Information Developers group-2014

2014- Year It Was

ApraDocs Information Developers is .in by registration but .org by heart.

We impart technical writing training in India and online by charging minimal fee and deliver more than we commit.Apart from our regular students, we also offer lot of free learning through different platform like blog,LinkdIN page,LinkedIN goup,Facebook page and sponsoring technical writers conferences in Delhi area.

Our growth is growth of all the technical writers directly or indirectly involved with us.

We partnered with Multivertex for technology support.
Started our new venture Digital marketing training through Digital Marketing Research and Training
Browse Motion continue to maintain our website.
Collaborated with Wincere.


Some numbers:

LinkedIN Group- Information Developers


Click  to view


835 members on 31 December 2014 Majority from Bangalore followed by Pune and New Delhi, 36% are seniors.

Thanks for being the part of our community.Hope we will be able to add more deligates this year.


Blogger performance


This blog continuously featured in All top tech writing. Kudos to blogging team!!!

From this year U.S guys surpassed Indian followers.Now we are more popular in U.S than in India.We are opened more on Firefox than IE or chrome.

By now 84000 page-view we received and most of the readers are coming from google search.In India we are most read in Bangalore followed by NCR.


Information Developers technical writing prformance

December 26, 2014

Test the Map IDs of a RoboHelp Context Sensitive HTML Help File

Map IDs in RoboHelp11

If you have Map IDs and not able to test it. RoboHelp provide a wonderful tool to test it. 
What is Map IDs All context sensitive help files have each individual help topic assigned a Map ID number.
The application developers integrate that ID into the application so that when a user presses the F1 button in a topic screen, the application reads the Map ID of the topic and displays the correct topic that corresponds to that Map ID number.
Question: Before giving it to the developers how would you know if your Map IDs are working in a help file; if they are properly attached to individual topics and are pointing at the correct topics?
SOLUTION: RoboHelp has a feature (tool)l for that called CSH (Context Sensitive Help) Test tool.
To test Map IDs
1) Open the Toolbox by selecting View > Pods > Toolbox.

CSH Test RoboHelp
 2) Double-click CSH Test icon to display the Context-Sensitive Help Test Tool dialog box.
CSH Test RoboHelp COntext Sensitive Help Test Tool
3) Browse and select the .CHM file you have generated earlier (for Offline files). If your help file is posted online, then enter its URL in the Online box.
4) (Optional) Enter a Window name.

5) Click the map file icon and select a map file.

6) Click the triangle and select a map number.

7) Click Show Help.

If your map IDs are correctly attached to the individual topics, a window will open and display the correct topic for that Map ID number.

If you are interested in learning complete Robohelp,Framemaker,Madcap Flair,MS VISIO,Captivate,SnagIT,Business writing,Technical writing at Noida,NCR,Gurgaon,Gaziabad visit www.informationdevelopers.in. For latest update you can also like our LinkedIn page.


December 18, 2014

Difference and Use of different fonts for technical writers

So, as a Technnical writer, it just makes sense to make sure the font you or your clients use is one that doesn't hinder sales in any way.

The difference between 'serif' and 'sans serif' fonts

Serif fonts have little feet and embellishments on the tip and base of each letter, making them more distinct and recognizable. Popular serif fonts are Times New Roman, Palatino, Georgia, Courier, Bookman and Garamond.
Nearly all books, newspapers, and magazines use a serif font. It's popularly accepted that – in print – serif fonts are easier to read. The idea being that the serifs actually make the letters flow together – and subsequently easier on the eyes.
As the name states, 'sans serif' fonts are fonts without serifs. While some sources say sans-serif fonts have existed since the 5th century BC, it wasn't until the 1920s that they became somewhat popular – mostly being used in advertisements.
One of the reasons for their lack of popularity was that typographers stuck with serif fonts because they felt they were easier to read.
It's been said that serif fonts are for "readability," while sans-serif fonts are for "legibility." Which is why, in print, sans-serif fonts are often used as the headline font and serif fonts are used for the body text.
Some popular San Serif fonts are Helvetica, Arial, Calibri, Century Gothic and Verdana.

Best fonts for print

In his book Cashvertising, Drew Eric Whitman cites a 1986 study of fonts (printed on paper) that found only 12 percent of participants effectively comprehended a paragraph set in sans-serif type versus 67 percent who were given a version set in serif typeface.
Those who read the sans-serif version said they had a tough time reading the text and "continually had to backtrack to regain comprehension."
In a test of three different fonts, two serifs (Garamond and Times New Roman) and one sans serif (Helvetica), he found 66 percent were able to comprehend Garamond; 31.5 percent Times New Roman, and 12.5 percent Helvetica (out of a total of 1,010,000 people surveyed).
The conclusion being that serif fonts are easier to read when it comes to fonts on paper. So, if you're sending out a sales letter or brochure in the mail, you probably want to use serif font (but, as mentioned in the first point, you could use sans-serif font for your headlines).
Here are the print font preferences of three of the copywriting greats: 1) advertising great John Caples liked using Cheltenham Bold for headlines; 2) advertising legend David Ogilvy preferred the Century family, Caslon, Baskerville, and Jenson; and 3) direct marketing guru Gary Halbert used Courier in his sales letters.

Best fonts for online

Now, one might assume that what works on the printed page will be similar to what works on the computer screen. But that's not the case.
In order to make the little serifs appear legible, a high degree of resolution is required. The more pixels, the more details of the font you can display.
Back 10 or so years ago, the best computer screen resolution was 800 x 600 pixels – which wasn’t great for defining the intricacies of a serif font. Screen resolution has increased through the years (resolutions of 1024 x 768 pixels or greater have become the norm). This makes serif fonts more legible but still generally not as easy to read as sans-serif fonts.
Plus, now you have to consider how your site or email will look on handheld devices, such as the BlackBerry and iPhone. The latest model of iPhone 4 has a screen resolution of 960 x 640 pixels. The BlackBerry Bold 978 has a screen resolution of 480 x 360 pixels.
So online, the best font to go with is sans serif.
A 2002 study by the Software Usability and Research Laboratory concluded that:
The most legible fonts were Arial, Courier, and Verdana.
At 10-point size, participants preferred Verdana. Times New Roman was the least preferred.
At 12-point size, Arial was preferred and Times New Roman was the least preferred.
The preferred font overall was Verdana, and Times New Roman was the least preferred.
So here are your marching orders:
For easiest online reading, use Arial 12-point size and larger. If you're going smaller than 12 points, Verdana at 10 points is your best choice. If you're after a formal look, use the font "Georgia." And for older readers, use at least a 14-point font.

Best fonts for email

Dr. Ralph F. Wilson, an e-commerce consultant, did a series of tests in 2001. He also came to the conclusion that the sans-serif fonts are more suited to the computer screen.
Some of the highlights of the test results were that at 12 points, respondents showed a preference for Arial over Verdana – 53% to 43% (with 4% not being able to distinguish between the two).
Two-thirds of respondents found that Verdana at 12 points was too large for body text, but Verdana at 10 points was voted more readable than Arial at 10 points by a 2 to 1 margin.
In conclusion, for the best font readability, use Arial 12 point or Verdana at 10 points and 9 points for body text. For headlines, he suggests using larger bold Verdana.

Deciding on a font

So the next time you submit a sales letter or email to your client, it might be a good idea to ask them what font they intend to use.
If they plan to use a serif font online or in an email, you might want to gently nudge them away from it and recommend a more easily readable sans-serif font.
If they also plan to send your copy to their list via regular mail, it's not a bad idea to suggest they switch over to a serif font at least for the body text.
It could mean the difference between a winning piece of copy and one that only delivers so-so results.

Credit to the original researcher and publisher of this article.

December 17, 2014

2014 Salary Survey of Indian Technical writer

Technical writer salary in 2014



STC India chapter recently released their salary survey results for 2014 in 16th STC annual conference at Bangalore which provides an insight about the technical writers salaries in India and also about the technical writing industry growth in Indai. This valuable and benchmark is result of  Paresh Naik. Kudos to Paresh’s indeed a great job in publishing this salary survey!

So what do you think about your salary!!! Have a look before you change in 2015 so that you can make maximum from the new market recovered from recession.

For me good news is my area (NCR) is highest paying area in India followed by Pune for the same experience level.On the other hand this year salary decrease by 11.9% compared to the
same in 2013.Really sad.


For international friend  1USD = 63 INR

Some Interesting Findings from the data

Measures used in this report 

Survey according to experience



Click to Zoom










Base:   The total responses in a given category.
Mean: The value computed by averaging the tabulated responses.

10%: Ten percent of the responses were below this value; ninety
percent were above this value.

25%: Twenty-five percent of the responses were below this value;
seventy-five percent were above this value.

50%: Fifty percent of the responses were below this value; fifty
percent were above this value. This is also called the median.

75%: Seventy-five percent of the responses were below this value;
twenty-five percent were above this value.

90%: Ninety percent of the responses were below this value; ten
percent were above this value.

TrimMean: This value is the mean taken by excluding 10% of data
points from the top and bottom tails of a data set. In other words, this
is an average of values excluding the extreme cases.

Salary/year of experience: Most of the tables also indicate the
measures for salary/year of experience. This parameter is included to
compare influence of various factors on the salary on level grounds,
i.e. to exclude the effect of experience. If all or most of the survey
participants from a specific category have a higher number of years of
experience, the average salary in that particular category may be
reflected as very high. In such cases, the salary/year of experience
parameter will give a more realistic comparison of salaries in related
categories.

All the salary figures mentioned in this report are in Indian Rupees
unless specifically mentioned otherwise





December 12, 2014

Best learning resources for RoboHelp

Learn Robohelp by yourself

Robohelp is a very user-friendly tool to author and publish in multiple channels.It is really evolving with every new release. The time this blog was written Rh11 was the latest in the market.

I find some useful resource while learning Rh.  Sharing it with you.Hope it will make your learning easy.






If you want to learn Robohelp from me please contact us and those who are  from New Delhi,Noda,Ghaziabad,Gurgon or Faridabad,India can drop in ApraDocs information Developers office.

November 22, 2014

Gerund rule for technical writers

Hi Folk,

One of the irrepressible skill of technical writers are good English.We can achieve this by practice.In this series we are trying to share some good rules of writing.

This is a brief about "Gerund Rules". Hope you all like the post!!

Gerund looks exactly the same as a present participle, and for this reason it is now common to call both forms 'the -ing form'. However it is useful to understand the difference between the two. The gerund always has the same function as a noun (although it looks like a verb), so it can be used:

Rule1 : As the subject of the sentence:
  • Eating people is wrong.
  • Hunting tigers is dangerous.
  • Flying makes me nervous.
Rule 2: As the complement of the verb 'to be':
  • One of his duties is attending meetings.
  • The hardest thing about learning English is understanding the gerund.
  • One of life's pleasures is having breakfast in bed.
Rule 3: After prepositions. The gerund must be used when a verb comes after a preposition:
  • Can you sneeze without opening your mouth?
  • She is good at painting.
  • They're keen on windsurfing.
  • She avoided him by walking on the opposite side of the road.
  • We arrived in Madrid after driving all night.
  • My father decided against postponing his trip to Hungary.
Note :  This is also true of certain expressions ending in a preposition, e.g. in spite of, there's no point in..:
  • There's no point in waiting.
  • In spite of missing the train, we arrived on time.
Rule4: After a number of 'phrasal verbs' which are composed of a verb + preposition/adverb
Example: to look forward to, to give up, to be for/against, to take to, to put off, to keep on:
  • I look forward to hearing from you soon. (at the end of a letter)
  • When are you going to give up smoking?
  • She always puts off going to the dentist.
  • He kept on asking for money.
NOTE: There are some phrasal verbs and other expressions that include the word 'to' as a preposition, not as part of a to-infinitive: - to look forward to, to take to, to be accustomed to, to be used to. It is important to recognise that 'to' is a preposition in these cases, as it must be followed by a gerund:
  • We are looking forward to seeing you.
  • I am used to waiting for buses.
  • She didn't really take to studying English.
Note : It is possible to check whether 'to  is a preposition or part of a to-infinitive: if you can put a noun or the pronoun 'it' after it, then it is a preposition and must be followed by a gerund:
  • I am accustomed to it (the cold).
  • I am accustomed to being cold.
Rule5 :  In compound nouns
Example:
driving lesson, a swimming pool, bird-watching, train-spotting
It is clear that the meaning is that of a noun, not of a continuous verb.

Example:
the pool is not swimming, it is a pool for swimming in.

Rule6 :  After the expressions:
can't help, can't stand, it's no use/good, and the adjective worth:
  • She couldn't help falling in love with him.
  • I can't stand being stuck in traffic jams.
  • It's no use/good trying to escape.
  • It might be worth phoning the station to check the time of the train. 

September 23, 2014

e-Library for Technical Writing Course

Apradocs comes up with a free E-library for Technical Writers

A Comprehensive Collection of Technical Documents and Marketing Collaterals

This beautiful press release is written by +Anuradha Malhotra,student of ADID.

ADID, a well-known technical writing training institute in New Delhi,Noida (NCR), has released its free e-library of high-level documentation. The repository contains documents that can be useful for technical writers. It also has important articles that explain standard methodologies like DDLC and Agile. All the documents are downloadable and no fee is charged for that. 


Delhi, INDIA September 23, 2014 – ADID, ApraDocs Information Developers, a reputed training institute in Dwarka, New Delhi recently released a repository of technical writing documents for student sharing. Comprising of a comprehensive archive of user manuals, help guides, newsletters, whitepapers, and troubleshooting documents, the repository has everything that is important fora technical writer to know- right from high-level documentation to sample guides to modernistic approaches like DITA and Agile, it has all.

The e-library has documents related to content writing also, an important and quintessential part of technical authoring. Articles penned down by experts on concepts like Audience Analysis, Scrum, and DDLC (Document Development Life Cycle) can be of good help to all levels of technical writers: beginners and professionals. Mr. Rahul Karn, Head of ADID when interviewed, said, “I always wanted to provide my students a virtual place where they could find all that is related to technical documentation. So, I kept on adding whatever I found could be useful to this e-library. I have kept it free for all. All documents are downloadable and can be accessed without any hassles. “

He further added, “As Technical Communication field is growing each day, keeping oneself updated is extremely important. So, I continue adding articles on latest technologies and methodologies adopted by organizations.” The students and technical experts can subscribe to this e-library and know of any updating/additions made in the repository via e-mail.
About ADID: ApraDocs Information Developers is Delhi’s and Noida leading Technical Writing training institute. It provides introductory, intermediate and advanced level training to its students. The course curriculum is tailored according to students’ needs and competencies. We offer courses in standard industry tools like RoboHelp, Captivate, Framemaker, Camtasia, MS Visio, SnagIt, Jing, and others.  

For more Information on how to use e-library, go through this video: 

For more information, 
contact: ApraDocs Information Developers
Mobile: 7840841999. 
Website: www.informationdevelopers.in

For free Download,click on the below link
Apradocs comes up with a free E-library for Technical Writers

If you are interested in learning Robohelp, Framemaker, Madcap Flair,MS VISIO,Captivate,SnagIT,Business writing,Technical writing training at Noida,NCR,Gurgaon,Gaziabad visit www.informationdevelopers.in. For latest update you can also like our LinkedIn page.


September 1, 2014

Basics of Waterfall method of Software Development

  • Waterfall is a traditional project management method.This was famous before agile.
  • It's a sequentially phased process.Means one after another.For clarity see image.
  • In this Teams will move from one stage to another only after the previous stage's completion; there's a phase-gate/phase-exit to clear before entering into the next phase.
  • The life cycle of Waterfall includes the analysis, design, development, testing, and release phases.
  • All requirements will be determined at the beginning of the project.
  • Design, development, and testing will be carried out based on the initially agreed-upon requirements.
  • Projects timeline may range anywhere from 1 to 1½  years.
  • There is less flexibility in changing the requirements or stalling the activities, as the team is working on the requirements that were documented months ago.
  • In the case of new requirements, a change request (CR) process needs to be initiated; any new requirement that was not identified at the beginning of the project is treated as scope creep.

If you are interested in learning Robohelp, Framemaker, Madcap Flair,MS VISIO,Captivate,SnagIT,Business writing,Technical writing training at Noida,NCR,Gurgaon,Gaziabad visit www.informationdevelopers.in. For latest update you can also like our LinkedIn page.

August 8, 2014

TOC- A tool to Plan Documentation Project

One of my friend ask me the importance of preparing TOC before writing.My answer was it is like restaurant without menu.Jokes apart, below is the reason.

The table of contents — is technical writer's best tool for organizing the document,planning  and project scoping. Your proposed table of contents not only shows your stakeholder or project manager that you have understand  the material well enough to know how to organize it into effective sections, but it also gives them  a chance to test whether or not you've included every important aspect of the project/product.

Table of contents is considered to be a fluid document. That's because new information that arises during the research and writing phases may result in sections being added to cover the new material. Your stakeholder may decide on a different focus for the project after viewing your initial drafts. You may later realize that additional subheads are needed to explain something within the context of the document itself rather than relegating that information to an appendix.Truely agile!!!

A proposed table of contents should contain your outline of the numbered chapters, parts, or sections and the heads and subheads within those parts. Depending on the style guide provided for submitting your table of contents, by help of TOC you can also estimate approx total page or word counts.

In short, your planned table of contents is the concrete face for your vision on how the document should be organized and what it will say. This also save you from any further dispute.

P.S-You can always take reference of previous or existing document,definitely this will ease your life.

August 1, 2014

Planning stage of document development lifecycle



This checklist can be used for planning stage  of document development lifecycle.You can customize it according to your need.
Not all the subjects will be included in plans at every stage. Some may be added in the later stages.
Collect all the relevant documents available, such as:
• Previous version of the Documentation Plan, Documents
• Product Specifications
• Requirements documents
• Documentation Proposal
• Quality Plan

Decide the standards and conventions to be followed (Style guide and Templates)
Plan the version and change control procedures 
Develop Backup plan
Plan provision of human resource
Plan provision of tools/software/hardware
Assign responsibilities for aspects of the documentation
Plan the prototypes
Plan the system tests
Plan the user tests
Plan the localisation
Plan the customisation
Plan the approval mechanism for the documentation
Decide how to handle updates and future developments
Plan the reproduction method for the printed documentation
Agree on the form of the deliverable to be handed over for release
Finally write the Documentation Plan:-)

July 31, 2014

Objectives and information before writing document proposal



Collect all the existing information of product, such as:

• Client need
• Marketing logic and requirment
• Product plans
• Task analysis
• Evaluation reports
• Customer feedback
• Previous versions of the product and product documentation

Find out the objectives for the following:

• The product
• Release Scheduling
• Usability
• Accessibility
• Future customization
• Internationalisation, localisation and customisation
• Translation
• Packaging
• Legal requirements
• Security
• International Standards and conventions
• Costs
• Documentation delivery and viewing mechanism

Then write the Documentation Proposal