Skip to content

Conversation

@dev-singh12
Copy link
Contributor

Fixes sveltejs/kit#14941

This PR addresses the issue of the support link in the Editor Tooling section of the Getting Started documentation resulting in a "No content found" page.


What's Fixed

Updated the link within the 'documentation/docs/01-introduction/02-getting-started.md' file. The text and surrounding formatting have been preserved exactly as they were, with only the URL being modified.

  • Old URL: https://sveltesociety.dev/resources#editor-support
  • New URL: https://sveltesociety.dev/collection/editor-support-c85c080efc292a34

Why This Change Matters

The old link resulted in a "No content found" error, causing confusion for new users seeking editor setup instructions. This change ensures the documentation provides accurate, working resources so beginners can easily find supported editor integrations.


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.
  • If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

This PR only updates documentation and does not modify any source code or logic.

  • Run the tests with pnpm test and lint the project with pnpm lint (N/A, documentation change only)

Updated editor tooling section for clarity and added link to the Editor Support collection.
Fix: Update support link URL in Getting Started documentation

Updates the support URL in 'documentation/docs/01-introduction/02-getting-started.md' to the correct location.
All content surrounding the link has been verified and restored to its original state.
@changeset-bot
Copy link

changeset-bot bot commented Dec 2, 2025

⚠️ No Changeset found

Latest commit: d90e42a

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

@svelte-docs-bot
Copy link

@benmccann benmccann changed the title fix: Update outdated Svelte Society editor support link URL docs: update outdated Svelte Society editor support link URL Dec 3, 2025
@benmccann
Copy link
Member

Note that there are other broken links that should be cleaned up: sveltejs/kit#15010 (comment)

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

Playground

pnpm add https://pkg.pr.new/svelte@17292

@dev-singh12
Copy link
Contributor Author

@benmccann
Sir,can I get those broken links which need to be fixed?

@Rich-Harris
Copy link
Member

They're listed on the linked issue. You just need to go and read it.

Look, we appreciate PRs that fix stuff but please, for the love of god, stop using 'AI' agents to do it. This PR should have been an extremely straightforward fix that you could have done yourself, but instead there have been multiple commits that left errors that a maintainer needed to step in and fix. So far you have wasted much more time — both your own, and ours — than you've saved.

Again: you are wasting your time using these tools. Learn how to contribute as a human, or don't bother.

@Rich-Harris Rich-Harris merged commit ba9de6a into sveltejs:main Dec 3, 2025
2 checks passed
@dev-singh12
Copy link
Contributor Author

Thanks for the feedback ,I understood your point.
The changes were reflecting correctly in my editor, but since this was my first PR in a reputed org.
To be honest I rushed through it and panicked a bit . I used AI only to explore the docs and check if any other links might be broken, not to replace my own contribution — but I’ll take this as valuable feedback and ensure future contributions are carefully reviewed and human-driven.

I’m taking this as inspiration to improve and contribute in a better way going forward.
@Rich-Harris sir🙏

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

Successfully merging this pull request may close these issues.

3 participants