Hey, On Wed, Sep 25, 2024 at 12:07 AM Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > Hi all, > > almost 400 weeks after Matt Burke started the process with > https://github.com/spraints/git-scm.com/commit/60af4ed3bc60 of migrating > Git's home page away from being a Rails app to being a static website that > is hosted on GitHub pages instead, today marks the day when Git's home > page at https://git-scm.com/ has finally moved. Or actually: yesterday > (because I took so long writing this email that I ended up sending it > after midnight). Big thanks to everyone involved in making this happen. As I'm pretty sure that nearly everything you've struggled valiantly to replace was largely my Ruby stuff from a decade ago, I appreciate the effort to move to something more stable and maintainable. > There are also new things that have sprung up that are not caused by the > migration to Hugo/Pagefind, for example some diagrams no longer shown (see > https://github.com/git/git-scm.com/issues/1862) because the Google Charts > API entered the Google Graveyard. Any takers? So, I commented on this issue, but maybe this is a good thing to discuss at the group level. The images on this page were comparing the speed of common operations between Git and _Subversion_. Ugh. Who cares now? I wrote all this stuff in the early days because those among us old enough to remember the fall of the Berlin Wall were still using systems like Subversion then and I was trying to sell Git's virtues. But now _everybody_ uses Git, there is no reason to sell it anymore, especially versus something like Subversion. The simple thing would be to solve issues like this by just removing this specific content, but we could also work on a perhaps more valuable project to rethink the website content entirely. Why are people coming to git-scm.com? What information are they looking for? How could we answer those questions most efficiently? This is essentially what my first version of git-scm.com was trying to do when I registered the domain and launched the first version 16 years ago as an alternative to git.or.cz: https://lore.kernel.org/git/d411cc4a0807251035i7aed2ec9wef7e8f1b3ae4c585@xxxxxxxxxxxxxx/ But as I said, the answers to these questions are very different today than they were 16 years ago. The version I helped launch 12 years ago (essentially the exact same site that exists there today) was trying to do the same thing - determine what people are coming to the site for and give them that information as quickly and easily as possible: https://lore.kernel.org/git/CAP2yMaJy=1c3b4F72h6jL_454+0ydEQNXYiC6E-ZeQQgE0PcVA@xxxxxxxxxxxxxx/ I would love to take another crack at this, I'm happy to put some design resources and further engineering (built off the great work Johannes has done here) into the project. It would be great to get some feedback from this group as to what they think would be most valuable for people today. For example, I think the book contents and the man-page hosting has been incredibly valuable. I still use those resources today from Google searches. I feel like perhaps the Guides section could be structured and presented better - there is some great documentation there. I have been talking to Apress on and off about a third edition, perhaps a revamp of that content is also overdue - the last edition of that was published in 2014. I think the entire "About" section should be totally rethought. Perhaps adding something about different use cases - large files for game development, etc. There is no mention of LFS or partial cloning or anything here. There is no information currently on any forge or hosting options, which seems silly. I think at the time I was trying to avoid "advertising" for GitHub, but it would be nice for people to know all the options for hosting their code, just as we have a client section. Even more CLI clients and tools, rather than just GUIs - things like git-absorb, stacked git, etc. Perhaps more videos - there is so much great content on YouTube we could link to. Right now it's like Linus's talk, my old Google talk and 4 Matt McCullough tutorials. I would love to pull in Git Rev News as a blog on git-scm.com, and/or link to Taylor's regular posts about what's new in the new versions. It's such great content and would be nice to have more visible. Honestly, this whole website would be nice to incorporate: https://git.github.io/rev_news/ In the end, I'm happy to put some work into this, or perhaps work with Johannes and Taylor and Matt and whomever else is maintaining the site now. Scott