Creating Two Levels of Open Engagement with Github Pages and Disqus
I’m moving all my side projects to run on GitHub as open source repositories. One of my goals in doing this, is to facilitate engagement around my projects, as opposed to developing them in isolation.
By default all pages and blog entries will have Disqus enabled for conversation around all aspects of the project.
This approach to project management will open up two levels of engagement from users:
- Casual - Quick comments and feedback via Disqus as users come across a project
- Deep - Fork a project and commit back blog posts, pages or other more structured data as JSON files
In 2013 my goal is to make sure all projects use this format by default. It really isn’t any more work than what I’m doing now--with a huge amount of benefits.
Hopefully more of my work will see the light of day, and it will encourage casual and deeper engagement from anyone with the interest.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)