It looks like this project can be archived?

What this extension would do, is literally just a setting in Visual Studio Code.
If you're adamant on helping users configure it, I think describing the setting in the documentation would be better.

That'd also provide a standardized solution that helps users be more productive with the editor, rather than a special one-off solution just for JSON Resume.

"json.schemas": [
  {
    "fileMatch": [
      "resume.json",
      "*.resume.json"
    ],
    "url": "https://raw.githubusercontent.com/jsonresume/resume-schema/v1.0.0/schema.json"
  }
]

Visual Studio Code also documents that one can use JSON Schema Store (on GitHub) to fetch JSON schemas to use in the $schema property. JSON Schema Store includes an entry for JSON Resume in its catalog.

The JSON support shipped with VS Code supports JSON Schema Draft 7.

Servers like JSON Schema Store provide schemas for most of the common JSON-based configuration files.
- https://code.visualstudio.com/Docs/languages/json#_json-schemas-and-settings

The only difference is that this project matches **/*resume.json and **/*.resume.json.
Schema Store currently only matches resume.json.

I've made a PR there to match the same files as this repository, plus the .yaml and .yml extensions, as they're supported by resume-cli.

• fix: accept .resume.json and allow any directory SchemaStore/schemastore#1760

The most popular YAML extension (redhat-developer/vscode-yaml) (third-party) automatically fetches JSON Schemas from JSON Schema Store and validates against it.

The JSON extension (built-in) doesn't do this yet. However, all example resumes and resume-cli set the $schema property by default, and getting IntelliSense enabled can otherwise be configured easily by users, and documented on the website if desirable.

The same support for JSON files will hopefully come eventually, an issue is being tracked for it here:

• [json] use the schemastore catalog microsoft/vscode#26289

When that's done, matching the JSON files will become default behavior of Visual Studio Code.

Overall, I think it'd be better to archive this repository and update the top of the README with instructions on how they could configure it themselves. (shown at the start of this issue)
It could also be nice to include a link to the issue on microsoft/vscode just to get it some more attention.