Reorganize interactive-computing docs

index.md

@@ -71,6 +71,7 @@ services/technical-support/index
 services/community-success-hours/index
 services/open-source-development/index
 services/delivery/index
+services/incidents/index
 List of running hubs <https://infrastructure.2i2c.org/reference/hubs/>
 ```
 

services/interactive-computing/community-information.md

@@ -0,0 +1,27 @@
+# Community Information
+
+BD fills in the following fields in the *Community* tab on a Deal in HubSpot:
+
+Propery Label | Description
+-- | --
+Community Name | one word, will be used to create an machine-readable identifier for naming clusters, accounts, database keys, and other infrastructure internal to 2i2c
+Community Long Name | Community Long Name (Long version, full formal name, for display on in public facing webpages )
+Community Website | Community's Website URL
+Community GitHub Organization  | Community's GitHub organization URL
+Community Logo | Community's Logo URL
+Community Representatives  | List of individual able to authorizes changes on behalf of this community
+Community Context | Notes on community goals and technical contraints
+
+These fields may be already known or discoverable during the sales process. This information is used downstream by the P&S team to accelerate the deployment of infrastructure on behalf of a community.
+
+Under 'Community Context', here is information that is useful:
+
+> Community Context questions: (use Markdown formatting)
+>
+> - Q: What do you want to achieve by working with 2i2c? Can you paint me a picture that describes the future you wish to materialize?(i.e. Do they have an existing image / environment they want us to use? )
+>
+> - Q: Can you describe this research community more? Is it segmented? Are there archetypes or personas? (i.e. How will users authenticate? If GitHub which GitHub Org or Teams? GitHub IDs of admins?)
+>
+> - Q: At a high level, what is your community trying to achieve and how open data/compute infrastructure will help advance toward your mission/vision? (i.e. Do they want GPUs? If so, what GitHub team should have access to GPUs? What's the maximum amount of RAM they want users to be able to spin up on the hub?  Default: 30G, generate with deployer generate resource-allocation choices r5.xlarge:4)
+>
+> - Q: Can you describe the data? Collaborating open science communities orbit around the heaviest objects in their science space -- their data. Where is it? (i.e. Do they have existing data in some cloud region or zone? Our default is AWS: us-west-2)

services/interactive-computing/hub-rollout-process.md

@@ -1,9 +1,5 @@
 # Hub Rollout Process
 
-Our interactive computing hubs are an opportunity for the Product & Services (PS) team to work directly with communities. Our expertise at 2i2c is solving *XY problems* — matching infrastructure and open source tooling to the needs of education and research communities. To do this well, we need a repeatable process for how PS engineers and BD interact with communities when deploying a hub.
-
-## Process Overview
-
 The hub rollout process is a collaboration between **Business Development (BD)** and **Product & Services (PS)**. BD bookends the process — identifying communities and tracking long-term value — while PS leads the technical engagement from sales engineering through validation.
 
 ```{mermaid}
@@ -42,11 +38,3 @@ flowchart
     style G fill:#50c878,color:#fff,stroke:#308050
     style BD3 fill:#3a7bc8,color:#fff,stroke:#2c5f8a
 ```
-
-## Step Guides
-
-Detailed documentation for each PS-led step:
-
-- **[Sales Engineer Guide](sales-engineer-guide.md)** — Step 2. What a PS engineer does in the sales call: listening to community needs, gathering technical context, and solving XY problems.
-- **[Needs Assessment Guide](needs-assessment-guide.md)** — Steps 4–5. Confirming requirements with the community and writing the GitHub issue with a technical plan and subtasks.
-- **[Validation Guide](validation-guide.md)** — Step 7. Verifying that community representatives and at least 5 users can log in and use the hub, and deciding whether the rollout is complete.

services/interactive-computing/index.md

@@ -8,19 +8,31 @@ The Managed Interactive Computing Service (MICS) is a service to **sustain and s
 **Communities Representatives: [`docs.2i2c.org`](https://docs.2i2c.org) has the information about how to use 2i2c interactive computing hubs.**.
 :::
 
+## Hub Rollout Process
+
+Our interactive computing hubs are an opportunity for the Product & Services (PS) team to work directly with communities. Our expertise at 2i2c is solving *XY problems* — matching infrastructure and open source tooling to the needs of education and research communities. To do this well, we need a repeatable process for how PS engineers and BD interact with communities when deploying a hub.
+
+See the **[Hub Rollout Process](hub-rollout-process.md)** for the overall 9-step process showing how BD and PS collaborate from identifying a community through to value delivery.
+
+### Step Guides
+
+Detailed documentation for each PS-led step:
+
+- **[Sales Engineer Guide](sales-engineer-guide.md)** — Step 2. What a PS engineer does in the sales call: listening to community needs, gathering technical context, and solving XY problems.
+- **[Needs Assessment Guide](needs-assessment-guide.md)** — Steps 4–5. Confirming requirements with the community and writing the GitHub issue with a technical plan and subtasks.
+- **[Validation Guide](validation-guide.md)** — Step 7. Verifying that community representatives and at least 5 users can log in and use the hub, and deciding whether the rollout is complete.
+
 ```{toctree}
 hub-rollout-process
 sales-engineer-guide
 needs-assessment-guide
 validation-guide
-onboard
+community-information
 offboard
 community-value
 communicating-changes
 multiple-hub-upgrades
 addhub
 clusters
-budget-alerts
 showcase-hub
-incidents/index
 ```

services/technical-support/index.md

@@ -21,5 +21,6 @@ update-contacts
 timeboxed-initial-ticket-evaluation
 communication
 time-off
+budget-alerts
 templates/index
 ```