About GitHub Pages
You can use GitHub Pages to host a website about yourself, your organization, or your project directly from a GitHub Enterprise repository.
GitHub Pages is available in public repositories with GitHub Free, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server.
In this article
- About GitHub Pages
- Types of GitHub Pages sites
- Publishing sources for GitHub Pages sites
- Static site generators
- Guidelines for using GitHub Pages
- MIME types on GitHub Pages
About GitHub Pages
To get started, see "Creating a GitHub Pages site."
Types of GitHub Pages sites
User and organization sites are always published from a repository named
The source files for a project site are stored in the same repository as their project.
You can only create one user or organization site for each GitHub Enterprise account. Project sites, whether owned by an organization or a user account, are unlimited.
The URL where your site is available depends on whether subdomain isolation is enabled for your GitHub Enterprise Server instance.
|Type of site||Subdomain isolation enabled||Subdomain isolation disabled|
|Project site owned by user account||
|Project site owned by organization account||
For more information, see "Enabling subdomain isolation" or contact your site administrator.
Publishing sources for GitHub Pages sites
The publishing source for your GitHub Pages site is the branch or folder where the source files for your site are stored. All sites have a default publishing source, and project sites have additional publishing sources available.
The default publishing source for user and organization sites is the
master branch. If the repository for your user or organization site has a
master branch, your site will publish automatically from that branch. You cannot choose a different publishing source for user or organization sites.
The default publishing source for a project site is the
gh-pages branch. If the repository for your project site has a
gh-pages branch, your site will publish automatically from that branch.
Project sites can also be published from the
master branch or a
/docs folder on the
master branch. To publish your site from one of these sources, you must configure a different publishing source. For more information, see "Configuring a publishing source for your GitHub Pages site."
If you choose the
/docs folder of the
master branch as your publishing source, GitHub Pages will read everything to publish your site from the
Static site generators
GitHub Pages publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. We recommend Jekyll, a static site generator with built-in support for GitHub Pages and a simplified build process. For more information, see "About GitHub Pages and Jekyll."
GitHub Pages will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called
.nojekyll in the root of your publishing source, then follow your static site generator's instructions to build your site locally.
GitHub Pages does not support server-side languages such as PHP, Ruby, or Python.
Guidelines for using GitHub Pages
GitHub Pages sites are subject to the following usage limits:
- GitHub Pages source repositories have a recommended limit of 1GB.
- Published GitHub Pages sites may be no larger than 1 GB.
MIME types on GitHub Pages
A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. GitHub Pages supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the mime-db project.
While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on GitHub Pages. For more information, see the mime-db contributing guidelines.