DTC-149: SEO optimize Blazor AI tools overview - #3822
Conversation
yordan-mitev
left a comment
yordan-mitev
left a comment
There was a problem hiding this comment.
A lot of content was repeated in the newly added sections and tables; Many Style Guide rules related to formatting and conciseness were broken; lots of fluff that adds no actual value was introduced;
That's not to say that the article doesn't need rewriting; on the contrary, it does, but it needs focused work on the actual problems without introducing new issues.
| title: Overview | ||
| page_title: Telerik Blazor MCP Server Overview | ||
| description: Learn about the Telerik Blazor MCP Server, its modes of operation, and how it enhances AI-powered development with Telerik UI for Blazor components. | ||
| title: Telerik UI for Blazor AI Tools Overview |
There was a problem hiding this comment.
This change makes the navigation item unnecessarily long and barely readable. I suggest reverting it.
| page_title: Telerik Blazor MCP Server Overview | ||
| description: Learn about the Telerik Blazor MCP Server, its modes of operation, and how it enhances AI-powered development with Telerik UI for Blazor components. | ||
| title: Telerik UI for Blazor AI Tools Overview | ||
| page_title: Telerik UI for Blazor AI Tools Overview |
There was a problem hiding this comment.
There's a mismatch between the navigation folder title and the page_title. The most logical title here would be "Agentic UI Generator Overview" to fit the context of the parent folder. If you want to keep "Telerik UI for Blazor AI Tools Overview" as a title, you must change the folder names in the navigation.
| tag: updated | ||
| --- | ||
|
|
||
| # Telerik UI for Blazor AI Tools Overview |
There was a problem hiding this comment.
There's again a mismatch between the parent folder in the navigation (Agentic UI Generator) and the H1 in this article. Which one is correct?
|
|
||
| # Telerik UI for Blazor AI Tools Overview | ||
|
|
||
| The Telerik UI for Blazor AI Tools are delivered through a single [Model Context Protocol (MCP) server](https://modelcontextprotocol.io/docs/getting-started/intro) that connects your AI client to UI-generation capabilities and knowledge specific to Telerik UI for Blazor. |
There was a problem hiding this comment.
I'm genuinely confused with this terminology - again talking about "Telerik UI for Blazor AI Tools" when I'm in the "Agentic UI Generator" folder, but everything I need is an MCP server? So three different names for the same thing?
|
|
||
| ## Before You Start | ||
|
|
||
| This overview assumes that you have: |
There was a problem hiding this comment.
Why do I need that in an Overview? Doesn't this information belong in the Getting Started article that covers the procedure?
|
|
||
| The following examples show what an end-to-end interaction can look like in practice. | ||
|
|
||
| ### Orchestrated Workflow Example |
There was a problem hiding this comment.
The formatting and style in these newly added sections are totally made up and don't follow the Style Guide.
|
|
||
| **Scenario:** You have a Blazor line-of-business app and need a new sales dashboard page. | ||
|
|
||
| **Prompt:** `Create a sales dashboard page with KPI cards, a revenue trend chart, a filter form, and a Telerik UI for Blazor Grid that shows recent orders with paging and filtering.` |
There was a problem hiding this comment.
Did we confirm that these prompts work as described here?
| * Your application data model and transport layer decisions. | ||
| * Performance testing with your real dataset size and hosting constraints. | ||
|
|
||
| ## Example Workflows |
There was a problem hiding this comment.
How many "example workflows" do we need to present in a single Overview article? Isn't it too much by now?
|
|
||
| Keep the following boundaries in mind: | ||
|
|
||
| * This overview does not replace the detailed setup, troubleshooting, or API-focused articles linked from Getting Started and the Prompt Library. |
| Use `#telerik_ui_generator` for a complete orchestration-first workflow from a single prompt. When you need finer control or want to adjust just one aspect (such as layout, theme, or a component), you can call a specialized assistant directly by its dedicated handle. For details, see [Target the Assistants (Advanced)](slug:agentic-ui-generator-prompt-library#assistant-specific-prompts). | ||
| Use `#telerik_ui_generator` when one request spans layout, components, styling, accessibility, and validation. Switch to a dedicated assistant when the page already exists and you want to refine a single area without rerunning the full orchestration flow. For details, see [Target the Assistants (Advanced)](slug:agentic-ui-generator-prompt-library#assistant-specific-prompts). | ||
|
|
||
| ## Limitations and Unsupported Scenarios |
There was a problem hiding this comment.
Which unsupported scenario exactly is described in this section?
2 participants
Asana item
Result after improvements