docs: migration guide (WIP)

[dummdidumm]

alternative to #249, would like an early look to see if the direction makes sense. Relies on #347 being merged.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
omnisite	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 12, 2024 9:21pm

[Rich-Harris]

yeah, this is definitely the right approach rather than #249. Seeing it laid out like this makes it feel nice and manageable

[dummdidumm]

lolol the headline.

That said, I'm wondering if they should go into some kind of <details> element instead (similar to the legacy deprecations) so you can ignore them when you're not interested in the reasoning.

[Rich-Harris]

Yeah, I had the same thought. Let's try it

[dummdidumm]

Finished the first version of this - you can take it from here as I'm not gonna be able to work on it next week. (make sure to copy this back to the Svelte repo once you're happy with it)

Note that I added a style tweak to not use italic on <details>, they tend to contain too much text to be readable that way IMO.

[Rich-Harris]

haven't edited it yet but this document already now exists on main, so i'll close this