What is Pages?

Who can use this feature?

Pages is available in public repositories with Free and Free for organizations, and in public and private repositories with Pro, Team, Enterprise Cloud, and Enterprise Server. For more information, see ’s plans.

Pages now uses Actions to execute the Jekyll build. When using a branch as the source of your build, Actions must be enabled in your repository if you want to use the built-in Jekyll workflow. Alternatively, if Actions is unavailable or disabled, adding a .nojekyll file to the root of your source branch will bypass the Jekyll build process and deploy the content directly. For more information on enabling Actions, see Managing Actions settings for a repository.

In this article

Pages is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on , optionally runs the files through a build process, and publishes a website. You can see examples of Pages sites in the Pages examples collection.

There are two types of Pages sites. Sites associated with a user or organization account, and sites for a specific project.

PropertyUser and organization sitesProject sites
Source filesMust be stored in a repository named <owner>..io, where <owner> is the personal or organization account nameStored in a folder within the repository that contains the project's code
LimitsMaximum of one pages site per accountMaximum of one pages site per repository
Default site locationhttp(s)://<owner>..iohttp(s)://<owner>..io/<repositoryname>

If you publish your site privately, the URL for your site will be different. For more information, see Changing the visibility of your Pages site.

You can host your site on 's .io domain or your own custom domain. See Configuring a custom domain for your Pages site.