Merge branch 'main' into PORT-16432-bug-add-documentation-for-aws-integration-live-events

Author: sivanel97

.cursor/rules/documentation_style.mdc

@@ -2,5 +2,4 @@
 description: 
 globs: 
 alwaysApply: false
----
- 
+---

.github/workflows/verify-docs-build.yml

@@ -22,7 +22,7 @@ jobs:
         with:
           persist-credentials: true
       - name: Install dependencies
-        uses: actions/setup-node@v5
+        uses: actions/setup-node@v6
         with:
           node-version: lts/*
           cache: npm

babel.config.js

@@ -1,14 +1,6 @@
-# Contributing to Port's documentation
+# Port documentation style guide
 
-Here you can find resources and guidelines on how to contribute to Port's documentation and how to correctly write and fix documentation content.
-
-## How to contribute
-
-The best way to suggest edits for an existing page is by using the "Edit this page" button at the bottom of most docs, this button will take you to the GitHub interface to make and propose changes.
-
-If you want to add a new documentation page, please fork the repository and after adding the new docs, create a PR which will be reviewed by our team.
-
-Contributions are very welcome. If you need help planning your contribution, feel free to ask us by opening an issue in this repository or by writing in our [community Slack](https://join.slack.com/t/getport/shared_invite/zt-1v5z1z1v-3~1Q1Q1).
+This document details guidelines for contributing to Port's documentation, and demonstrates how to correctly write and review documentation content.
 
 ## Styling guidelines
 

CONTRIBUTING.md renamed to best_practices.md

@@ -5,13 +5,12 @@ import PortTooltip from "/src/components/tooltip/tooltip.jsx"
 One of Port's core offerings is the ability to automate and simplify the processes and routines of your developers.  
 This is done using two powerful tools:
 
-## 1. Self-service actions
+## 1. Actions
 
-Create a wide range of personalized, controlled actions that developers can use to scaffold a service, provision a cloud resource, or any other logic that serves your organization.  
-Self-service actions drive developer productivity by providing a consistent and repeatable way to perform common tasks, all with guardrails like manual approvals or consumption policies to comply with organizational standards.
+Actions are executable pieces of logic that developers or AI agents can run. You can create a wide range of personalized, controlled actions to scaffold a service, provision a cloud resource, or any other logic that serves your organization. Actions drive developer productivity by providing a consistent and repeatable way to perform common tasks, all with guardrails like manual approvals or consumption policies to comply with organizational standards.
 
 :::tip Live demo
-For real-world examples of self-service actions, check out our [live demo](https://demo.getport.io/self-serve).
+For real-world examples of self-service actions, check out our [live demo](https://showcase.port.io/self-serve).
 :::
 
 For more information and instructions for creating self-service actions, click [here](/actions-and-automations/create-self-service-experiences).

docs/actions-and-automations/actions-and-automations.md

@@ -1,4 +1,4 @@
 {
-  "label": "Create self-service actions",
+  "label": "Create actions",
   "position": 1
 }

docs/actions-and-automations/create-self-service-experiences/_category_.json

@@ -14,7 +14,9 @@ import ExecuteActionLocations from '/docs/actions-and-automations/create-self-se
 </center>
 <br/>
 
-Drive developer productivity by allowing developers to use self-service actions like scaffolding a service or provisioning a cloud resource. Developer self-service drives consistency and repeatability and ensures that their routines are intuitive and clear, all with guardrails like manual approvals or consumption policies to comply with organizational standards.
+Actions are executable pieces of logic that either developers or AI agents can run. They drive developer productivity by enabling them to use actions like scaffolding a service or provisioning a cloud resource.  
+
+Actions drive consistency and repeatability and ensure that routines are intuitive and clear, all with guardrails like manual approvals or consumption policies to comply with organizational standards.
 
 Port's action model is designed to be flexible and can be used to cover a wide range of use-cases:
 
@@ -24,7 +26,7 @@ Port's action model is designed to be flexible and can be used to cover a wide r
 4. **Stateful** - every invoked action affects the software catalog by adding/modifying/deleting one or more entities.
 5. **Secure by design** - does not require keys to sensitive infrastructure by using an event-based model. All actions are audited and can include guardrails like manual approval and TTL.
 
-## 💡 Common self-service actions
+## Common self-service actions
 
 - [**Scaffold** a new service](https://docs.port.io/guides/all/scaffold-a-new-service/).
 - [**Create** a cloud resource](https://docs.port.io/guides/all/create-cloud-resource-using-iac).
@@ -33,11 +35,11 @@ Port's action model is designed to be flexible and can be used to cover a wide r
 - **Rollback** a running service.
 - **Change** a deployment's replica count.
 
-In our [live demo](https://demo.getport.io/self-serve), you can see examples for self-service experiences. 🎬
+In our [live demo](https://showcase.port.io/self-serve), you can see examples for self-service experiences. 🎬
 
 ## How does it work?
 
-1. A user **executes an action** from Port's UI interface.
+1. A user or AI agent **executes an action** from Port's UI interface or through API calls.
 2. A pre-defined **payload** containing any desired metadata about the action and its inputs is **sent** to your infrastructure.
 3. A **job is triggered** and the user gets a **continuous indication** about its progress.
 4. Once the action is running, you can use Port's API to **update Port on its status** and provide information such as **logs and links to the resulting handlers**.

docs/actions-and-automations/create-self-service-experiences/create-self-service-experiences.md

@@ -233,9 +233,13 @@ values={[
 
 <TabItem value="visible">
 
-The `visible` property is used to dynamically hide/show inputs in the form.
+The `visible` property is used to dynamically hide/show elements in the form.
 The `visible` value could be set to either a boolean (`true` value is always shown, `false` value is always hidden), or to a `jqQuery` which evaluates to a boolean.
 
+<h4>Input-level visibility</h4>
+
+You can apply `visible` to individual inputs to control their display:
+
 In this example, the `runArguments` properties are configured with `visible` so that they only show up in the form when the matching value is selected in the `language` input:
 
 <Tabs
@@ -318,6 +322,59 @@ action = Action(
 
 </Tabs>
 
+<h4>Step-level visibility</h4>
+
+You can also apply `visible` to entire steps to control their display:
+
+In this example, the `AWS Configuration` and `Azure Configuration` steps are conditionally shown based on the values selected in the first step's cloud provider input:
+
+<Tabs
+defaultValue="api"
+values={[
+{label: 'API', value: 'api'}
+]}>
+
+<TabItem value="api">
+
+```json showLineNumbers
+  {
+    "userInputs": {
+      "properties": {
+        "enum": {
+          "icon": "DefaultProperty",
+          "title": "Cloud provider",
+          "type": "array",
+          "items": {
+            "enum": [ "aws", "azure" ],
+            "enumColors": { "aws": "red", "azure": "blue" },
+            "type": "string"
+          }
+        }
+      },
+      "required": [],
+      "steps": [
+        {
+          "title": "Cloud selection",
+          "order": [ "enum" ]
+        },
+        {
+          "title": "AWS configuration",
+          "order": [],
+          "visible": { "jqQuery": ".form.enum | index(\"aws\") != null" }
+        },
+        {
+          "title": "Azure configuration",
+          "order": [],
+          "visible": { "jqQuery": ".form.enum | index(\"azure\") != null" }
+        }
+      ]
+    }
+  }
+```
+</TabItem>
+
+</Tabs>
+
 </TabItem>
 
 <TabItem value="dependsOn">

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/advanced-form-configurations.md

@@ -21,7 +21,7 @@ The entity input type can be used to reference any existing entity from the soft
 - Clusters
 - Configurations
 
-In the [live demo](https://demo.getport.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `Domain` input is an entity input. 🎬
+In the [live demo](https://showcase.port.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `Domain` input is an entity input. 🎬
 
 ## Sorting entities
 

docs/actions-and-automations/create-self-service-experiences/setup-ui-for-action/user-inputs/entity.md

@@ -21,7 +21,7 @@ The number input type can be used to store any numeric data, for example:
 - Replica counts
 - Number of days to retain data
 
-In the [live demo](https://demo.getport.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `K8s Replica Count` input is a number input. 🎬
+In the [live demo](https://showcase.port.io/self-serve) self-service hub page, we can see the **scaffold new service** action whose `K8s Replica Count` input is a number input. 🎬
 
 ## API definition