Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Two "Hosting Integration" links nearby go to different places #2648

Open
afscrome opened this issue Feb 20, 2025 · 1 comment · May be fixed by #2566
Open

Two "Hosting Integration" links nearby go to different places #2648

afscrome opened this issue Feb 20, 2025 · 1 comment · May be fixed by #2566
Assignees
@IEvangelist
Labels
doc-enhancement Improve the current content [org][type][category] in-pr okr-quality Content-health KR: Concerns article defects/freshness or build warnings. Pri1 High priority, do before Pri2 and Pri3 🗺️ reQUEST Triggers an issue to be imported into Quest.

Comments

@afscrome
Copy link
Contributor

Describe the issue or suggestion

The integration pages have links named "Client Integration" in close proximity to each other, but each goes to a different place. (Ditto for "Hosting Integration".)

These two similar links have confused me a few time. It would be nice if there could be some more indication that one is linking to the Kafka specific client integration, whereas the other is linking to general details on client integrations.

Image
@dotnetrepoman dotnetrepoman bot added the ⌚ Not Triaged Not triaged label Feb 20, 2025
@IEvangelist IEvangelist self-assigned this Feb 24, 2025
@IEvangelist IEvangelist added 🗺️ reQUEST Triggers an issue to be imported into Quest. Pri1 High priority, do before Pri2 and Pri3 doc-enhancement Improve the current content [org][type][category] okr-quality Content-health KR: Concerns article defects/freshness or build warnings. and removed ⌚ Not Triaged Not triaged labels Feb 24, 2025
@dotnetrepoman dotnetrepoman bot added 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. and removed 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. labels Feb 24, 2025
@IEvangelist
Copy link
Member

Good callout, I can see how this misleading and confusing. I'll fix it and it should be live tomorrow.

@IEvangelist IEvangelist linked a pull request Feb 24, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@IEvangelist IEvangelist

Labels
doc-enhancement Improve the current content [org][type][category] in-pr okr-quality Content-health KR: Concerns article defects/freshness or build warnings. Pri1 High priority, do before Pri2 and Pri3 🗺️ reQUEST Triggers an issue to be imported into Quest.
Projects
dotnet/docs February 2025 sprint project
Status: 🔖 Ready
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Content for .NET Aspire 9.1 dotnet/docs-aspire
2 participants
@afscrome @IEvangelist