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.

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

Consider ways to make this page look less hard #40280

Open
KathleenDollard opened this issue Apr 1, 2024 · 2 comments · May be fixed by #40999
Open

Consider ways to make this page look less hard #40280

KathleenDollard opened this issue Apr 1, 2024 · 2 comments · May be fixed by #40999
Assignees
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-fundamentals/svc install/subsvc Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@KathleenDollard
Copy link
Contributor

KathleenDollard commented Apr 1, 2024

Type of issue

General feedback on page

Description

This page seems very intimidating. I don't know if there are limitations that keep us from having separate pages here, which might help a bit. Mostly this content, especially install with VS jumps straight to information an expert needs (which TFM) and not what a beginner needs "You have what you need and this is how you adjust installed workloads if you need that"

Since most folks use VS, could we move that to the top and start with friendly language like "If you're using Visual Studio, hopefully you do not need anything on this page". OK, not that ;-)

Or put DevKit installation at the top with a nice simple walk-through.

Installation seems a place to focus on a welcome, feel good, hand holding vibe.

This page makes it look like it is hard to install .NET, and it came up high in SEO.

Page URL

https://learn.microsoft.com/en-us/dotnet/core/install/windows?tabs=net80#install-with-visual-studio

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/install/windows.md

Document Version Independent Id

d11d0d14-8a03-50e4-5c00-9a4417ad4d0a

Article author

@adegeo

Metadata

  • ID: 1eeab451-820f-de42-983e-4d0d5764f6ab
  • Service: dotnet-fundamentals
  • Sub-service: install

Associated WorkItem - 239918

@dotnet-bot dotnet-bot added ⌚ Not Triaged Not triaged needs-more-info Needs more info from OP. Auto-closed after 2 weeks if no response. [org][resolution] labels Apr 1, 2024
@issues-automation issues-automation bot added dotnet-fundamentals/svc install/subsvc Pri1 High priority, do before Pri2 and Pri3 labels Apr 1, 2024
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Apr 1, 2024
@KathleenDollard KathleenDollard changed the title Consider ways to make this Consider ways to make this page look less hard Apr 1, 2024
@adegeo adegeo reopened this Apr 1, 2024
@adegeo
Copy link
Contributor

adegeo commented Apr 1, 2024

Automation closed this because it was originally created empty.

@adegeo adegeo added doc-enhancement Improve the current content [org][type][category] and removed needs-more-info Needs more info from OP. Auto-closed after 2 weeks if no response. [org][resolution] labels Apr 1, 2024
@adegeo
Copy link
Contributor

adegeo commented Apr 1, 2024

Great feedback. This page has been neglected for sure.

@adegeo adegeo self-assigned this Apr 1, 2024
@adegeo adegeo added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label Apr 1, 2024
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Apr 2, 2024
@adegeo adegeo linked a pull request May 18, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-fundamentals/svc install/subsvc Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
Status: 👀 In review
Development

Successfully merging a pull request may close this issue.

3 participants