As @br3wb0n1k
mentioned, with the JSON file the data is separated from the code, hence you don't have to search and go through the code to update your personal information.
Also the Json follows standard which is always good 😏
I actually thought about making a command line tool that would assist you in building your own Json file (so you don't have to know the Json Resume standard). But that's the only "automation" I would add.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why is piping in from a JSON file easier to update? It’s still a manual process or am I missing something?
It's a nicer way of managing the content in one place. It also provides a visible data model for expanding on the project (ie. adding a CMS)
As @br3wb0n1k mentioned, with the JSON file the data is separated from the code, hence you don't have to search and go through the code to update your personal information.
Also the Json follows standard which is always good 😏
Is there a better way to deal with that? An automation process, for example?
I actually thought about making a command line tool that would assist you in building your own Json file (so you don't have to know the Json Resume standard). But that's the only "automation" I would add.