No documentation set is ever fully complete, but having a thorough library of documentation is a great way to build trust in would-be buyers when they encounter your product and are trying to make a purchase decision. If we can get most of the plugin as well as the integration plugins documented, that will go a long way to both reduce support burden as well as be its own form of “marketing”. The biggest difficulty here is knowing where to start.
My plan right now is to record a screencast showing how to install the plugin, configure the board, add some cards, take advantage of the various features of the cards and just generally show the workflow from beginning to end. At this point, I’m relatively experienced with using the plugin itself, and I think going back through this screencast will allow me to generate an outline of the various sections that the new documentation will need to have.
Once we have this outline and an idea of the various articles we need, it will be much easier to fill in the content around that outline. Right now, this whole task feels very overwhelming, but I’m hoping that breaking it down like this will allow us to get going and gain some momentum. In addition, once we have this outline written up, it will allow me to bring on additional help with filling in some of the content, which is one of the ways Alpha Particle
is going to help support the plugin going forward.
In addition to customer-facing documentation, we’ll also be working on developer-facing documentation to give developers a better idea of how they can customize the plugin for clients or even for themselves. I think that the developer market is largely an unexplored customer base for Kanban for WordPress, but having rock solid developer docs will help us break in there a bit better (similar to how Stripe became the go-to solution for developers, in large part because of their extensive documentation).