First Official Release

posted July 31, 2014

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 and thus no backwards compatibility has been built out.

Unfortunately this means that if you created a resume before this release, most parts of the ecosystem will not work for you. Though there weren’t too many changes 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 terminal. Once installed, you can also take advantage of the resume test command to test if your resume.json is compatiable with version 0.0.0.

For a full list of changes, view the README for the resume schema repo.

Just because this is an official release of the specification, it 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 it to have been. 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

An obligitory 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 brain storming the future of JSON resume.

Where are we heading?

After long discussions about the specification in the Github issues, we have come to settle on a few points.

  • JSON resume exist 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 to be the perfect description of a person but instead a description of a resume where only things relevant in the context of hiring will be allowed in.

To guarantee the success of JSON resume, we will be aiming to integrate as an import/export option where ever 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