Automating checks and updating of gh-pages

[pjackson28]

Would be good to add some automation to this repo to help reduce the workload. How should we go about automating some of the following:

• Running checkers on pull requests (could be submitted normally or through Prose)
• Automatically updating gh-pages on a merge (Setup push from master to gh-pages on Travis #98)
• Tracking pages that need update or new translations

@nschonni Any suggestions?

Would be good to reuse this for ogpl,github.io as well (although don't need to update gh-pages in that case).

[nschonni]

Related to https://github.com/wet-boew/wet-boew-documentation/issues/9

---

I'll answer to this one separately as this one might have a different implementation. Should this one be hot-linking to the public demo files in master or just have that configuration loosely coupled in master but configured in gh-pages?

[pjackson28]

It is different from wet-boew-documentation as it's primary purpose is to provide reusable code and gh-pages is providing a working example. The wet-boew-documentation is meant to be living, breathing documentation with possibly some side development.

What model do you recommend? I'm assuming there would be need for branching as we proceed through different versions like with WET core but unlike wet-boew-documentation where we wouldn't be maintaining separate versions.

[nschonni]

I would probably use a submodule to the dist for the files rather than hardcoding the absolute links. Maybe a configuration approach similar to what the php demos did, but I'll have to dig into Jekyll to tell what makes sense.