technical writer contextual help

Designed for technical writers and contributors

Your job is to write and review content.

You are often the first user of product features

You see and use the product early in the development cycle and interact with those designing and developing it.

edc is about people working together in various roles. Developers provide you the bricks for designing content for the UI: contextualized help & embedded onboarding
design content

Your role in content strategy

With edc, content is a matrix.

Imagine creating content as putting together a puzzle. As content strategist, you put a content puzzle together that caters to user experience and satisfaction.

User feedback is one of the key drivers you will use for content creation and curation in edc.

Write contextualized help

Most parts of your product UI can have associated content, eg. Windows panels, wizards, login pages, etc.

With edc, a developer provides you a brick associated with a part of the UI. You create the content for the UI. Developers can even create a screenshot, just to make sure you and the developer are talking about the same piece of UI.
write contextual help

Design embedded onboarding

The old way of doing this is that contributors write Getting Started docs and long training manuals. Support answers the same questions over and over again.
With edc, onboarding changes all that.


create a brick
1. Imagine Triggers & Create Bricks
Working with developers, you imagine events are contexts that trigger information the users needs at any given moment. Developers create bricks for triggers.
Onbaording replaces getting started manuals
2. Add Content
You write onboarding in the edc editor based on triggers. Bricks connect onboarding content to the UI.
publishing onboarding
3. Publish
Publish immediately or use your internal review process to add comments and edits. Don’t worry, edc has its own onboarding that shows you just what to do, where, and when.

You are a key participant in the development process

You write content alongside the development. The editing and review process happens in parallel with development. You continue to write as developers get the product ready for release.
collaboration
deliver onboarding content

Your content can be live. Anytime.

Of course, edc has a review and validation cycle option, if your strategy calls for it. But with edc, you can be truly agile, creating live content as features become available.

Or it can be delivered to the product at any point in the development cycle. In that case, you deliver to your developer collaborators.

Start small; build later. An agile process with planned cycles of improvement.