It has been just over three weeks since JSON Resume first went public, and we are proud to announce the first official version of the specification. After much consideration we decided to launch the first version as 0.0.0, which assumes everything up until this point was conceptual, so no backwards compatibility has been built in.
Unfortunately this means that if you created a resume before this release, most parts of the ecosystem will not work for you. There weren't too many changes, though, so visit the specification page and update your resume.json accordingly.
Make sure you reinstall the latest version of the CLI tool by typing sudo npm install -g resume-cli into your terminal. Once it's installed, you can also use the resume test command to test whether your resume.json is compatible with version 0.0.0.
For a full list of changes, view the README of the resume schema repo.
Just because this is an official release of the specification doesn't guarantee that the ecosystem is stable. We actually had to wait for this official release before we could lock down parts of the ecosystem.
How are we doing?
When JSON Resume first went public, it was actually unexpected, and the project wasn't quite as mature as we would have liked. In the days following the leak, the homepage received over 50,000 visitors and a lot of people reached out offering support. We worked overtime to get people hacking away at different areas of the project.
Some accomplishments so far:
- Over 1400 stars on the resume CLI
- 97 issues created for the specification, 52 closed
- Built a modular theme system using npm for version management
- Active theme development underway
- Progress made on LinkedIn export
- Build your
resume.jsonwith a GUI, coming in the next few days (screenshot) - Organized a standards committee
- Multiple HR-related services are looking at supporting and potentially sponsoring the JSON Resume project
- Officially listed JSON schema on the JSON Schema Store
An obligatory thank you to everybody who has participated up to this point. And a very special thanks to Mattias Erming, who has put a lot of hard work into developing and brainstorming the future of JSON Resume.
Where are we heading?
After long discussions about the specification in the GitHub issues, we have settled on a few points:
- JSON Resume exists to empower individuals to manage their job-seeking profiles, and this is our highest priority.
- Because there is no easily accessible alternative, we are going to maintain a casual approach to the project.
- The specification is not meant to be the perfect description of a person, but a description of a resume, where only things relevant in the context of hiring are allowed in.
To guarantee the success of JSON Resume, we will aim to integrate as an import/export option wherever possible. We want a thriving theme ecosystem and as many tools as possible.
Please leave your feedback and ideas below! Also, please join the movement!
By Thomas Davis and Roland Sharp