It already works and you don’t have to do anything I’m not sure if you are already aware of that or not but to remove .html extension from GitHub Pages all you have to do is remove .html extension from your links. In other words it already works and you don’t have to do anything. … Read more
You can but you can’t use html5 mode (removes the # from urls). If you use html5 mode, you have to redirect all requests to the root url since its a single page app. Since you can’t use server side code on GitHub pages, you can’t do this. So, if you don’t mind the # … Read more
Yes, you can. Put this into the head part of your webpage: <link rel=”shortcut icon” type=”image/x-icon” href=”https://stackoverflow.com/questions/35037482/favicon.ico”> It is important to not put the slash before the favicon.ico part. Put the favicon.ico file in your repository’s home directory.
Although you can’t use .htaccess or .conf, Github has instructions on how to use the Jekyll Redirect From plugin. https://help.github.com/articles/redirects-on-github-pages/ The page above no longer has any mention of the plugin. The direct link to the jekyll-redirect-from plugin GitHub repo is https://github.com/jekyll/jekyll-redirect-from
Create a dummy index.html at the root and put this in your header: <meta http-equiv=”refresh” content=”0; url=https://repo.github.io/folder/index.html”> Be sure to change the destination URL. This will instantly redirect from index.html to your folder/index.html.
Short answer Step 1: Add a new file CNAME to your GitHub Pages repository containing only one line: your top-level domain name. E.g.: example.com Step 2: [Optional] but highly recommended 2.1: Remove all other top-level records (prefixed with @) of type A from your DNS configuration. 2.2: Remove a CNAME record for the second-level domain … Read more
While building my own site I came across this very same problem, and I have found an (IMHO) easy and robust solution. The Problem Given a subset of pages (not posts) on the site, list them under headings based on their categories. For example: given a set of pages which we consider resource pages (or … Read more
EDIT: Yay! Looks like GitHub Pages now supports CORS: https://twitter.com/invisiblecomma/status/575219895308324864 This can be verified by curling a request to enable-cors.org (which is hosted on GitHub Pages). Running this command: curl -v enable-cors.org > /dev/null returns an Access-Control-Allow-Origin: * header. There’s no way to support CORS on GitHub Pages, though I’d love to see this feature. … Read more
No, this is not possible. See the GitHub Help docs that explain this: Ensure you only have one domain listed in your CNAME file. If you wish to have multiple domains pointing to the same Pages, you will need to set up redirects for the other domains. Most domain registrars and DNS hosts offer this … Read more