Skip to content

DTC-169 standardize Blazor AI components intro - #3853

Open
antonmironovv wants to merge 1 commit into
masterfrom
docs/dtc-169-ai-components-blazor
Open

DTC-169 standardize Blazor AI components intro#3853
antonmironovv wants to merge 1 commit into
masterfrom
docs/dtc-169-ai-components-blazor

Conversation

@antonmironovv

@antonmironovv antonmironovv commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Updated the Telerik UI for Blazor AI Components overview page with developer-focused context and clear feature categories.

Changes

  • Replaced the marketing-focused introduction with a description of the AI-ready components and smart features available for Blazor applications.
  • Added an overview of four feature categories:
    • Conversational UI
    • Smart Grid Features
    • Editor AI Integration
    • Utility Components
  • Added a dedicated heading and explanatory paragraph for each category.
  • Grouped the existing article cards under their respective categories.
  • Preserved all existing card links, images, titles, and descriptions.

Related Jira item: DTC-169

@antonmironovv
antonmironovv requested review from a team as code owners August 12, 2026 12:13
Comment thread aicomponents.md

The available tools fit into four categories:

1. [Conversational UI](#conversational-ui)—Chat, PromptBox, Inline AI Prompt, and AI Prompt for conversational and prompt-driven interfaces.

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.

Consider adding the LLM Kit to the Conversational UI category: https://www.telerik.com/blazor-ui/documentation/components/llmkit/overview

@IvanDanchev IvanDanchev added the merge-to-production Use this label to get a comment to choose whether to merge the PR to production label Aug 27, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Hello @IvanDanchev,

Check the below option if you would like to automatically generate PR to production. The automation uses the branch for the cherry-pick, and then will delete the branch. Please, do not delete it manually.

  • create PR to production

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

Labels

merge-to-production Use this label to get a comment to choose whether to merge the PR to production

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants