Currently the data for each command is hard coded in script.js. It would be better if we have one config.json file for all the data which the js code can read from.
Explain the possible use cases for the feature
It will make it much easier for others to clone the project and spin up their own terminal-portfolios. They will just have to add their data in the config.json file.
Any other details you would like to provide?
Later a platform can be built that enables users to create their own terminal portfolios by simply filling out a form with all their data.
Contact Details
sadashay01@gmail.com
Explain the proposed feature
Currently the data for each command is hard coded in
script.js
. It would be better if we have oneconfig.json
file for all the data which the js code can read from.Explain the possible use cases for the feature
It will make it much easier for others to clone the project and spin up their own terminal-portfolios. They will just have to add their data in the
config.json
file.Any other details you would like to provide?
Later a platform can be built that enables users to create their own terminal portfolios by simply filling out a form with all their data.