Migrate to scaffold-github-jekyll-travis

[jmatsushita]

Related to #15

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.

[jmatsushita]

Before doing this I needed to wrap my head around how the tooling's modularity would work which I've done a first pass at in the README.md here https://www.npmjs.com/package/docsmith (no code yet).

[jmatsushita]

Here's a possible path to migrate this repo trying to focus on a DX that would use the docsmith approach.

Start state: the current repo has a stack-github-pages approach which means its docsmith.yml file would be like:

source: .
build: 'github-pages'

If we started from scratch then

• Click based: forking the contentascode/site template should allow to get started immediately.
• CLI based: using a docsmith init site should create the site scaffolding in the current directory.

Migrating out of the previous stack there should be a way to upgrade to the new stack which should look like either:

• Click based: Not sure its possible unless editing the files from the github editor.
• CLI based: docsmith install build travis should do the migration which are what the manual steps do:
• Manually:
  • Changing the docsmith.yml file manually to:

source: .
build: 'travis'

• Adding a default .travis.yml file.

[jmatsushita]

Done and merged.