Skip to content

feat(catalog): Revamp - #6586

Draft
cloudjumpercat wants to merge 4 commits into
mainfrom
feat/catalog-revamp
Draft

feat(catalog): Revamp#6586
cloudjumpercat wants to merge 4 commits into
mainfrom
feat/catalog-revamp

Conversation

@cloudjumpercat

@cloudjumpercat cloudjumpercat commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Description

Fixes #5413

TODO:

  • app/_landing_pages/catalog.yaml: FAQ about migration, banner currently renders weird don't use the include and create a separate one for just this page that is text that is all a link similar to /dev-portal.yaml
  • app/_landing_pages/catalog-classic.yaml: probably also needs the same fix for the note as the other landing page.
  • app/_landing_pages/catalog.yaml: and app/_landing_pages/catalog-classic.yaml: FAQ that's an include about the difference between classic and new catalog with a link to the migraiton content
  • all the classic pages will need their breadcrumbs and permalinks looked at. Ex. the GitHub integration one is using /catalog/ in the breadcrumbs and that should probably be /catalog-classic/, which also means I think that we're going to need redirects.
  • _indices/catalog.yaml: the Classic pages should be moved to their own Classic section but retain the subsections that they are currently in (ex. Services and scorecards will move to the Classic section), also be sure to add the Classic landing page
  • app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-ui.md check this one
  • new UI means we have to change some things as MCP registries is included in this release
  • complete AI Models page https://docs.google.com/document/d/1W17b_7OJTsEnw_FoYVun2JOk55ipYlwl4vyHRYfMn3A/edit?tab=t.0#heading=h.gfoe2totyqbx
  • index with how tos in catalog classic section may need to be combed through

Open questions:

  • when you link to an AI gateway model, you can add any provider, even if the linked Model doesn't have that provider in it's config
  • MCP registry publishing?

Preview Links

Checklist

  • Tested how-to docs. If not, note why here.
  • All pages contain metadata.
  • Any new docs link to existing docs.
  • All autogenerated instructions render correctly (API, decK, Konnect, Kong Manager).
  • Style guide (capitalized gateway entities, placeholder URLs) implemented correctly.
  • Every page has a description entry in frontmatter.
  • Add new pages to the product documentation index (if applicable).

Signed-off-by: Diana <75819066+cloudjumpercat@users.noreply.github.com>
@cloudjumpercat cloudjumpercat added do not merge Issues/ PRs whose changes should not be merged at this time release-docs Docs for release labels Aug 6, 2026
@netlify

netlify Bot commented Aug 6, 2026

Copy link
Copy Markdown

Deploy Preview for kongdeveloper ready!

Name Link
🔨 Latest commit 1f7b89b
🔍 Latest deploy log https://app.netlify.com/projects/kongdeveloper/deploys/6a7e038f42a77a0008662cd3
😎 Deploy Preview https://deploy-preview-6586--kongdeveloper.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

… about differences to catalog landing page, content about differences on the classic landing page

Signed-off-by: Diana <75819066+cloudjumpercat@users.noreply.github.com>
…e some in UI step links

Signed-off-by: Diana <75819066+cloudjumpercat@users.noreply.github.com>
Comment thread app/catalog/ai-models.md
{% endnavtab %}
{% endnavtabs %}

## AI Model analytics

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

FYI - AI Gateway 2.0 is still bootstrapping the analytics, so we have placeholders in the UI but data is not populating atm.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@cloudjumpercat Do we think it still makes sense to leave this here? To give you a sense of timelines, the AI Gateway team is hoping to get Analytics for their 2.0 object-model shipped by end-September.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

That said, we (as in, Catalog team) are shipping the UI widget already. Users will just see blank dashes ("-") instead of populated numbers.

Comment thread app/catalog/ai-models.md
Add the providers and target models that this AI Model routes to by sending a POST request to the `/ai-models/{aiModelId}/versions` endpoint:
<!--vale off-->
{% konnect_api_request %}
url: /v1/ai-models/$AI_MODEL_ID/versions

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

add version field to this request:

