You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub Issues are a great way to track issues about SvelteKit itself, but are perhaps not the best tool for help about using SvelteKit.
Since GitHub now has a built-in discussions tab for repositories, it would be amazing if we could turn those on.
Having a clear distinction between community support about usage and issues about the project would be beneficial in two main ways:
The Issues tab will be less cluttered, and contributors will have an easier time finding issues they would like to solve.
The discussions section is more welcoming for people seeking help than posting help as an issue. Also, there's the benefit of gamification in discussions, which could further encourage community members to help each other out.
Additionally, the discussions tab could have two (or more) main categories, 'help' and 'ideas/discussion', so that not only seeking help will be encouraged, but also discussing the evolution of SvelteKit in a slightly less formal setting.
The TailwindCSS discussions tab is a great example showcasing the possibilities of the GitHub discussions tab.
To me personally, this is more of a nice-to-have, but I think other people, especially newcomers to SvelteKit, will benefit a lot from this.
The text was updated successfully, but these errors were encountered:
GitHub Issues are a great way to track issues about SvelteKit itself, but are perhaps not the best tool for help about using SvelteKit.
Since GitHub now has a built-in discussions tab for repositories, it would be amazing if we could turn those on.
Having a clear distinction between community support about usage and issues about the project would be beneficial in two main ways:
Additionally, the discussions tab could have two (or more) main categories, 'help' and 'ideas/discussion', so that not only seeking help will be encouraged, but also discussing the evolution of SvelteKit in a slightly less formal setting.
The TailwindCSS discussions tab is a great example showcasing the possibilities of the GitHub discussions tab.
To me personally, this is more of a nice-to-have, but I think other people, especially newcomers to SvelteKit, will benefit a lot from this.
The text was updated successfully, but these errors were encountered: