developer contextual help

Designed for developers

Your job is to develop software. You don’t have time to worry about content, except when you are ready to release and content is not ready. 

Contextualized and embedded help cannot exist without you

edc is about people working together in various roles. You are the key link between product UI and content: contextualized help & embedded onboarding.

How do you connect content?

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

With edc, you create bricks as you develop. We provide the IDE plugin for connecting bricks with content. You can even create a screenshot, just to make sure you and the contributor are talking about the same piece of UI.
collaboration

Contributors can work on content as you develop

The edit and review process happens in parallel with development. You continue to develop and get your product ready for release.

But wait! You know how the product works. You can follow content as it’s created, and provide feedback on functionality and check for content coherence...if you want.

Your role is important because you help decide with other contributors on the granularity of information available in your product.

What’s your role in 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.

Your role is key

With edc, onboarding changes all that; and you have a key role to play in user onboarding.  

Working with contributors, you imagine events or contexts that trigger information the users needs at any given moment.
design content
create a brick

You trigger user content

Writers design onboarding in the edc editor, but you provide the triggers that connect onboarding content to the UI.

Don’t worry, edc has its own onboarding that shows you just what to do, where and when.