{

    "version": "1.0.0",
    "target_models": [
        {}
    ]

}


- header:
type: h2
text: "Create your catalog"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Could we reorder these cards to: APIs -> API Packages -> AI Models -> MCP Registries (tech preview)?

Comment thread app/_landing_pages/catalog.yaml Outdated
key: solution
rows:
- usecase: |
You need to know every AI model, API, and MCP server your org has built, without checking each team's tools individually

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

"...know every API, AI Model, and MCP server..."

Comment thread app/_landing_pages/catalog.yaml Outdated
- q: "What if I notice discrepancies in {{site.konnect_catalog}} data?"
a: "Check integration settings, verify connected tools, and ensure data synchronization is working correctly."
- q: "What's different between {{site.konnect_catalog}} and {{site.konnect_catalog}} Classic?"
a: "{{site.konnect_catalog}} is the unified, platform-level experience for APIs, API packages, AI Models, and MCP Registries (tech preview) today, with more interface types coming. {{site.konnect_catalog}} Classic remains available with Services, Scorecards, and Integrations. See [Migrate to the new Catalog](/catalog-classic/#migrate-to-the-new-catalog) for how to move to the new experience."

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

"Classic remains available with Services, Scorecards, and Integrations." -> "Classic remains available with Services."

We do want to eventually bring Scorecards and Integrations back in the new Catalog experience.

Comment thread app/_landing_pages/catalog.yaml Outdated
a: "Check integration settings, verify connected tools, and ensure data synchronization is working correctly."
- q: "What's different between {{site.konnect_catalog}} and {{site.konnect_catalog}} Classic?"
a: "{{site.konnect_catalog}} is the unified, platform-level experience for APIs, API packages, AI Models, and MCP Registries (tech preview) today, with more interface types coming. {{site.konnect_catalog}} Classic remains available with Services, Scorecards, and Integrations. See [Migrate to the new Catalog](/catalog-classic/#migrate-to-the-new-catalog) for how to move to the new experience."
- q: "What happened to Services, Integrations, and Scorecards?"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

"What happens to Integrations and Scorecards?"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

And then, could we instead explain that Integrations and Scorecards will eventually be brought back into the new Catalog experience, but with a focus on APIs & AI interfaces, rather than Services?

(Probably needs some wordsmithing.)


- header:
type: h2
text: "Frequently asked questions"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Should we explain how an Org Admin can toggle between the old Service Catalog and the new Catalog experience? To do so, they have to enable the toggle under Organization > Settings > Catalog.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Nevermind! I see that you already cover this in the Konnect Catalog Classic page.


An MCP server can define multiple packages and multiple remotes simultaneously. This allows organizations to support different runtime environments without duplicating server definitions.

## Publish an MCP Registry to Dev Portal

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I'd take this out. The MCP Registry (Tech Preview) object won't be publishable to Portal.

The new MCP Server object that we're launching into GA by end-September, though, will be publishable to Portal. Timeline for the Portal publishing bit specifically needs to be confirmed with Jason/Nathanael.

Comment thread app/catalog/ai-models.md
1. To manually define providers and models, select **Add manually**.
1. To import an existing gateway-defined model, select **Import from AI gateway**, then:
1. From the **AI gateway** dropdown menu, select your {{site.ai_gateway}} control plane.
1. From the **Model from AI gateway** dropdown menu, select the model you want to import.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I feel like we should link out into AI Gateway's documentation for their AI Model object.

Comment thread app/catalog/ai-models.md
url: /ai-gateway/
---

An AI Model is an interface in {{site.konnect_catalog}} that represents the providers and target models your organization routes requests to, along with the OpenAPI spec that describes how to call it.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We should explain what it actually means for an AI Model in Catalog to be "linked" to an AI Model in AI Gateway. When the two are linked, it means traffic to that Catalog entity is protected by AI Gateway.

The same principle apply to MCP Servers and Agents too.

Signed-off-by: Diana <75819066+cloudjumpercat@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Issues/ PRs whose changes should not be merged at this time release-docs Docs for release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Catalog: Revamp M2

4 participants