Repo-wide lint cleanup: redirects, frontmatter, alt text, dead URLs

src/pages/get_started/app_builder_get_started/ai-development-tools.md

@@ -165,7 +165,7 @@ AI assistants generate better code when they understand your project structure.
 - Use current API versions (Workfront v21.0, AEM OpenAPI)
 
 ## Documentation
-- App Builder and Runtime: https://developer.adobe.com/app-builder/docs/
+- App Builder and Runtime: https://developer.adobe.com/app-builder/docs/intro_and_overview/
 ```
 
 **For Cursor**, point to the [App Builder skills folder](https://github.com/adobe/skills) as described in the setup section above.
@@ -188,7 +188,7 @@ All formats serve the same purpose: giving the AI assistant context about App Bu
 
 ## Resources
 
-- [App Builder Documentation](https://developer.adobe.com/app-builder/docs/)
+- [App Builder Documentation](https://developer.adobe.com/app-builder/docs/intro_and_overview/)
 - [App Builder Adobe Summit Session: Build Fast, Secure AI-Powered Integrations with Adobe App Builder - OS605](https://business.adobe.com/summit/2026/sessions/build-fast-secure-aipowered-integrations-with-adob-os605.html)
 - [AEM AI Coding Agents Guide](https://www.aem.live/developer/ai-coding-agents)
 - [MCP Server Generator](https://github.com/adobe/generator-app-remote-mcp-server-generic)

src/pages/get_started/app_builder_get_started/app-builder-intro.md

@@ -5,6 +5,7 @@ keywords:
   - API Documentation
   - Developer Tooling
 title: How it Works
+description: 'Overview of how App Builder works and what you''ll learn in the get-started tutorial series.'
 ---
 
 # Get Started with App Builder

src/pages/get_started/app_builder_get_started/first-app.md

@@ -5,6 +5,7 @@ keywords:
   - API Documentation
   - Developer Tooling
 title: Creating your First App Builder Application
+description: 'Step-by-step guide to creating, configuring, and deploying your first App Builder application.'
 ---
 
 # Create your First App Builder Application
@@ -66,7 +67,7 @@ Follow these instructions to set up your project:
 
     ![Workspace](../../images/console-6.png)
 
-To learn more about Adobe Developer Console, please refer to [Console Documentation](https://developer.adobe.com/developer-console/docs).
+To learn more about Adobe Developer Console, please refer to [Console Documentation](https://developer.adobe.com/developer-console/docs/guides/).
 
 ## 3. Sign in from the CLI
 
@@ -241,9 +242,9 @@ You may not see all the options listed below on your command line, because they
 
 - **Adobe Target**, including dependencies and examples of accessing the [Adobe Target API](https://developers.adobetarget.com/api/#admin-apis)
 - **Adobe Analytics**, including dependencies and examples of accessing the [Adobe Analytics 2.0 API](https://adobedocs.github.io/analytics-2.0-apis/)
-- **Adobe Audience Manager: Customer Data**, including dependencies and examples of accessing the [Adobe Audience Manager Customer Data API](https://docs.adobe.com/content/help/en/audience-manager/user-guide/api-and-sdk-code/api.html)
-- **Adobe Campaign Standard**, including dependencies and examples of accessing the [Adobe Campaign Standard (ACS) API](https://docs.adobe.com/content/help/en/campaign-standard/using/working-with-apis/get-started-apis.html)
-- **Adobe Experience Platform: Realtime Customer Profile**, including dependencies and examples of accessing the [Realtime Customer Profile API of Adobe Experience Platform](https://developer.adobe.com/experience-platform-apis/references/profile/)
+- **Adobe Audience Manager: Customer Data**, including dependencies and examples of accessing the [Adobe Audience Manager Customer Data API](https://experienceleague.adobe.com/en/docs/audience-manager/user-guide/api-and-sdk-code/api)
+- **Adobe Campaign Standard**, including dependencies and examples of accessing the [Adobe Campaign Standard (ACS) API](https://experienceleague.adobe.com/en/docs/campaign-standard/using/working-with-apis/get-started-apis)
+- **Adobe Experience Platform: Realtime Customer Profile**, including dependencies and examples of accessing the [Realtime Customer Profile API of Adobe Experience Platform](https://developer.adobe.com/experience-platform-apis/references/profile)
 - **Generic**, a generic back-end action with hello-world flow that can be reused and modified, for simple serverless computing, third-party API integration, and more
 
 If you included `Web Assets` under Adobe I/O App features above, you will be given the choice to include the React Spectrum-based UI template or a raw HTML/JS UI template:
@@ -256,7 +257,7 @@ If you included `Web Assets` under Adobe I/O App features above, you will be giv
 
 - The `React Spectrum 3 UI` template adds a React-based UI with [React Spectrum](https://react-spectrum.adobe.com/) components included
 
-- The `Raw HTML/JS UI` will add a raw HTML/JS/CSS UI with [Spectrum CSS](https://opensource.adobe.com/spectrum-css) styles included.
+- The `Raw HTML/JS UI` will add a raw HTML/JS/CSS UI with [Spectrum CSS](https://opensource.adobe.com/spectrum-css/) styles included.
 
   Both templates come with boilerplate code needed to integrate your App Builder application with [Adobe Experience Cloud](../../guides/app_builder_guides/exc_app/aec-integration.md)
 

src/pages/get_started/app_builder_get_started/index.md

@@ -5,6 +5,7 @@ keywords:
   - API Documentation
   - Developer Tooling
 title: App Builder and Adobe I/O Runtime
+description: 'Introduction to App Builder and Adobe I/O Runtime for building cloud-native applications on Adobe infrastructure.'
 ---
 
 # App Builder and Adobe I/O Runtime

src/pages/get_started/app_builder_get_started/publish-app.md

@@ -5,6 +5,7 @@ keywords:
   - API Documentation
   - Developer Tooling
 title: Publishing Your First App Builder Application
+description: 'How to submit, review, and publish App Builder SPAs through Developer Console, Adobe Exchange, and Adobe Experience Cloud.'
 ---
 
 # Publishing Your First App Builder Application
@@ -29,53 +30,53 @@ The final app is based on the Production workspace, so it is important to make s
 
 To begin the approval process, navigate to the Production workspace and select **Submit for approval** in the top-right corner of the screen or **Approval** in the left navigation.
 
-![](../../images/approval-production-overview.png)
+![Approval screen in the Production workspace](../../images/approval-production-overview.png)
 
 On the Approval screen you will be able to fill out the **App Submission Details** form.
 
 These details will be visible to people who use your app and administrators who review your application. Once the form is completed, select **Submit** to begin the approval process.
 
-![](../../images/approval-app-submission-details.png)
+![App submission details form](../../images/approval-app-submission-details.png)
 
 You will be returned to the Approval screen, where the Status of your application should now be "In Review."
 
-![](../../images/approval-in-review.png)
+![Approval screen showing application status In Review](../../images/approval-in-review.png)
 
 Following a review by your organization administrators, your application will either be approved and published, or rejected. If it is rejected, your Admin will be able to include a note telling you what went wrong so you can fix the error and resubmit.
 
-![](../../images/approval-app-rejected.png)
+![Approval screen showing a rejected application](../../images/approval-app-rejected.png)
 
 ### Published app
 
 Once your application has been submitted for approval, the Admin can see it pending for review in Adobe Exchange. The next section will describe Admin approval flow from Adobe Exchange. From Console side, once an application has been approved, its Status will be updated to Published and the application will be available for use by employees within your enterprise organization.
 
-![](../../images/approval-published.png)
+![Approval screen showing a published application](../../images/approval-published.png)
 
 ## Administrator review of your app from Adobe Exchange
 
 After you submit an application for approval, your organization's administrators can find it in Adobe Exchange under Manage → App Builder applications → Private distribution. Your submitted application will appear with a Pending Review status.
 
-![](../../images/approval-myexchange.png)
+![Pending Review listing in Adobe Exchange private distribution](../../images/approval-myexchange.png)
 
 The reviewer can review this app and approve it or reject it. If the application is rejected, your admin will be able to include a note telling you what went wrong, so you can fix the error and resubmit.
 
-![](../../images/approval-myexchange-review.png)
+![Adobe Exchange app review screen for an administrator](../../images/approval-myexchange-review.png)
 
 After the application is approved, the reviewer can also unpublish the app, requiring the app owner to resubmit it for review and approval.
 
-![](../../images/approval-myexchange-revoke.png)
+![Adobe Exchange unpublish action for an approved application](../../images/approval-myexchange-revoke.png)
 
 ## Check your published app at Experience Cloud
 
 Once the reviewer has approved your application, you will be notified by email and your app will appear at Adobe Experience Cloud:
 
-![](../../images/approval-myapp-home.png)
+![Approved app on the Adobe Experience Cloud home page](../../images/approval-myapp-home.png)
 
 Click on `App Builder Apps` to discover all the applications published for your organization.
 
-![](../../images/approval-myapp-customapps.png)
+![App Builder Apps list in Adobe Experience Cloud](../../images/approval-myapp-customapps.png)
 
-# Publishing your headless App Builder app
+## Publishing your headless App Builder app
 
 The `App Builder Apps` Adobe Experience Cloud lists only App Builder SPAs. If you publish a headless app, please refer to our Code Lab [Headless Apps with App Builder](../../resources/barcode-reader/index.md).
 

src/pages/get_started/app_builder_get_started/set-up.md

@@ -5,7 +5,7 @@ keywords:
   - Local Environment
   - Set up
 title: Set Up Access, Environment, and Tools
-description: App Builder is a complete framework that enables enterprise developers to build and deploy custom web applications that extend Adobe Experience Cloud solutions and run on Adobe infrastructure.
+description: Get the access, credentials, and local tooling you need to start building App Builder applications.
 ---
 
 # Set Up Access, Environment, and Tools
@@ -22,7 +22,7 @@ Here you'll learn what systems you need to access, how to access them, and how t
 
   - Customers should request access from their account manager or their company IT/Marketing admin
 
-  - Partners should request App Builder access from their partner manager, or Sandbox access though the [Adobe Solution Partner Portal](https://solutionpartners.adobe.com/home.html)
+  - Partners should request App Builder access from their partner manager, or Sandbox access though the [Adobe Solution Partner Portal](https://partners.adobe.com/digitalexperience/)
 
 **App Builder access** is only available with a purchased license. 
 

src/pages/get_started/app_builder_get_started/troubleshoot.md

@@ -5,6 +5,7 @@ keywords:
   - API Documentation
   - Developer Tooling
 title: Troubleshooting Common Issues
+description: 'Troubleshooting guide for the most common issues encountered while developing App Builder applications.'
 ---
 
 # Troubleshooting Common Issues

src/pages/get_started/index.md

@@ -1,3 +1,13 @@
+---
+keywords:
+  - Adobe I/O
+  - App Builder
+  - Getting Started
+  - Runtime
+title: 'Getting Started with App Builder'
+description: 'Choose between the App Builder and Runtime getting-started paths and explore the rest of the App Builder documentation.'
+---
+
 # Getting Started with App Builder
 
 Welcome to the Getting Started section of App Builder documentation. Here you'll find comprehensive guides to help you start working with App Builder and Adobe I/O Runtime.

src/pages/get_started/runtime_getting_started/activations.md

@@ -1,3 +1,13 @@
+---
+keywords:
+  - Adobe I/O
+  - Runtime
+  - Activations
+  - OpenWhisk
+title: 'Retrieve Action Invocation Results'
+description: 'Use aio rt:activation commands to list and retrieve invocation records, logs, and responses for Adobe I/O Runtime actions.'
+---
+
 # Retrieve Action Invocation Results
 
 The activation record of an action invocation contains information to help you understand what happened. It contains the invocation's: 

src/pages/get_started/runtime_getting_started/deploy.md

@@ -1,3 +1,13 @@
+---
+keywords:
+  - Adobe I/O
+  - Runtime
+  - Actions
+  - Deploy
+title: 'Deploy Your First Adobe I/O Runtime Action'
+description: 'Create, deploy, and test your first Adobe I/O Runtime action using the aio CLI.'
+---
+
 # Deploy Your First Adobe I/O Runtime Action
 
 In this step, you will create an I/O Runtime action, test it, and deploy it. 

src/pages/get_started/runtime_getting_started/entities.md

@@ -1,3 +1,16 @@
+---
+keywords:
+  - Adobe I/O
+  - Runtime
+  - Actions
+  - Namespaces
+  - Triggers
+  - Rules
+  - Packages
+title: 'Entities and Core Concepts'
+description: 'Glossary of Adobe I/O Runtime entities including actions, namespaces, triggers, rules, packages, sequences, and feeds.'
+---
+
 # Entities and Core Concepts
 
 Adobe I/O Runtime's computing model is composed of functional elements or entities, and the interactions among them. This glossary defines the most important entities, outlines their interactions, and links to relevant resources in the Guides and elsewhere in this documentation.

src/pages/get_started/runtime_getting_started/how-runtime-works.md

@@ -1,14 +1,18 @@
-```yaml
+---
 keywords:
