Rework the build other apps page for using github organization

Author: marionbarker

docs/browser/other-apps.md

@@ -9,26 +9,14 @@ Once Loop 3 was released with the ability to build using a browser, a lot of oth
 
 If you want to build another DIY app that is not included here, look for the file `fastlane/testflight.md` in the *GitHub* repository associated with that app and open it in a browser. The instructions for that app should be located in that file.
 
-The same technique is used and the same six <code>Secrets</code> are applied to each `repository`. Those secrets are tied to your *Apple* Developer ID and your *GitHub* account.
+The same technique is used and the same six <code>Secrets</code> are used for many Open-Source apps. Over time, it is expected that more apps will use the `variable` ENABLE_NUKE_CERTS to allow automatic creation and update of the required certificates.
+
+* Did you start building with your personal account and want to switch to the recommended organization account for buiding?: [Switch to a GitHub Organization Account](#switch-to-a-github-organization-account)
 
 ### Updating / Rebuilding Other Apps
 
 If you are coming to this page to update one of the other apps, follow the [How to Update or Rebuild](bb-update.md#how-to-update-or-rebuild){: target="_blank" } instructions provided for the *Loop* app, but substitute the repository name for the app you want to rebuild for all references to&nbsp;*<span translate="no">LoopWorkspace</span>*.
 
-### Optional Build Method
-
-!!! tip "Set up a Organization Account"
-    If you are going to be building a lot of different apps, you should set up a free organization account with *GitHub* and use that to build.
-
-    Pros:
-
-    * The 6 <code>Secrets</code> and 1 `Variable` can be added to the organization one-time and apply to every repository
-
-    Cons:
-
-    * None other than a little prep work:
-        * [Switch to a *GitHub* Organization Account](#switch-to-a-github-organization-account)
-
 ### Multiple Copies of `LoopFollow`
 
 For the convenience of caregivers who use `LoopFollow` to monitor multiple people, updates were added in v2.1.2 to make this more convenient. This works regardless of the build method. (Build with Browser or [Build with *Mac*](https://www.loopandlearn.org/loop-follow#lf-script){: target="_blank" }).
@@ -48,17 +36,12 @@ For the convenience of caregivers who use `LoopFollow` to monitor multiple peopl
     * After all your secrets are collected, continue on this page with [<span translate="no">Fork and Add Secrets</span>](#fork-and-add-secrets).
 
 ## <span translate="no">Fork and Add Secrets</span>
-    
-!!! important "Use the <code>repository</code> for the application you are building"
-    Many graphics show&nbsp;<span translate="no">LoopWorkspace</span>. You need to replace that with the <code>repository</code> for the app you want to build. You may need to adjust the App Name, the Shared App Group and look for different Identifiers.
-    
-    Instructions for&nbsp;_<span translate="no">LoopCaregiver</span>_&nbsp;or &nbsp;_<span translate="no">LoopFollow</span>_ are found on this page.
-    
-    Other apps such as xDrip4iOS and Trio can also be built with this method. Refer to the repository associated with those other apps, examine the fastlane folder and open the testflight.md file in your browser to get specific details for building that app.
 
-You will return to this page after reviewing (but not doing) this step [Configure to Use Browser: <span translate="no">Fork LoopWorkspace</span>](prepare-fork.md#fork-loopworkspace)
+> If you are not using an organization, stop and reconsider. This page assumes an organization and that you have added your `Secrets` and your `Variable` to your organization. If not, then for every app you `fork` you must individually add those to the repository in your personal account.
 
-* Use the same method as that section, but <span>`fork` the `repository` for the app</span> you plan to build
+You will return to this page after reviewing (but not doing) this step [Configure to Use Browser: <span translate="no">Fork LoopWorkspace</span>](prepare-fork.md#fork-loopworkspace){: target="_blank" }
+
+* Use the same method as that section, but <span>`fork` the `repository` for the app</span> you plan to build to your *GitHub* organization
 * _<span translate="no">LoopCaregiver</span>_, expect the `dev branch`
 * _<span translate="no">LoopFollow</span>_, expect the `main branch`
 
@@ -78,11 +61,13 @@ The two repositories below are only if you need to follow a second or third loop
 
 ## Configure <code>Secrets</code> for this App
 
-> If you choose to use the optional *GitHub* organization method, you can skip this section:
+**When using a *GitHub* organization, you skip this section**:
+
+* All `repositories` in your *GitHub* organization use the organization <code>Secrets and Variables</code>
+* If you have not already completed [Add <code>Secrets</code> to your *GitHub* Organization](#add-secrets-to-your-github-organization), do it now
+* Skip ahead to [Validate <code>Secrets</code>](#validate-secrets)
 
-> * All `repositories` in your *GitHub* organization use the organization <code>Secrets</code>
-> * Make sure you complete [Add <code>Secrets</code> to your *GitHub* Organization](#add-secrets-to-your-github-organization) instead of this section
-> * Skip ahead to [Validate <code>Secrets</code>](#validate-secrets)
+### Using a Personal *GitHub* Account
 
 After successfully creating your fork of the repository for this app:
 
@@ -92,7 +77,7 @@ After successfully creating your fork of the repository for this app:
     * You should follow the detailed steps at [Configure to Use Browser: Configure <code>Secrets</code>](../browser/prepare-fork.md#configure-secrets){: target="_blank" }, except you will apply the <code>Secrets</code> to the repository for the app you are planning to build
     * Once your 6 secrets have been added, return to this page and skip ahead to [Validate <code>Secrets</code>](#validate-secrets) on this page.
 
-### Add Existing <code>Secrets</code>
+#### Add Existing <code>Secrets</code>
 
 Open the text file in which you maintain a copy of your 6 <code>Secrets</code> so you can copy each value into the <code>Secrets</code> for this repository.
 
@@ -128,7 +113,7 @@ The workflows are now displayed: look at the list on the left side similar to th
 
 This step validates most of your six <code>Secrets</code> and provides error messages if it detects an issue with one or more.
 
-1. Click on the "Actions" tab of your  *LoopFollow*  or  *LoopCaregiver*repository and enable workflows if needed
+1. Click on the "Actions" tab of your  *LoopFollow*  or  *LoopCaregiver* repository and enable workflows if needed
 1. On the left side, click on 1. <code>Validate Secrets</code>
 1. On the right side, click `Run Workflow` to show a dropdown menu
     * You will see your default branch (`main` for LoopFollow, `dev` for LoopCaregiver)
@@ -191,7 +176,7 @@ The *LoopFollow* app does not require this extra step. You can skip ahead to [Cr
 
 ## Add `App Group` to `LoopCaregiver`
 
-As of 2023 December 8, the *LoopCaregiver* app requires the addition of an `App Group` to an expanded list of `Identifiers`. Follow these steps one time to be able to build the *LoopCaregiver* app after this update.
+The *LoopCaregiver* app requires the addition of an `App Group` to each of its list of `Identifiers`. Follow these steps one time to be able to build the *LoopCaregiver* app.
 
 ### Check if `App Group` Exists
 
@@ -278,8 +263,6 @@ The `Edit Your App ID Configuration` screen will open.
 !!! abstract "Same procedure as for the *Loop* app"
     You will follow the same procedure as you did with the *Loop* app.
 
-    You will also want to edit your new app once you create it to [Remove Apple Vision Pro](prepare-app.md#remove-apple-vision-pro){: target="_blank" }.
-
 You will be following the directions below to create an App in App Store Connect if you don't already have one.
 
 This requires you to provide some information. Examine the table below for the bundle ID associated with your app. 
@@ -317,9 +300,17 @@ This requires you to provide some information. Examine the table below for the b
 
 1. Click Create but do not fill out the next form. That is for submitting to the app store and you will not be doing that.
 
-1. Edit your new app to [Remove Apple Vision Pro](prepare-app.md#remove-apple-vision-pro){: target="_blank" }
+You are done with the create app step. You will use this same browser location to complete the next step. Tap on the *TestFlight* tab at the top of the page.
+
+## Add Users to *TestFlight* for App
+
+You need to configure a *TestFlight* Internal Testing Group for each app you build and invite the users (including yourself). 
+
+* Each person added to the Internal Testing Group gets an invitation to join the group for this app
+* Then after each successful build of the app, group members will get a notification when the new build is transferred to *TestFlight* and is available for use
+* They open the *TestFlight* app on their phone to install the new build
 
-You are done with this activity. Before you close this browser window, note the *TestFlight* tab at the top of the page. You'll be using that tab after you complete the next two actions.
+If you need detailed instruction, visit [Configure to Use Browser: *TestFlight* Users Overview](tf-users.md#testflight-users-overview){: target="_blank" }.
 
 ## Create Certificates
 
@@ -394,29 +385,26 @@ Please do not remove an existing app if you have trouble building a new one. You
     For more information, see [Do Not Remove an App](bb-errors.md#do-not-remove-an-app){: target="_blank" }.
 
 
-## Add Users to *TestFlight* for App
-
-Once the first build completes, you will be able to configure *TestFlight* for the app - follow the template for setting up *TestFlight* for Loop found in [Configure to Use Browser: *TestFlight* Users Overview](../browser/tf-users.md#testflight-users-overview).
-
 ## Install on Phone
 
 The [Install on Phone](phone-install.md) walks you through the steps to install the app to a phone. When going through those steps, replace your App Name for&nbsp;_<span translate="no">Loop</span>_. Everything else is the same.
 
 ## Switch to a *GitHub* Organization Account
 
-This section is optional. It is strongly recommended for anyone building more than one app.
+If you are already using an Organization account for building, no need to read this section - you are done with this page.
 
-### Set up a Free *GitHub* Organization
+There are a number of folks who started using the Browser Build method when only the Personal account method was documented. This section is meant to assist them in switching to an Organization account.
 
-Prerequisite: You need a personal *GitHub* account. If you do not already have a personal *GitHub* account, click on [New *GitHub* Account](secrets.md#new-github-account){: target="_blank" }.
+### Set up a Free *GitHub* Organization
 
 Detailed instructions for creating an organization are found at [Create a Free *GitHub* Organization](secrets.md#create-a-free-github-organization){: target="_blank" }.
 
-The directions below may be sufficient for some where you use your *GitHub* username instead of `my-name`.
+The directions below summarize that detailed section. Use your *GitHub* username instead of `my-name`.
+
+> Prerequisite: You need a personal *GitHub* account. If you do not already have a personal *GitHub* account, click on [New *GitHub* Account](secrets.md#new-github-account){: target="_blank" }.
 
-1. Follow the directions below to create a new *GitHub* organization account with a username of `my-name-org` (of course naming is up to you)
-    * There is documentation at this link, [New *GitHub* Organization](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch){: target="_blank" }, or you can follow the bullets below
-    * Log into `my-name` and click on your icon (at upper right) and choose Settings
+1. You will create a new *GitHub* organization account with a username of `my-name-org` (of course naming is up to you)
+    * Log into your *GitHub* account (username `my-name`) and click on your icon (at upper right) and choose Settings
     * On the left side-bar, click on Organizations
     * In the new view, click on New Organization and choose Free for the plan by clicking on  `Create a free organization`.
     * In the `Set up your organization` screen:
@@ -439,52 +427,41 @@ There are two steps to using this account moving forward:
 1. For each repository: you need to `fork` for each app you wish to build to the new `my-name-org` account
 
     * When you do the fork, there will be a dropdown menu under Owner for you to select the account for the `fork`
+        * For detailed directions with a GIF, see [Create the Fork](prepare-fork.md#create-the-fork){: target="_blank" }
     * Choose the organization account
-    * Other than that extra step, follow the standard `fork` directions
-        * This link provides instructions to [`Fork LoopWorkspace`](prepare-fork.md#fork-loopworkspace)
-        * Refer to the [Table of App `Repositories`](#table-of-app-repositories) when building apps other than the *Loop* app
-
-Then, for every build, you will use just the organization account. The original account is maintained to give you access to *GitHub* and holds your *GitHub* personal access token.
-
-> WARNING - If you have `forks` of DIY apps in your original `my-name` account that are configured to build automatically, you want to disable that and have only the `my-name-org` account be configured for automatic building. Refer to [Disable Building for Personal *GitHub* account](#disable-building-for-personal-github-account).
+    * Refer to the [Table of App `Repositories`](#table-of-app-repositories) when building apps other than the *Loop* app
 
 ### Add <code>Secrets</code> to your *GitHub* Organization
 
-Adding the <code>Secrets</code> to an organization is similar to adding them to each <code>repository</code> for a personal *GitHub* account. The difference is you add them at the organization level and then they are available to each <code>repository</code> in that organization.
+You use the same `Secrets` and `Variable` that you have saved in your [Secrets Reference File](intro-summary.md#make-a-secrets-reference-file){: target="_blank" }.
 
-Detailed instructions for using an organization are found at [Configure Secrets](prepare-fork.md#configure-secrets){: target="_blank" }.
+Detailed instructions for adding these to an organization are found at [Configure Secrets](prepare-fork.md#configure-secrets){: target="_blank" }.
 
 The directions below may be sufficient for some.
 
-Make sure you are in the organization for *GitHub*:
-
 * Make sure the URL is `github.com/my-name-org`
 * Click on Settings
 * In the left pane, scroll down to find `Secrets and variables` and click on the dropdown symbol and choose `Actions`
 * At this point, tap on `New organization secret` and add your 6 secrets
 * Then tap on the `Variable` tab and enter your Variable
 
-### Disable Building for Personal *GitHub* account
+### Build with Organization
 
-Once you have your apps building as you expected from the `my-name-org` organization account, you should configure your personal account to stop any automatic building that may be taking place.
+For every build, you will use the repository in your organization account. Your personal account is maintained to give you access to *GitHub* and holds your *GitHub* personal access token.
 
-#### Option 1: Delete `repository`
+If you previously built with your personal account, all the Identifiers and the App are already configured over at *Apple*. You simply Create Certificates and Build the app.
 
-You can delete the DIY repositories from your personal account
+* If this is your first build of an app, then yes - you must do all the steps
+* If this is switching from personal account for building to organization account for building, then you are using your already configured Identifiers and App
+* New certificates must be created because those tie a particular *GitHub* username to the particular *Apple* developer ID and your organization username differs from your personal username
 
-* Pro: You can't get confused about where you should be building
-* Cons:
-    * If you have already generated some customizations there, it is safest to not delete the repository
-    * If you have pull requests open from your personal account, DO NOT DELETE that repository - that would automatically close those open PR
-* Here are the instructions if you decide to delete the repositories
-    * Click on your icon at upper right of *GitHub* browser
-    * Select `Your Repositories`
-    * Notice the github address now says `my-name` instead of `my-name-org`
-    * Select the repository you wish to delete and follow these instructions
-    * [GitHub Docs: Delete a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/deleting-a-repository){: target="_blank" }
+> WARNING - If you have `forks` of DIY apps in your original `my-name` account that are configured to build automatically, you want to disable building and have only the `my-name-org` account be configured for automatic building. Refer to [Disable Building for Personal *GitHub* account](#disable-building-for-personal-github-account).
+
+### Disable Building for Personal *GitHub* account
 
+Once you have your apps building as you expected from the `my-name-org` organization account, you should configure your personal account to stop any automatic building that may be taking place.
 
-#### Option 2: Disable Build Action
+#### Option 1: Disable Build Action
 
 You can disable the build actions from the repositories in your personal account
 
@@ -495,5 +472,20 @@ You can disable the build actions from the repositories in your personal account
     * Select `Your Repositories`
     * Notice the github address now says `my-name` instead of `my-name-org`
     * Select the repository you wish to disable build actions for and follow these instructions
-    * [GitHub Directions to Disable and Enable a Workflow](https://docs.github.com/en/actions/using-workflows/disabling-and-enabling-a-workflow#disabling-a-workflow){: target="_blank" }
     * It is the Build action that kicks off the update and build steps, so simply disabling the one action is sufficient
+        * [GitHub Directions to Disable and Enable a Workflow](https://docs.github.com/en/actions/using-workflows/disabling-and-enabling-a-workflow#disabling-a-workflow){: target="_blank" }
+
+#### Option 2: Delete `repository`
+
+You can delete the DIY repositories from your personal account
+
+* Pro: You can't get confused about where you should be building
+* Cons:
+    * If you have already generated some customizations there, it is safest to not delete the repository
+    * If you have pull requests open from your personal account, DO NOT DELETE that repository - that would automatically close those open PR
+* Here are the instructions if you decide to delete the repositories
+    * Click on your icon at upper right of *GitHub* browser
+    * Select `Your Repositories`
+    * Notice the github address now says `my-name` instead of `my-name-org`
+    * Select the repository you wish to delete and follow these instructions
+    * [GitHub Docs: Delete a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/deleting-a-repository){: target="_blank" }