Technical writer, editor, information architect, Software industry
Mar, 2006 - Present
I write documentation from scratch. I also coach, guide, and handhold new writers. My interests include design thinking, information architecture, APIs, and DITA.
All for words; words for all.
Technical writer, editor, information architect, Software industry
Mar, 2006 - Present
I write documentation from scratch. I also coach, guide, and handhold new writers. My interests include design thinking, information architecture, APIs, and DITA.
Officer, Government sector
Apr, 1996 - Mar, 20069 years 10 months
Departmental work at various divisions of the note printing presses of the country's federal bank.
Editor, Publishing industry
Feb, 1995 - Mar, 19961 year 2 months
Digests of tax cases related to corporate laws.
Sep, 2020 - Present
Logistics (and impressions) from the pan-India solo-drive project.
Jan, 2016 - Present
Data from the epic. Is still a work-in-progress, and will morph into an API at an unknown time.
Markdown
reStructured Text
HTML
DITA
DocBook
Python
MkDocs
Jekyll
Sphinx
Arbortext Editor
Oxygen XML Editor
Madcap Flare
Method for extracting the click sequence from the UI source code and reusing for documentation , IBM
Published on: Jul 05, 2012
A disclosure for a method that pulls the UI text from product code and puts it automatically in the help content, while making it contextually correct. The disclosed method consists of traversing the source code in the UI mockup designer software to determine the click sequence. The determined click sequence is then referenced in the help document. Thus, all instances in the help document where these UI controls are mentioned are instances of auto-generated text, where the text in the help document is pulled (auto-generated) from the click sequence that is determined methodically by traversing the source code. The determined click sequences are identified by unique IDs.
Ancient history
Etymology