[Feedback] Site Organization, QoL, Persistent logic of submitted file structure #208908
Unanswered
V3XBANE
asked this question in
Repositories
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
Body
For years before I got involved with any code related activities myself, I absolutely HATED coming to github. For the average person to find the "file" they need to download to do it's a convoluted mess. Now that I've been doing some misc coding things here and there, trying to use github to work for my needs is a heinously horrible experience even more.
It only makes sense that being a coder, you want persistent structure of your files / folders across all platforms. When uploading stuff you github, there is very little control of that. The green "get code" button should not exist in my opinion, or should be allowed to be disabled by devs that upload stuff, so It can't be the method that is used to download the code. Github controls the file / folder structure of that green button for whatever their cataloging / archiving reasons may be and screw with the logic behind the intend of the file folder structure of the developer.
As a dev, to not have control over this being exposed, used or influence over how that folder structure behaves once github puts its own -main extension on the zip and inside folder is counterintuitive. Putting a side the fact Github is more for "devs" than those that are downloading it - the average user trying to find the right thing to click on is annoying, pathetic design. Even if its not primarily designed for "non devs" you dont have to purposely have a terrible system in place when there are better ways to handle it. After all, if there were no "consumers" for the devs products - there'd be no use for devs. the clients are just as important in a symbiotic feedback loop.
I had a terrible time setting up the desktop github to try to submit / publish stuff directly from pc without going to website only to find the whole process infuriating that I had to be mindful of the exact file structure in order to know exactly how it would look / download for others once uploaded. Asking why tf its even setup this way
The system for this should be so intuitive and multifaceted layers of control over our content with simplistic ease to share with others. Coders and non coders a like. Of all the billions of people and millions of coders on the planet, this is the best we got? Surely we can find a better way, if we can first agknowledge there is a problem with it in the first place.
All reactions