search

fresh-standard / fresh-resume-schema

A rational schema for your résumé or CV.
https://resume.freshstandard.org
MIT License
548 stars 25 forks source link

FRESH vs JSON RESUME #16

Closed drkarl closed 8 years ago

drkarl commented 8 years ago

I really like HackMyResume (well, I'm a little bit confused of wether I should use HackMyResume or the fork FluentCV, and if I wanted to contribute to which project should I contribute).

I think FRESH is a good format, but I also think JSON Resume is a good format, and there seems to be more people involved on the latter, and seems to have more adoption and more momentum. So, my question (and is a honest question), why don't we just use one format? That would allow to focus efforts and move faster.

There are probably good reasons to maintain FRESH separate/different from JSON Resume, I'd like to know about them :)

drkarl commented 8 years ago

I think this answers my question :)

https://github.com/fresh-standard/fresh-themes/issues/45#issuecomment-175229207

Translations between the disparate formats are a lot easier if you have a universal container format that won't lose data. That format is FRESH.

drkarl commented 8 years ago

Also, about https://github.com/fresh-standard/fresh-themes/issues/45#issuecomment-175229207

I agree with you, I want to use this concept of decoupling the data and appeareance of a CV locally, not in a cloud service where I wouldn't have control of my data.

drkarl commented 8 years ago

I'll close this now :)