[Docs] Properly document how GitHub Pages CNAME file works in conjunction w/ settings about forestry.io

[chrisdmacrae]

[4:39 PM] 
jordan It’s not an issue at all. It has to do with where you put the file


[4:39 PM] 
if it’s a hugo site then the file needs to go into the static directory so that it gets published


[4:40 PM] 
if it’s jekyll then it should just be in the root of the project


[4:40 PM] 
chrisdmacrae ^^^ i'm not sure what that has to do w/ a file???

[4:42 PM] 
jordan @chrisdmacrae if the CNAME file is in the root of your hugo project and you have forestry build the project and then push it to the gh-pages branch, the CNAME file isn’t going to be included because hugo doesn’t include files from the root of the project in the built site. So if you want it in the root of your built site then you should put the CNAME file in the static directory (edited)

[4:43 PM] 
chrisdmacrae @jordan But I think the issue here was that the actual setting in GitHub pages was getting removed. Is that caused by the CNAME file?


[4:44 PM] 
jordan @chrisdmacrae They are one and the same. If you create the CNAME file, it sets the setting. If you set the setting, it creates the CNAME file for you.


[4:44 PM] 
chrisdmacrae Ah ok


[4:45 PM] 
That makes sense! I'll move that issue over to the new site to create a doc


[4:45 PM] 
jordan In this scenario though, the setting won’t be set for the master branch because the CNAME file is in the static dir.