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

Tools page or pages? #58

Closed
benmccann opened this issue Jul 11, 2024 · 2 comments
Closed

Tools page or pages? #58

benmccann opened this issue Jul 11, 2024 · 2 comments
Milestone

Comments

@benmccann
Copy link
Member

benmccann commented Jul 11, 2024

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?

Screenshot from 2024-07-11 14-35-19

Or should we combine them into a single section?

Screenshot from 2024-07-11 14-55-39

A few considerations:

  • eslint-plugin-svelte has about 70 pages. It also has an existing site and a 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).

@benmccann
Copy link
Member Author

From maintainer's chat: let's prototype dropdown menu with a dozen items and see what it looks like and play around with it

@Rich-Harris Rich-Harris added this to the one day milestone Oct 12, 2024
@Rich-Harris
Copy link
Member

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

@Rich-Harris Rich-Harris closed this as not planned Won't fix, can't repro, duplicate, stale Oct 31, 2024
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