Design DX for contentascode adoption

[iilab]

Design DX for contentascode adoption

[jmatsushita]

This should also grow to include criteria (and later test tools) to determine if an implementation is following the content as code principles.

[jmatsushita]

This repo is currently an implementation of the stack-github-pages approach. Not sure it can be made completely fork and play as it might always require to activate Pages on the github repo.

Moving to the stack-github-jekyll-travis approach will add the following features:

• Build/CI process! Server side integration tests link link checking #11
• Notifications of Build success and failure on Pull Requests
• Build badges

From a DX standpoint, moving to this stack should be as simple as changing branches and merging (and configuring travis). Will open a new issue to track this.