-  - [need keywords]
-title: How I/O Runtime works
-```
+  - Adobe I/O
+  - Runtime
+  - OpenWhisk
+  - Architecture
+title: 'How I/O Runtime works'
+description: 'How Adobe I/O Runtime uses the Apache OpenWhisk architecture to provide function-as-a-service execution.'
+---
 
 # How Adobe I/O Runtime Works
 
 Adobe I/O Runtime is based on the open source Apache OpenWhisk platform, and uses the OpenWhisk architecture to provide function-as-a-service. Here is a high-level look at the architecture:
 
-![The OpenWhisk architecture](https://developer.adobe.com/runtime/docs/static/2f65d806954291bfd2a474f3c8b2f9f4/73c8b/howitworks_f01.png)
+![The OpenWhisk architecture](../../images/howitworks_f01.png)
 
 The figure shows how Runtime (via OpenWhisk) is set up to respond to events and direct invocations. Whether the event comes from an external or internal source, it is associated with a trigger, which invokes an action according to any rules that are applied. Actions can also be invoked directly through the Runtime (OpenWhisk) CLI or the REST API.
 
@@ -54,13 +58,13 @@ Host: $openwhiskEndpoint
 
 Note the `$userNamespace` variable. Runtime requests require access to the same namespace in which the action was created. When users are configured for Runtime accounts, they are given their own personal namespaces. 
 
-![](../../images/howitworks_f02.png)
+![Diagram of the Runtime internal process flow](../../images/howitworks_f02.png)
 
 *Internal process flow*
 
 #### Receiving: nginx
 
-[Nginx](https://www.nginx.com/) is a reverse proxy and HTTP server. The OpenWhisk architecture uses it to terminal SSL and forward the HTTP request to the next component in the processing loop.
+[Nginx](https://www.f5.com/products/nginx) is a reverse proxy and HTTP server. The OpenWhisk architecture uses it to terminal SSL and forward the HTTP request to the next component in the processing loop.
 
 #### Interpreting: the Controller
 

src/pages/get_started/runtime_getting_started/index.md

@@ -1,3 +1,13 @@
+---
+keywords:
+  - Adobe I/O
+  - Runtime
+  - Getting Started
+  - Serverless
+title: 'Get Started with Adobe I/O Runtime'
+description: 'Introduction to Adobe I/O Runtime, the serverless computing platform that powers App Builder applications.'
+---
+
 # Get Started with Adobe I/O Runtime
 
 Adobe I/O Runtime is Adobe’s serverless computing platform based on Apache OpenWhisk, an open-source project of the Apache Software Foundation. Runtime lets you deploy your own custom code to the cloud and call it as needed, so you can execute functions, also called "actions," from the cloud without deploying or configuring a server. 

src/pages/get_started/runtime_getting_started/resources.md

@@ -1,3 +1,14 @@
+---
+keywords:
+  - Adobe I/O
+  - Runtime
+  - OpenWhisk
+  - Resources
+  - Support
+title: 'Resources and support'
+description: 'Resources, social media accounts, and community support channels for Adobe I/O Runtime developers.'
+---
+
 <HeroSimple slots="heading, text" />
 
 # Resources and support
@@ -6,11 +17,11 @@ Adobe I/O Runtime is built on top of Apache OpenWhisk, so blogs, documentation,
 
 ## Resources
 
-A good starting point is the [Apache OpenWhisk repository](https://github.com/apache/incubator-openwhisk/tree/master/docs).
+A good starting point is the [Apache OpenWhisk repository](https://github.com/apache/openwhisk/tree/master/docs).
 
 ## Social media
 
-You can follow our team on [Twitter](https://twitter.com/adobeio), [Medium](https://medium.com/adobetech/tagged/platform), and [Youtube](https://www.youtube.com/channel/UCDtYqOjS9Eq9gacLcbMwhhQ).
+You can follow our team on [Twitter](https://x.com/adobeio), [Medium](https://medium.com/adobetech/tagged/platform), and [Youtube](https://www.youtube.com/channel/UCDtYqOjS9Eq9gacLcbMwhhQ).
 
 ## Support
 

src/pages/get_started/runtime_getting_started/setup.md

@@ -1,3 +1,14 @@
+---
+keywords:
+  - Adobe I/O
+  - Runtime
+  - Setup
+  - CLI
+  - Namespace
+title: 'Set up Your Environment'
+description: 'Install the aio CLI, create a Developer Console namespace, and sign in to start using Adobe I/O Runtime.'
+---
+
 # Set up Your Environment
 
 ## Get access

src/pages/get_started/runtime_getting_started/understanding-runtime.md

@@ -1,3 +1,13 @@
+---
+keywords:
+  - Adobe I/O
+  - Runtime
+  - Programming Model
+  - OpenWhisk
+title: 'Understanding Adobe I/O Runtime'
+description: 'Programming model, components, and architecture of Adobe I/O Runtime, the serverless platform that powers App Builder.'
+---
+
 # Understanding Adobe I/O Runtime
 
 Serverless platforms greatly simplify the development and operation of business applications. Successful use of them takes advantage of their many strengths, while working around their limitations. This Quick Start Guide explores the most critical of these considerations as they apply to I/O Runtime.
@@ -12,19 +22,19 @@ Actions may be invoked by HTTP calls (RESTful or HTTP) or by other actions. Acti
 
 Actions may be organized into any number of **packages** within a namespace. Packages are used to organize the code, manage different versions of the same action, or share code with other tenants or applications. Packages marked **shareable** may be bound to the namespaces of anyone who has their full name, in the manner of symbolic links.
 
-![](../../images/quickstart-programming-model.png)
+![Diagram of the Runtime programming model with actions, namespaces, and packages](../../images/quickstart-programming-model.png)
 
-![](../../images/quickstart-shared-packages.png)
+![Diagram showing how shareable packages bind to other namespaces](../../images/quickstart-shared-packages.png)
 
 Actions may be invoked anonymously - with no authorization required - or with authentication. Runtime supports basic authorization  Developers can implement their own auth. We will be adding support for IMS based auth.
 
 ## Understanding I/O Runtime components
 
-Adobe I/O Runtime is built on the Apache OpenWhisk open-source project, so many resources written for Apache OpenWhisk also apply to Adobe I/O Runtime. The [Apache OpenWhisk repository](https://github.com/apache/incubator-openwhisk/tree/master/docs) is a useful resource.
+Adobe I/O Runtime is built on the Apache OpenWhisk open-source project, so many resources written for Apache OpenWhisk also apply to Adobe I/O Runtime. The [Apache OpenWhisk repository](https://github.com/apache/openwhisk/tree/master/docs) is a useful resource.
 
 This diagram shows the high-level architecture of I/O Runtime built on OpenWhisk:
 
-![](../../images/quickstart-components.png)
+![High-level Runtime architecture diagram built on OpenWhisk](../../images/quickstart-components.png)
 
 This is the sequence by which Runtime components execute user code when an action is executed:
 
@@ -144,7 +154,7 @@ This is just the beginning for Adobe I/O Runtime. We encourage you to help us en
 
 ### Social media
 
-You can follow the Adobe I/O team on [Twitter](https://twitter.com/adobeio), [Medium](https://medium.com/adobetech/tagged/platform), and [Youtube](https://www.youtube.com/channel/UCDtYqOjS9Eq9gacLcbMwhhQ).
+You can follow the Adobe I/O team on [Twitter](https://x.com/adobeio), [Medium](https://medium.com/adobetech/tagged/platform), and [Youtube](https://www.youtube.com/channel/UCDtYqOjS9Eq9gacLcbMwhhQ).
 
 ### Support
 

src/pages/guides/app_builder_guides/application-state.md

@@ -5,6 +5,7 @@ keywords:
 - API Documentation
 - Developer Tooling
 title: Storage Options
+description: 'Compare Database, Files, and State storage services available out-of-the-box for persisting App Builder application data.'
 ---