-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Reinstate svelte 3/4 tutorial #14063
Comments
It is available at https://v4.svelte.dev/tutorial |
@dummdidumm Can I rephrase this question in that case as 'make it easier to find v4 docs'. I can't find a link to them anywhere on the site |
The old site is linked to from https://svelte.dev/docs/svelte/legacy-overview - I don't think we want to make this too prominent. People looking for information about legacy features sounds like the right audience. |
But I was looking fro information about legacy APIs, and I couldn't find it. What would be so bad in making it easier for people like me. It's not as if the site navigation is overloaded or cluttered. It's not uncommon - arguably it's close to being a convention - for projects to include a version selector in site navigation (jest, react, eslint, vitest, vite, next.js, webpack ... the last 2 are also open source projects run by vercel) What are the benefits to the svelte project of making it harder to find than in other popular projects? |
Describe the problem
I maintain a project that needs updating about once a year. It's the only svelte codebase I work in, and every time I return to it I inevitably need to refresh my memory of svelte fundamentals. The tutorial was great for this, but now a tutorial for svelte 5 is all there is. I don't want to upgrade to svelte 5 as a precursor to making the small changes I need to do, but am struggling to find good learning resources for svelte 3.
Describe the proposed solution
Make the tutorial for svelte 3/4 available on something like https://svelte.dev/tutorial/legacy-api
Importance
would make my life easier
The text was updated successfully, but these errors were encountered: