The Jekyll project repository itself is a perfect example of this branch structure—the master branch contains the actual software project for Jekyll, and the Jekyll website that you’re looking at right now is contained in the docs folder of the same repository.
If all else fails, you should contact Git Hub Support. However, the subdirectory-like URL structure Git Hub uses for Project Pages complicates the proper resolution of URLs.
In order to assure your site builds properly, use the handy URL filters: branch all the URLs will resolve properly.
Note that Git Hub Pages works equally well for regular HTML content, simply because Jekyll treats files without YAML front matter as static assets.
So if you only need to push generated HTML, you’re good to go without any further setup. See this marvelous guide by Jonathan Mc Glone to get you up and running.
When setting a Type Script version on a project, the project becomes fixed on that version.
Even if a new Type Script version becomes available through a Visual Studio update or a manual SDK download, the project will still use the version it is fixed to.
To stay on the latest version, we encourage you to set your projects to "use latest available" as described in step 4 above.
During installation of Visual Studio 2017 version 15.2, Type Script 2.2 will be automatically included with the Web, Node.js, Universal Windows, or Mobile Java Script workloads.
Github Pages is a sweet service that builds your Jekyll site for you when you commit changes to a Github repo.