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

Feat: Recommended Resources #2

Open
raygervais opened this issue Oct 28, 2022 · 1 comment
Open

Feat: Recommended Resources #2

raygervais opened this issue Oct 28, 2022 · 1 comment

Comments

@raygervais
Copy link

Purely just throwing the idea, not implying it's a needed concept

Description and Idea Behind

Similar to curating content found on social media, I've found having peer-reviewed recommendations to be invaluable when learning; removing some of the ambiguity of all the links found in a Google search.

Imagine you're working on a rust project and VS Code has identified that is the language currently open in an editor:

A small window pane opens to the side (or, can be opened via the command prompt if we don't want to clutter the UI?) with a set of links relative to the language (documentation, How-to) which has been provided and rated by the Seneca community. Users can submit and rate resources so that it can be peer reviewed and validated.

I believe this could be useful for all devs, both new and seasoned who are looking for highly spoken of resources for:

  • Learning a new language
  • Using a popular framework
  • Common idioms of a language or platform
  • etc

Steps to consider

  • Users would have to be authenticated, would not want anon interaction.
  • Something like this would involve a back end service external to the client to perform basic CRUD operators
  • Ratings, Submissions would be attached to the user for easier auditing
  • Spam filtering would need to be considered. I see any CRUD-centric app being a terrible headache when it comes to content aggregation and submissions
@humphd
Copy link
Contributor

humphd commented Oct 29, 2022

I like this, since it unifies a goal of almost all of the "Seneca Devs," namely, to learn how to do what they are currently doing.

We could try this out using something simpler to begin: showing static content (HTML) in a pane in the editor that is relevant to the file/project you're working on currently. Curation could begin by being done as Markdown in a repo, and we could consume this in the extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants