Thanks for your kind words. When creating the resume state structure, I have considered making it a JSON Resume format so it is compatible with other JSON Resume as well as tools that built on top of JSON Resume. However, after looking more into JSON Resume's schema, I find it to be a bit more restrictive than I would like, e.g. it includes a startDate and endDate as date type for work experience, but I want to combine both into date so user can type anything they like `June 2022 - Present` or `06/2022 - Present`. Also, for skills, JSON Resume has a very fixed structured but I want to give users the freedom to type anything in any format. Overall, I think JSONResume works well on its own and defines each field very well. But when thinking in product level, these restrictions might pose too much restrictions, so I ultimately create my own custom resume state type.

This sounds reasonable. If exporting a JSON resume is not possible, maybe you could support importing one?

Great point. Top of my head, it seems possible and easier to support import from JSON resume instead of export. Just created an issue to keep track of it: https://github.com/xitanggg/open-resume/issues/12