To get started, see "Creating a Páginas de GitHub site."
To publish a user site, you must create a repository owned by your user account that's named
<username>.<hostname>. To publish an organization site, you must create a repository owned by an organization that's 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 account on GitHub Enterprise. 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 tu instancia de servidor de GitHub Enterprise.
|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.
The publishing source for your Páginas de GitHub site is the branch and folder where the source files for your site are stored.
Warning: If your site administrator has enabled Public Pages, Páginas de GitHub sites are publicly available on the internet, even if the repository for the site is private or internal. If you have sensitive data in your site's repository, you may want to remove it before publishing. For more information, see "Configuring Páginas de GitHub on your appliance" and "About repository visibility."
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 Páginas de GitHub site."
If you choose the
/docs folder of the
master branch as your publishing source, Páginas de GitHub will read everything to publish your site from the
You cannot publish your project site from any other branch, even if the default branch is not
Páginas de GitHub 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 Páginas de GitHub and a simplified build process. For more information, see "About Páginas de GitHub and Jekyll."
Páginas de GitHub 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.
Páginas de GitHub does not support server-side languages such as PHP, Ruby, or Python.
Páginas de GitHub sites are subject to the following usage limits:
- Páginas de GitHub source repositories have a recommended limit of 1GB.
- Published Páginas de GitHub sites may be no larger than 1 GB.
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. Páginas de GitHub 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 Páginas de GitHub. For more information, see the mime-db contributing guidelines.