Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title: Add fallback guidance for VS Code Marketplace links
Summary: Added short fallback notes in the docs to help users who encounter an intermittent 404 when opening the Accord Project VS Code extension in the Visual Studio Marketplace. This is a documentation mitigation only (not a Marketplace or server-side fix).
Changes:
Files updated: docs/started-resources.md, website/versioned_docs/version-0.30.1/started-resources.md, docs/tutorial-vscode.md, website/versioned_docs/version-0.21/tutorial-vscode.md, docs/accordproject.md, website/versioned_docs/version-0.30.1/accordproject.md
What changed: each file now contains a one-line note advising: if the Marketplace page shows a 404 on first load, click “Go back home” on that page or search for “Accord Project” in the VS Code Marketplace.
Flags:
This is a user-facing workaround only; it does not fix the underlying Marketplace routing/redirect behavior.
Recommend the maintainers ask repository owners or the Marketplace team to verify the extension URL and server-side redirects, and consider automated link checks in CI.