As per Sean's ideas here. I've fixed up the README very quikcly with a contributor section. But it could really use more TLC as well the repo itself could use a clean up. As he suggested. Here's Seans initial suggestion.
"
My initial takeaway is that your README is missing steps to get new users spun up. For instance, it assumes that users have Node.js (for the npx command) and svelte on their system already. It's a small thing but it can be a momentum derailer: I started getting node.js and sv on my system but turns out there were a couple extra steps for my machine.
In addition to improving the new user friendliness by explicitly listing which package installations will be necessary, I think you would also be well served by a bit of cleanup in your repository. The very first thing I noticed upon cloning your repo is that there are a ton of files in the home directory, getting me off to a confusing start (so I went to the README, which actually overall looks pretty good despite my original nitpick). Files like "temp_dump_file.dump" can probably just be deleted, those csv files and any other files containing raw data could be moved into a "data/" directory, and anything else that can be done to make the top level directory more organized/dev friendly would be good. After that I think adding a "contributors" section to your readme describing what you think initial steps developers/contributors should take would be helpful, even if it's simply "reach out to me for a quick conversation".
As per Sean's ideas here. I've fixed up the README very quikcly with a contributor section. But it could really use more TLC as well the repo itself could use a clean up. As he suggested. Here's Seans initial suggestion.
"
In addition to improving the new user friendliness by explicitly listing which package installations will be necessary, I think you would also be well served by a bit of cleanup in your repository. The very first thing I noticed upon cloning your repo is that there are a ton of files in the home directory, getting me off to a confusing start (so I went to the README, which actually overall looks pretty good despite my original nitpick). Files like "temp_dump_file.dump" can probably just be deleted, those csv files and any other files containing raw data could be moved into a "data/" directory, and anything else that can be done to make the top level directory more organized/dev friendly would be good. After that I think adding a "contributors" section to your readme describing what you think initial steps developers/contributors should take would be helpful, even if it's simply "reach out to me for a quick conversation".