Skip to content

Commit e3a169c

Browse files
graceparkgracepark
authored
Part 3: Third fourth content unordered lists from dash to asterisk (#51097)
1 parent 6acca22 commit e3a169c

253 files changed

Lines changed: 1871 additions & 1871 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -78,9 +78,9 @@ An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through you
7878

7979
There are a couple of reasons your site might be automatically disabled.
8080

81-
- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan)."
82-
- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/transferring-a-repository)."
81+
* If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[AUTOTITLE](/billing/managing-the-plan-for-your-github-account/downgrading-your-accounts-plan)."
82+
* If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/transferring-a-repository)."
8383

8484
## Further reading
8585

86-
- "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages)"
86+
* "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages)"

‎content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
4949
{% data reusables.pages.sidebar-pages %}
5050
1. Under "Custom domain", type your custom domain, then click **Save**. If you are publishing your site from a branch, this will create a commit that adds a `CNAME` file directly to the root of your source branch. If you are publishing your site with a custom {% data variables.product.prodname_actions %} workflow, no `CNAME` file is created, so you need to create one manually (containing only a line of text with your custom domain). For more information about your publishing source, see "[AUTOTITLE](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)."
5151
1. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. If you're implementing IPv6 support, we highly recommend using an `A` record in addition to your `AAAA` record, due to slow adoption of IPv6 globally. {% data reusables.pages.contact-dns-provider %}
52-
- To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
53-
- To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
52+
* To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
53+
* To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
5454

5555
```shell
5656
185.199.108.153
@@ -59,7 +59,7 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
5959
185.199.111.153
6060
```
6161

62-
- To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
62+
* To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
6363

6464
```shell
6565
2606:50c0:8000::153
@@ -71,7 +71,7 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
7171
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
7272
{% data reusables.command_line.open_the_multi_os_terminal %}
7373
1. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
74-
- For `A` records:
74+
* For `A` records:
7575

7676
```shell
7777
$ dig EXAMPLE.COM +noall +answer -t A
@@ -81,7 +81,7 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
8181
> EXAMPLE.COM 3600 IN A 185.199.111.153
8282
```
8383

84-
- For `AAAA` records:
84+
* For `AAAA` records:
8585

8686
```shell
8787
$ dig EXAMPLE.COM +noall +answer -t AAAA
@@ -181,4 +181,4 @@ If you get an error about a custom domain being taken, you may need to remove th
181181

182182
## Further reading
183183

184-
- "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages)"
184+
* "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages)"

‎content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -26,28 +26,28 @@ For your site to render at the correct domain, make sure your CNAME file still e
2626

2727
Then, make sure the CNAME file is formatted correctly.
2828

29-
- The CNAME filename must be all uppercase.
30-
- The CNAME file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
31-
- The CNAME file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`.
32-
- The domain name must be unique across all {% data variables.product.prodname_pages %} sites. For example, if another repository's CNAME file contains `example.com`, you cannot use `example.com` in the CNAME file for your repository.
29+
* The CNAME filename must be all uppercase.
30+
* The CNAME file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
31+
* The CNAME file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`.
32+
* The domain name must be unique across all {% data variables.product.prodname_pages %} sites. For example, if another repository's CNAME file contains `example.com`, you cannot use `example.com` in the CNAME file for your repository.
3333

3434
## DNS misconfiguration
3535

3636
If you have trouble pointing the default domain for your site to your custom domain, contact your DNS provider.
3737

3838
You can also use one of the following methods to test whether your custom domain's DNS records are configured correctly:
3939

40-
- A CLI tool such as `dig`. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site)".
41-
- An online DNS lookup tool.
40+
* A CLI tool such as `dig`. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site)".
41+
* An online DNS lookup tool.
4242

4343
## Custom domain names that are unsupported
4444

4545
If your custom domain is unsupported, you may need to change your domain to a supported domain. You can also contact your DNS provider to see if they offer forwarding services for domain names.
4646

4747
Make sure your site does not:
48-
- Use more than one apex domain. For example, both `example.com` and `anotherexample.com`.
49-
- Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`.
50-
- Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`.
48+
* Use more than one apex domain. For example, both `example.com` and `anotherexample.com`.
49+
* Use more than one `www` subdomain. For example, both `www.example.com` and `www.anotherexample.com`.
50+
* Use both an apex domain and custom subdomain. For example, both `example.com` and `docs.example.com`.
5151

5252
The one exception is the `www` subdomain. If configured correctly, the `www` subdomain is automatically redirected to the apex domain. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)."
5353

‎content/pages/getting-started-with-github-pages/about-github-pages.md‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -80,9 +80,9 @@ For more information, see "[AUTOTITLE](/pages/getting-started-with-github-pages/
8080

8181
If you're a {% data variables.enterprise.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited.
8282

