What is Pages?

You can use Pages to host a website about yourself, your organization, or your project directly from a repository on .

Кто может использовать эту функцию?

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.

В этой статье

About Pages

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.

Types of Pages sites

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

Property	User and organization sites	Project sites
Source files	Must be stored in a repository named `<owner>..io`, where `<owner>` is the personal or organization account name	Stored in a folder within the repository that contains the project's code
Limits	Maximum of one pages site per account	Maximum of one pages site per repository
Default site location	`http(s)://<owner>..io`	`http(s)://<owner>..io/<repositoryname>`

Hosting on your own custom domain

You can host your site on 's .io domain or your own custom domain. See Настройка личного домена для сайта Pages.

Data collection

When a Pages site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into or not. For more information about 's security practices, see Privacy Statement.