+ [2016-12-18T17:33:48Z] miklb s/fornt/front/
+ [2016-12-18T17:33:49Z] jekyllrb For the record, miklb meant: webjay right, but without seeing the front matter, there's really no way of knowing what is hardcoded and what isn't
+ [2016-12-19T04:23:08Z] parsnip why the does `jekyll new ./' ask for a password?
+ [2016-12-19T05:01:17Z] jaybe i doubt it does
+ [2016-12-19T05:01:58Z] jaybe if it does, consider the location within the filesystem when executing the command, and your permissions therein

message no. 159752

Posted by jaybe in #jekyll at 2016-12-19T05:01:58Z

if it does, consider the location within the filesystem when executing the command, and your permissions therein
+ [2016-12-20T15:43:54Z] gsnedders Locally, I'm having page.title be empty, yet on GitHub Pages it's taking the highest level title seemingly. Why would there be a difference? Locally everything is installed from the github-pages gem.
+ [2016-12-20T15:47:30Z] jaybe Because [[ github pages ]]
+ [2016-12-20T15:47:30Z] jekyllrb (github pages) (#1) https://help.github.com/articles/using-jekyll-with-pages/, or (#2) https://help.github.com/articles/what-is-github-pages/
+ [2016-12-20T15:51:07Z] gsnedders jaybe: oh, duh, I'd missed the vital part when reading over it before. sorry! is the Github Pages default config anywhere, given it seems to include plugins magically?
+ [2016-12-20T16:34:19Z] jaybe ./shrug