---
# System prepended metadata

title: Documentation Revamp Plan

---

# Documentation Revamp Plan
## This doc serves as a skeleton for the upcoming documentation revamp at Esper, to be undertaken by Rin and Hussain

### Problem We're Solving

* Currently, Esper's console/UX documentation is spread across multiple segments on the site, making for a poor user experience
* Our aim is to unify this content into one main segment on Esper.io to decrease the amount of time that is needed by AE's and support to address questions customers could answer themselves with updated documentation
* Console documentation verbiage is confusing, needs to be updated to have a consistent tone/style/language
* Making Console On-Boarding self-serve for the average user

### Setting docs up in right places for content improvement

### Driving improvements in tone, language, style

### Re-Organize Console Docs

### Bringing content up-to-date

### Evaluating what we’re using for docs.esper.io

### Creating a process for maintaining accurate up-to-date docs
* Integrated into release

### Wrap console docs, and then move to dev docs in Github

### Sprint Cadence

* Work on docs improvements daily, with pull requests submitted often, as a part of a continuous improvement strategy

### Timeline

* Follows https://docs.google.com/presentation/d/1VBiQlLPj-zcf_SiqXO4QAiy4LyXEXy8O1LQd0FvrVjw/edit?ts=5f47d3ad#slide=id.g92fdd3266c_0_0

### Goals

* Update console docs for tone/language/style
* Update UX/console docs to improve customer experience
* Update UX/console docs to explain to customers how to get started with Esper
* Updated UX/console docs to allow customers to troubleshoot their issues on their own up to a certain threshold before needing to contact support
* Establish/update docs to support a clear device provisioning workflow

### What Success Looks Like

* Clear, accessible documentation that meets the goals outlined above
* Customers are provided a unified self-serve experience to get started with Esper