83-
- {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations.
84-
- {% data variables.product.prodname_pages %} sites are always privately published, and you cannot change this visibility. For more information, see "[AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
85-
- You cannot create an organization site (a site published from a repository named `<organization>.github.io`)
83+
* {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations.
84+
* {% data variables.product.prodname_pages %} sites are always privately published, and you cannot change this visibility. For more information, see "[AUTOTITLE](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
85+
* You cannot create an organization site (a site published from a repository named `<organization>.github.io`)
8686

8787
For more information about {% data variables.product.prodname_emus %}, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
8888
{% endif %}
@@ -117,13 +117,13 @@ Using {% data variables.product.prodname_pages %} to create a copy of an existin
117117

118118
{% data variables.product.prodname_pages %} sites are subject to the following usage limits:
119119

120-
- {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB.{% ifversion fpt or ghec %} For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-and-repository-size-limitations)"{% endif %}
121-
- Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB.
122-
- {% data variables.product.prodname_pages %} deployments will timeout if they take longer than 10 minutes.
120+
* {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB.{% ifversion fpt or ghec %} For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-and-repository-size-limitations)"{% endif %}
121+
* Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB.
122+
* {% data variables.product.prodname_pages %} deployments will timeout if they take longer than 10 minutes.
123123
{% ifversion fpt or ghec %}
124-
- {% data variables.product.prodname_pages %} sites have a _soft_ bandwidth limit of 100 GB per month.
125-
- {% data variables.product.prodname_pages %} sites have a _soft_ limit of 10 builds per hour. This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow.
126-
- In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body.
124+
* {% data variables.product.prodname_pages %} sites have a _soft_ bandwidth limit of 100 GB per month.
125+
* {% data variables.product.prodname_pages %} sites have a _soft_ limit of 10 builds per hour. This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow.
126+
* In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body.
127127

128128
If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.github_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs.
129129

@@ -144,5 +144,5 @@ When a {% data variables.product.prodname_pages %} site is visited, the visitor'
144144

145145
## Further reading
146146

147-
- [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %}
148-
- "[AUTOTITLE](/rest/repos#pages)"
147+
* [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %}
148+
* "[AUTOTITLE](/rest/repos#pages)"

‎content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,8 @@ Access control is available for project sites that are published from a private
2525

2626
Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published:
2727

28-
- We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS.
29-
- We use a unique subdomain for the privately published site to ensure that other repositories in your organization cannot publish content on the same origin as the site. This protects your site from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain.
28+
* We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS.
29+
* We use a unique subdomain for the privately published site to ensure that other repositories in your organization cannot publish content on the same origin as the site. This protects your site from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain.
3030

3131
You can see your site's unique subdomain in the "Pages" tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[AUTOTITLE](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator.
3232

‎content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,4 +35,4 @@ shortTitle: Create custom 404 page
3535

3636
## Further reading
3737

38-
- [Front matter](https://jekyllrb.com/docs/frontmatter) in the Jekyll documentation
38+
* [Front matter](https://jekyllrb.com/docs/frontmatter) in the Jekyll documentation

‎content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ To customize your site even more, you can use Jekyll, a static site generator wi
6464

6565
## Further reading
6666

67-
- "[AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
68-
- "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)"
69-
- "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)"
70-
- "[AUTOTITLE](/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites)"
67+
* "[AUTOTITLE](/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
68+
* "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)"
69+
* "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)"
70+
* "[AUTOTITLE](/pages/getting-started-with-github-pages/troubleshooting-404-errors-for-github-pages-sites)"

‎content/pages/getting-started-with-github-pages/deleting-a-github-pages-site.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,8 @@ shortTitle: Delete a GitHub Pages site
1515
## Deleting your site
1616

1717
You can delete your site in two ways:
18-
- Delete the repository. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/deleting-a-repository)."
19-
- Change the source to the `None` branch. For more information, see [Deleting your site by changing the source](#deleting-your-site-by-changing-the-source) below.
18+
* Delete the repository. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/deleting-a-repository)."
19+
* Change the source to the `None` branch. For more information, see [Deleting your site by changing the source](#deleting-your-site-by-changing-the-source) below.
2020

2121
If you want to remove the current deployment of your site but do not want to delete the site, you can unpublish your site. For more information, see "[AUTOTITLE](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)."
2222

‎content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -51,10 +51,10 @@ If you enable HTTPS for your {% data variables.product.prodname_pages %} site bu
5151
To remove your site's mixed content, make sure all your assets are served over HTTPS by changing `http://` to `https://` in your site's HTML.
5252

5353
Assets are commonly found in the following locations:
54-
- If your site uses Jekyll, your HTML files will probably be found in the __layouts_ folder.
55-
- CSS is usually found in the `<head>` section of your HTML file.
56-
- JavaScript is usually found in the `<head>` section or just before the closing `</body>` tag.
57-
- Images are often found in the `<body>` section.
54+
* If your site uses Jekyll, your HTML files will probably be found in the __layouts_ folder.
55+
* CSS is usually found in the `<head>` section of your HTML file.
56+
* JavaScript is usually found in the `<head>` section or just before the closing `</body>` tag.
57+
* Images are often found in the `<body>` section.
5858

5959
{% tip %}
6060

0 commit comments

Comments
 (0)