2 ms·

You are right I'm sorry to perpetuate anything bad. Thank you for your views and wisdom

• KronisLV 5y ago
  Actually, that felt like a very valid question on your part! A question that would be answered by a small intro for the project, like: "Svelte Cubed is a component library for building Three.js scene graphs in Svelte apps. It was built because of reasons X and Y, attempts to solve the W problem and in practice will make doing Z easier thanks to this." Perhaps a bit like their Getting Started guide, but with the missing reasoning for the project to exist: https://svelte-cubed.vercel.app/docs/getting-started https://svelte-cubed.vercel.app/docs/getting-started Similarly, the GitHub doesn't seem to have an extensive README or anything yet, either: https://github.com/rich-harris/svelte-cubed https://github.com/rich-harris/svelte-cubed While having docs of any sort is nice and should be encouraged, at the same time i often find myself wishing that more projects would summarize what they are, why they exist and what problems they solve, much like a lot of software packages do (or should do) in the app stores. Do other people not do that sort of stuff with their Git repos for projects, so that everyone can understand what they're looking at, at a glance? Here's a few examples from repos that were a part of my Master's degree: https://git.kronis.dev/rtu1/kvps5_masters_degree_covid_1984/blob/master/README.md https://git.kronis.dev/rtu1/kvps5_masters_degree_covid_1984/... https://git.kronis.dev/rtu1/kvps5_masters_degree_astolfo_cloud_servant/blob/master/README.md https://git.kronis.dev/rtu1/kvps5_masters_degree_astolfo_clo... (admittedly the repos themselves no longer are relevant, though should serve as an example of what i mean)