This is related to #11 my branch actually is 3 commits behind but this PR simply pushes the relevant file changes. Nevertheless if I would update my fork with p2coder's latest changes I would have the CNAME and google analytics code snippets again in my private gh-pages which would result in identity conflicts for both CNAME and analytics.
Note: When updating forks make sure to not pulish CNAME and google analytics code to the gh-pages branch of the forks. Actually #11 is still alive and critical ...
This is related to #11 my branch actually is 3 commits behind but this PR simply pushes the relevant file changes. Nevertheless if I would update my fork with p2coder's latest changes I would have the CNAME and google analytics code snippets again in my private gh-pages which would result in identity conflicts for both CNAME and analytics.
Note: When updating forks make sure to not pulish CNAME and google analytics code to the gh-pages branch of the forks. Actually #11 is still alive and critical ...