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
We have a lot of tools. Here are a couple of options for how to display them (ignore the main page content and just look at the sidebar)
Should that create a lot of sections each with mostly a single entry?
Or should we combine them into a single section?
A few considerations:
eslint-plugin-svelte has about 70 pages. It also has an existing site and a playground.
Should we try to incorporate the playground into the main site? Its setup looks complicated. I also don't know if that would make things harder for its developers
Should we just have a single page with setup instructions and then link to the site?
Or should move all the content over except for the playground?
The navigation menu is much simpler if they just have to choose between Svelte, SvelteKit, and Tools. It could be more to digest if there's a double digit number of items (svelte, sveltekit, vite-plugin-svelte, rollup-plugin-svelte, svelte-loader, svelte-preprocess, language tools, prettier-plugin-svelte, eslint-plugin-svelte, etc.)
We can probably add a link to both Svelte and SvelteKit on the homepage (#63) to simplify nav to those two most common destinations, but beyond that you'll have to choose from a larger list in a nav (#61).
The text was updated successfully, but these errors were encountered:
let's cross this bridge when we come to it, I don't know that we need to keep an issue open until then. For now I lean towards a section per package — pages are free
We have a lot of tools. Here are a couple of options for how to display them (ignore the main page content and just look at the sidebar)
Should that create a lot of sections each with mostly a single entry?
Or should we combine them into a single section?
A few considerations:
We can probably add a link to both Svelte and SvelteKit on the homepage (#63) to simplify nav to those two most common destinations, but beyond that you'll have to choose from a larger list in a nav (#61).
The text was updated successfully, but these errors were encountered: