Skip to content

docs(kdp): document AI Blueprints and AI-generated forms#2227

Open
iammerus wants to merge 5 commits into
mainfrom
docs/kdp-ai-features-735
Open

docs(kdp): document AI Blueprints and AI-generated forms#2227
iammerus wants to merge 5 commits into
mainfrom
docs/kdp-ai-features-735

Conversation

@iammerus

@iammerus iammerus commented Jul 22, 2026

Copy link
Copy Markdown

Documents two KDP AI features under v1.1: AI-assisted blueprint authoring and AI-generated service UI.

  • New AI-Generated Forms page covering the UI Builder and the per-service generateUI first draft.
  • Expanded the Blueprints page with a section on the AI assistant (create, edit, fix with AI).

Screenshots are placeholders for now. I'll drop the images in before marking this ready.

Closes kubermatic/developer-platform#735.

@kubermatic-bot kubermatic-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. labels Jul 22, 2026
@kubermatic-bot

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubermatic-bot kubermatic-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 22, 2026
@kubermatic-bot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ahmadhamzh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@iammerus
iammerus marked this pull request as ready for review July 22, 2026 11:19
Copilot AI review requested due to automatic review settings July 22, 2026 11:19
@kubermatic-bot kubermatic-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 22, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation for two KDP v1.1 AI-assisted authoring features: generating tailored dashboard UIs for services (UI Builder + generateUI) and AI-assisted Blueprint authoring within the dashboard.

Changes:

  • Adds a new “AI-Generated Forms” page describing the UI Builder workflow, spec.generateUI: true, and schema drift/regeneration.
  • Expands the Blueprints documentation with a “Building Blueprints with AI” section covering grounding, modes (Create/Edit/Fix), and safety notes.
  • Cross-links both AI feature pages in their respective “Availability” and “Related topics” sections.

Reviewed changes

Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.

File Description
content/developer-platform/v1.1/service-providers/generated-forms/_index.en.md New page documenting UI Builder usage, async first-draft generation via generateUI, and UI/schema sync behavior.
content/developer-platform/v1.1/service-providers/blueprints/_index.en.md Adds an AI assistant section to Blueprint authoring docs and links to the new AI-Generated Forms page.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@iammerus
iammerus requested a review from mstruebing July 22, 2026 11:26

@mstruebing mstruebing left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In one of my previous companies, where we've had dedicated technical writers for our documentation, there was a rule to never include screenshots as they are a hell to maintain. They will get outdated VERY quickly and it's super super hard to keep track of every place that needs an update and regenerating these updated screenshots is also very hard with the exact same scenarios.

I do not say we shouldn't include screenshots, but we should think about it and make it conscious.

Comment thread content/developer-platform/v1.1/service-providers/blueprints/_index.en.md Outdated
Graph** you can inspect either as a diagram or as the underlying RGD YAML.
The dashboard provides a visual Blueprint builder: a resource-graph editor where you add
services as nodes and wire their fields together, plus an **AI assistant** panel (see
[Building Blueprints with AI](#building-blueprints-with-ai) below). Published Blueprints get a

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should align on releasing it/toggling the feature flag before publishing these docs or mentioning the feature flag.

Comment thread content/developer-platform/v1.1/service-providers/blueprints/_index.en.md Outdated
@@ -0,0 +1,79 @@
+++
title = "AI-Generated Forms"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also have the ability AI generate detail pages.

Comment thread content/developer-platform/v1.1/service-providers/generated-forms/_index.en.md Outdated
@@ -0,0 +1,79 @@
+++
title = "AI-Generated Forms"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably mention in here that this is workspace specific, every workspace can have their own UI for create/detail and even list view (list view is no AI involved though) as well as the service provider can provide defaults.

Service provider can generate a UI -> every consumer workspace will use that unless they create their own.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants