GitLab Account factory docs

docs/2.0/docs/accountfactory/guides/vend-aws-account.md

@@ -1,37 +1,66 @@
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 # Using the Account Factory Workflow
 
-## Introduction
+## Generate the account-request file
 
-The Account Factory Workflow in your `infrastructure-live-root` repository can be used to create new AWS accounts. It requires a single input—a JSON payload—generated from the `account-factory-inputs.html` web page.
+There are currently two ways to generate the account-request file:
 
-The JSON payload approach provides greater flexibility for account vending, overcoming the GitHub workflow restriction of a 10-input maximum.
+1. Using the [Gruntwork Developer Portal](/2.0/docs/accountfactory/guides/vend-aws-account?account-creation-method=ui#using-the-gruntwork-developer-portal) (**GitLab and GitHub non-enterprise customers**)
+2. Using the [Account Factory workflow in your repository](/2.0/docs/accountfactory/guides/vend-aws-account?account-creation-method=workflow#using-the-account-factory-workflow-in-your-repository) (**GitHub only**)
+
+
+<Tabs groupId="account-creation-method" queryString="account-creation-method">
+<TabItem value="ui" label="Using Portal UI">
+
+### Using the Gruntwork Developer Portal
+
+1. Navigate to the [Account Request](https://app.gruntwork.io/account-factory/request-generator) page in the Gruntwork Developer Portal, as an authenticated user, to access the request generator UI.
 
-:::note
+    ![Account Request Generator](/img/accountfactory/dev-portal-request-generator.png)
 
-This guide focuses on non-delegated repositories. Enterprise customers can also [use Account Factory to create new Delegated Repositories](/2.0/docs/accountfactory/guides/delegated-repositories).
+1. If the form is disabled for filling out, request that an Admin in your Gruntwork Developer Account configures the Account factory settings.
+1. Fill out the form with the required information and click on the "Generate Account Request" button.
+1. Use the "Download" button to download the account-request file or the "Copy" button to copy the account-request file to your clipboard.
+1. Navigate to your repository and create a new branch.
+1. Create a new file in the `_new-account-requests` directory by moving the downloaded file to the directory or by creating a new file with the content of your clipboard. If copying content, ensure that the file is created with the correct name displayed in the generator output.
+1. Commit your changes and open a Pull Request to the main branch.
 
+</TabItem>
+<TabItem value="workflow" label="Using Workflow in Repo">
+
+### Using the Account Factory workflow in your repository
+
+:::info
+Only available for GitHub customers. This guide focuses on non-delegated repositories. Enterprise GitHub customers can also [use Account Factory to create new Delegated Repositories](/2.0/docs/accountfactory/guides/delegated-repositories).
 :::
 
+The Account Factory Workflow in your `infrastructure-live-root` repository can be used to create new AWS accounts. It requires a single input—a JSON payload—generated from the `account-factory-inputs.html` web page.
 
-### Step 1 - Download the file
+The JSON payload approach provides greater flexibility for account vending, overcoming the GitHub workflow restriction of a 10-input maximum.
+
+#### Step 1 - Download the file
 
 Locate the inputs web page in your `infrastructure-live-root` repository at `.github/workflows/account-factory-inputs.html` and download it to your local machine.
 
-### Step 2 - Populate the values
+#### Step 2 - Populate the values
 
 Open the downloaded `account-factory-inputs.html` file in a web browser and populate the input fields as required.
 
 Once all values are filled, click "Generate" and copy the resulting JSON output to your clipboard.
 
-### Step 3 - Run the Account Factory workflow
+#### Step 3 - Run the Account Factory workflow
 
 Access the Actions tab in your `infrastructure-live-root` repository on GitHub and select `Account factory` from the left-hand pane.
 
 Click "Run workflow" on the right, paste the generated JSON payload into the dropdown, and click the green "Run workflow" button to initiate the workflow.
+After the workflow is complete, a new Pull Request will be created in the `infrastructure-live-root` repository. This PR will add an account request to the `_new-account-requests` directory.
 
-### Step 4 - Merge the account request PR
+</TabItem>
+</Tabs>
 
-After the workflow is complete, a new Pull Request will be created in the `infrastructure-live-root` repository. This PR will add an account request to the `_new-account-requests` directory.
+## Review and merge the account request PR
 
 Review and merge the Pull Request to begin the account creation process.
 
@@ -43,7 +72,7 @@ Once the account request PR merges into the main branch, Pipelines will initiate
 
 When the account is successfully created, Pipelines will open another Pull Request to baseline the account.
 
-### Step 5 - Merge the Account Baseline PR
+## Review and merge the Account Baseline PR
 
 Review and merge the Account Baseline Pull Request. This PR contains essential infrastructure for enabling your delegated repository to plan and apply infrastructure changes in AWS. It also includes account baselines and configured account-specific infrastructure, such as a VPC.
 

docs/2.0/docs/overview/getting-started/index.md

@@ -19,9 +19,15 @@ Set up authentication for Pipelines to enable secure automation of infrastructur
 
 <PersistentCheckbox id="install-df-3" label="Pipelines Auth Configured" />
 
-### Step 4: [Create new Pipelines repositories](/2.0/docs/pipelines/installation/addingnewrepo)
+### Step 4: Create new Pipelines repositories
 
-Alternatively, you can [add Pipelines to an existing repository](/2.0/docs/pipelines/installation/addingexistingrepo).
+- [New GitHub repository](/2.0/docs/pipelines/installation/addingnewrepo)
+- [New GitLab repository](/2.0/docs/pipelines/installation/addingnewgitlabrepo)
+
+Alternatively, you can add Pipelines to an existing repository:
+
+- [Existing GitHub repository](/2.0/docs/pipelines/installation/addingexistingrepo)
+- [Existing GitLab repository](/2.0/docs/pipelines/installation/addinggitlabrepo)
 
 <PersistentCheckbox id="install-df-4" label="Pipelines Repositories Ready" />
 

docs/2.0/docs/pipelines/installation/addinggitlabrepo.md

@@ -1,6 +1,6 @@
 import CustomizableValue from '/src/components/CustomizableValue';
 
-# Adding Pipelines to a GitLab Project
+# Adding Pipelines to an existing GitLab Project
 
 This guide walks you through the process of adding Gruntwork Pipelines to a GitLab project. By the end, you'll have a fully configured GitLab CI/CD pipeline that can deploy infrastructure changes automatically.
 
@@ -11,7 +11,7 @@ Before you begin, make sure you have:
 - Basic familiarity with Git, GitLab, and infrastructure as code concepts
 - Access to one (or many) AWS account(s) where you have permission to create IAM roles and OIDC providers
 - Completed the [Pipelines Auth setup for GitLab](/2.0/docs/pipelines/installation/viamachineusers#gitlab) and setup a machine user with appropriate PAT tokens
-- Local access to Gruntwork's GitHub repositories, specifically [boilerplate](https://github.com/gruntwork-io/boilerplate) and the [architecture catalog](https://github.com/gruntwork-io/terraform-aws-architecture-catalog/)
+- Local access to Gruntwork's GitHub repositories, specifically the [architecture catalog](https://github.com/gruntwork-io/terraform-aws-architecture-catalog/)
 
 :::info