Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Creating Two Levels of Open Engagement with Github Pages and Disqus

DZone's Guide to

Creating Two Levels of Open Engagement with Github Pages and Disqus

· DevOps Zone ·
Free Resource

Do you need to strengthen the security of the mobile apps you build? Discover more than 50 secure mobile development coding practices to make your apps more secure.

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.

My projects all start as a public GitHub repository, equipped a subdomain pointed at a GitHub Pages and a Jekyll site template--allowing me to add pages and give the project its own blog.

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:

  1. Casual - Quick comments and feedback via Disqus as users come across a project
  2. 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.

Check out tips for blazing the way from agile to DevSecOps with security built into your mobile app toolchain.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}