+ [2014-12-28T19:27:57Z] jaybe pontiki, you could; yes - i.e. ~/Sites/example.com/_site/
+ [2014-12-28T19:28:36Z] jaybe the 'challenge' and setup i'm contemplating is how to use Coda for both managing/developing/previewing pre-rendered jekyll "code", while also being positioned to examine/manage/push/sync rendered code
+ [2014-12-28T19:29:07Z] jaybe all that is based on personal decisions; i.e. rendering locally versus on the server, etc.
+ [2014-12-28T19:39:52Z] travis-ci jekyll/jekyll#4949 (separate-jekyll-docs) The build passed. http://travis-ci.org/jekyll/jekyll/builds/45297345
+ [2014-12-28T19:39:53Z] jekyllrb Title: Travis CI - Free Hosted Continuous Integration Platform for the Open Source Community (at travis-ci.org)

message no. 68528

Posted by marcosscriven in #jekyll at 2014-12-28T01:54:20Z

Can anyone point to 'best practice' for embedding (minimal) structure into Jekyll (particularly within GitHub pages)? There appear to be a few options:
+ [2014-12-29T04:10:57Z] travis-ci jekyll/jekyll-docs#11 (add-tests) The build was fixed. http://travis-ci.org/jekyll/jekyll-docs/builds/45323467
+ [2014-12-29T04:10:59Z] jekyllrb Title: Travis CI - Free Hosted Continuous Integration Platform for the Open Source Community (at travis-ci.org)
+ [2014-12-29T04:14:22Z] travis-ci jekyll/jekyll-docs#13 (master) The build passed. http://travis-ci.org/jekyll/jekyll-docs/builds/45323720
+ [2014-12-29T04:14:24Z] jekyllrb Title: Travis CI - Free Hosted Continuous Integration Platform for the Open Source Community (at travis-ci.org)
+ [2014-12-29T04:58:36Z] travis-ci jekyll/integration-tests#193 The build has errored. http://travis-ci.org/jekyll/integration-tests/builds/45325310