It's been a while since we've done any work on QuikCV.

We originally built it so that we could easily manage our work history and make it easier for others to do the same.

It was successful in terms of allowing users to be able to easily update and modify their CV, but we ceased development of it due to not finding a way of monetising the service. Due to this, we decommissioned it, even though the service isn't publicly accessible we've still found ourselves using the service personally.

QuikCV was initially built using Rails 3 and BackboneJS, back in the day when CoffeeScript was all the rage, and we all loved Rails Engines.

Things have changed over the years, we now have ECMAScript and VueJS is a lot nicer to work with than BackboneJS. Along with this, there wasn't much reason for using Rails, apart from exposing API endpoints and serving pages. So once we've reviewed the service, we'll also consider extracting the core functionality and building it using VueJS.

Recently we had the pleasure of having to resurrect the project and having to reinstall the dependencies, which provided to be a bit of a challenge but reasonable considering that it's an 8-year-old project.

In this series we'll explore the core functionality of this project and identify the core bits of functionality required to update QuikCV and bring it into the 2020s.