Make public projects boards and gists internal for AE (github#17247)

content/github/managing-your-work-on-github/changing-project-board-visibility.md

@@ -1,6 +1,6 @@
 ---
 title: Changing project board visibility
-intro: 'As an organization owner or project board admin, you can make a project board public or private.'
+intro: 'As an organization owner or project board admin, you can make a project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.'
 redirect_from:
   - /articles/changing-project-board-visibility
 versions:
@@ -13,12 +13,12 @@ versions:
 
 {% tip %}
 
-**Tip:** When you make your project board public, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+**Tip:** When you make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving project board access to teams they're on or by adding them to the project board as a collaborator. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endtip %}
 
-1. Navigate to the project board you want to make public or private.
+1. Navigate to the project board you want to make {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private.
 {% data reusables.project-management.click-menu %}
 {% data reusables.project-management.access-collaboration-settings %}
-4. Under "Visibility", select **Public** or **Private**. Then, click **Save**.
-![Public and private radio buttons](/assets/images/help/projects/project-board-visibility-options.png)
+{% data reusables.project-management.choose-visibility %}
+1. Click **Save**.

content/github/managing-your-work-on-github/copying-a-project-board.md

@@ -27,7 +27,6 @@ A project board's automation is also enabled by default. For more information, s
 ![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png)
 7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)."
 ![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png)
-8. If you are copying an organization-owned project board, under "Visibility", select whether you want your copied project board to be private or public.
-![Select visibility settings for copied project board](/assets/images/help/projects/copied-project-board-visibility-settings.png)
+{% data reusables.project-management.choose-visibility %}
 9. Click **Copy project**.
 ![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png)

content/github/managing-your-work-on-github/creating-a-project-board.md

@@ -30,6 +30,7 @@ You can also configure workflow automations to keep your project board in sync w
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
+{% data reusables.project-management.choose-visibility %}
 {% data reusables.project-management.linked-repositories %}
 {% data reusables.project-management.create-project-button %}
 {% data reusables.project-management.add-column-new-project %}
@@ -49,6 +50,7 @@ You can also configure workflow automations to keep your project board in sync w
 {% data reusables.project-management.click-new-project %}
 {% data reusables.project-management.create-project-name-description %}
 {% data reusables.project-management.choose-template %}
+{% data reusables.project-management.choose-visibility %}
 {% data reusables.project-management.linked-repositories %}
 {% data reusables.project-management.create-project-button %}
 {% data reusables.project-management.add-column-new-project %}

content/github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization.md

@@ -30,7 +30,7 @@ For example, if an organization owner has given all organization members read pe
 
 ### Project board visibility
 
-{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to public and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
+{% data reusables.project-management.project-board-visibility %} You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
 
 ### Further reading
 

content/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards.md

@@ -22,7 +22,7 @@ There are three levels of permissions for project board collaborators:
 The project board owner and collaborators with admin access have full control of the project board. In addition to all the permissions allowed by project board collaborators, a project board owner and collaborator with admin access can:
 
 - [Manage, view, and add collaborators](/articles/managing-access-to-your-user-account-s-project-boards)
-- [Configure a project board as public or private](/articles/changing-project-board-visibility)
+- [Configure a project board as {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private](/articles/changing-project-board-visibility)
 - [Delete a project board](/articles/deleting-a-project-board/)
 - [Close a project board](/articles/closing-a-project-board/)
 - [Reopen a closed project board](/articles/reopening-a-closed-project-board)
@@ -51,7 +51,7 @@ Collaborators with write access to a user-owned project board can:
 
 ### Project board visibility
 
-You can change the project board's visibility from private to public and back again. By default, user-owned project boards are private. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
+You can change the project board's visibility from private to {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and back again. By default, user-owned project boards are private. For more information, see "[Changing project board visibility](/articles/changing-project-board-visibility)."
 
 ### Further reading
 

content/github/writing-on-github/creating-gists.md

@@ -1,6 +1,6 @@
 ---
 title: Creating gists
-intro: 'You can create two kinds of gists: public and secret. Create a public gist if you''re ready to share your ideas with the world or a secret gist if you''re not.'
+intro: 'You can create two kinds of gists: {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} and secret. Create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.'
 redirect_from:
   - /articles/about-gists/
   - /articles/cannot-delete-an-anonymous-gist/
@@ -14,11 +14,13 @@ versions:
 
 ### About gists
 
-Every gist is a Git repository, which means that it can be forked and cloned. If you are signed in to {% data variables.product.product_name %} when you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}.
+Every gist is a Git repository, which means that it can be forked and cloned. {% if currentVersion != "github-ae@latest" %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}.
 
-Gists can be public or secret. Public gists show up in {% data variables.gists.discover_url %}, where people can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work. {% data reusables.gist.cannot-convert-public-gists-to-secret %}
+Gists can be {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret. {% if currentVersion == "github-ae@latest" %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% if currentVersion == "github-ae@latest" %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work.
 
-Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. {% data reusables.gist.cannot-convert-public-gists-to-secret %} Secret gists aren't private. If you send the URL of a secret gist to a friend, they'll be able to see it. However, if someone you don't know discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead.
+Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable. Secret gists aren't private. If you send the URL of a secret gist to {% if currentVersion == "github-ae@latest" %}another enterprise member{% else %}a friend {% endif %}, they'll be able to see it. However, if {% if currentVersion == "github-ae@latest" %}any other enterpise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead.
+
+{% data reusables.gist.cannot-convert-public-gists-to-secret %}
 
 {% if enterpriseServerVersions contains currentVersion %}
 
@@ -39,7 +41,7 @@ You can pin gists to your profile so other people can see them easily. For more
 
 {% endif %}
 
-You can discover gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code).
+You can discover {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code).
 
 Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists).
 
@@ -71,13 +73,8 @@ You can also create a gist using the {% data variables.product.prodname_cli %}.
 4. Type the text of your gist into the gist text box.
 ![Gist text box](/assets/images/help/gist/gist_text_box.png)
 
-5. Do one of the following:
-    - To create a public gist, click **Create public gist**.
-    - To create a secret gist, click **Create secret Gist**.
-  ![Gist create button](/assets/images/help/gist/gist_create_btn.png)
-
-  {% note %}
-
-  **Note:** {% data reusables.gist.cannot-convert-public-gists-to-secret %}
+5. Optionally, to create {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. 
+![Drop-down menu to select gist visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %}
 
-  {% endnote %}
+6. Click **Create secret Gist** or **Create {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} gist**. 
+  ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png)

content/github/writing-on-github/forking-and-cloning-gists.md

@@ -11,7 +11,7 @@ versions:
 
 ### Forking gists
 
-Each gist indicates which forks have activity, making it easy to find interesting changes from coworkers or complete strangers.
+Each gist indicates which forks have activity, making it easy to find interesting changes from others.
 
 ![Gist forks](/assets/images/help/gist/gist_forks.png)
 

data/glossaries/external.yml

@@ -256,8 +256,8 @@
 - term: Gist
   description: >-
     A gist is a shareable file that you can edit, clone, and fork on GitHub.
-    You can make a gist public or secret, although secret gists will be
-    available to anyone with the URL.
+    You can make a gist {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or secret, although secret gists will be
+    available to {% if currentVersion == "github-ae@latest" %}any enterprise member{% else %}anyone{% endif %} with the URL.
 - term: Git
   description: >-
     Git is an open source program for tracking changes in text files. It was

data/reusables/gist/cannot-convert-public-gists-to-secret.md

@@ -1 +1 @@
-After creating a gist, you cannot convert it from public to secret.
+After creating a gist, you cannot convert it from {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} to secret.

data/reusables/project-management/choose-visibility.md

@@ -0,0 +1,2 @@
+1. Under "Visibility", choose to make your project board {% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} or private. For more information, see "[Changing project board visibility](/github/managing-your-work-on-github/changing-project-board-visibility)."
+  ![Radio buttons to choose project board visibility]{% if currentVersion == "github-ae@latest" %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %}

data/reusables/project-management/project-board-visibility.md

@@ -1 +1 @@
-By default, your project board is private and only visible to people with read, write, or admin permissions to the project board. A public project board is visible to anyone with the project board's URL.
+By default, your project board is private and only visible to people with read, write, or admin permissions to the project board. {% if currentVersion == "github-ae@latest" %}An internal{% else %}A public{% endif %} project board is visible to {% if currentVersion == "github-ae@latest" %}any enterprise members{% else %}anyone{% endif %} with the project board's URL.

data/variables/gists.yml

@@ -1,8 +1,8 @@
 gist_homepage: >-
-  {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled {% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[gist home page](https://gist.github.com/){% elsif currentVersion == "github-ae@latest" %}gist home page, `http(s)://gist.[hostname)`,{% else %}gist home page, `http(s)://[hostname]/gist` or `http(s)://gist.[hostname]` if subdomains are enabled{% endif %}
 
 gist_search_url: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[Gist Search](https://gist.github.com/search){% elsif currentVersion == "github-ae@latest" %}Gist Search, `http(s)://gist.[hostname]/search`,{% else %}Gist Search, `http(s)://[hostname]/gist/search` or `http(s)://gist.[hostname]/search` if subdomains are enabled{% endif %}
 
 discover_url: >-
-  {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %}
+  {% if currentVersion == "free-pro-team@latest" %}[Discover](https://gist.github.com/discover){% elsif currentVersion == "github-ae@latest" %}Discover, `http(s)://gist.[hostname]/discover`,{% else %}Discover, `http(s)://[hostname]/gist/discover` or `http(s)://gist.[hostname]/discover` if subdomains are enabled{% endif %}