You could use GitHub Pages or at least their principle of storing the documentation in gh-pages branch.
This way users could just clone just the source of the plugin, easier integration with package managers like Twitter/Bower etc.
Also it would be possible stable releases to be available in the documentation, but development to be performed on master.
You could use GitHub Pages or at least their principle of storing the documentation in
gh-pagesbranch.This way users could just clone just the source of the plugin, easier integration with package managers like Twitter/Bower etc.
Also it would be possible stable releases to be available in the documentation, but development to be performed on master.