Open jmatsushita opened 8 years ago
This should also grow to include criteria (and later test tools) to determine if an implementation is following the content as code principles.
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:
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.
Part of #7
My thoughts on this would be to focus on allowing user to start from a project scaffold:
We could create repos (
contentascode-blog
,contentascode-wiki
,contentascode-website
,contentascode-doc
) that are ready to clone with some sensible defaults.The default pipelines would have a travis.yml that push to a
gh-pages
branch.We could also look into Grunt-init or Yeoman Project Scaffolding tools to allow configuration of various options such as:
We also need to think about migration and various options to use integrations to facilitate a progressive transition process.
Reference Implementation Matrix