docs: update sveltesociety.dev links

[lachlancollins]

Changes

This PR updates the sveltesociety.dev links to use URL query params to filter tags, rather than the previous URL fragment.

For example, https://sveltesociety.dev/packages#svelte-kit-adapters becomes https://sveltesociety.dev/packages?tag=sveltekit-adapters

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• Prefix your PR title with feat:, fix:, chore:, or docs:.
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0baff48

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[benmccann]

Sigh. I really wanted to give svelte-society/sveltesociety.dev#541 another look, but didn't get a chance yet due to the holidays. I think the new UI is pretty messy because of the huge list of tags on the top of the page and the change also conflicts with other plans I had for that page. Honestly I think we should consider reverting svelte-society/sveltesociety.dev#541 at least temporarily as I feel it needed more discussion. @MacFJA did you have a chance to take a look at that change?

[lachlancollins]

Oh I'm so sorry @benmccann! I was eager to get this merged because I have a limited timeframe where I can smash out a bunch of tasks before life becomes a whole lot busier (indefinitely). I wasn't aware you had your own plans for this page either! I took @kevmodrome's positive feedback as approval.

This is what I see as the pros and cons of this change:

Pros:

• Better functionality - When you apply a tag, it narrows your other tag options. This helps users apply all the conditions they want from their package.

• Better UX - Applying tags now is just a single click, rather than a click, scroll/type, click. Also, having 2 separate select fields could be confusing - if an entry could fit under multiple categories, the user won't know which one we assigned to it.

• Better discoverability - With category separation, the first alphabetical category always appears first, so you always see the same entries at the top, even with different sorting.

Cons:

• Messier UI - There are a lot of tags on the packages page, so this isn't a perfect solution either. I have adjusted the CSS to reduce the amount of whitespace showing up on mobile layout.

I'd be interested in hearing if you had any suggestions for handling the UI problem. One idea I've had would be making them expandable/collapsible from a single row to all rows? Maybe we could continue discussion on Discord rather than this repo?

[benmccann]

Thanks for all the updates! This is looking pretty good to me now. I left you a message on Discord earlier today. I think my one remaining question before merging this is about the URL. We can discuss on Discord, but thought I should share an update here in case anyone else tries to look at this PR