Add a "Tools" section#2092
Conversation
dscho
left a comment
dscho
left a comment
There was a problem hiding this comment.
Very nice! I have just one main concern about leaving backwards-compatible redirects when moving pages, but otherwise it looks wonderful!
Put on the homepage and in the sidebar Signed-off-by: Julia Evans <julia@jvns.ca>
Signed-off-by: Julia Evans <julia@jvns.ca>
Signed-off-by: Julia Evans <julia@jvns.ca>
Signed-off-by: Julia Evans <julia@jvns.ca>
These boxes look like giant buttons, and I don't hate that idea. But they aren't. Having the whole box clickable would be nice I think, with making the background gray on hover. Or would that be too much? |
|
@jvns Just a few comments from my side. But I really like where this is going! 💜 |
|
@To1ne I agree they look like buttons and it's a bit weird. On its own I like the idea of making the whole thing clickable, but because right now the design is the same as the design as https://git-scm.com/learn, it requires also rethinking the design of that page and I'm not quite sure how to do it. It's tricky because on the Learn page there are sometimes internal links inside those boxes, so you can't make the whole box a link in the same way |
|
Let’s then just defer that to a later point.
|
|
💜 |
3 participants
This adds the "Tools" page discussed in #2070. I added tools to the "command line tools" page pretty arbitrarily -- I just added a tools that I've heard of before or used, with the idea that folks can submit PRs with other tools that they've used. I tried to stick to the ways the command line tools describe themselves and avoided editorializing.
I also moved "Hosting" into the Tools section from the homepage (from #2063), since hosts feel like tools to me, especially since some of them can be self-hosted. In the future it might be good to point out specifically which repository hosting tools can be used to self-host, but I just moved the existing page for now.
You can see it in action here: https://jvns.github.io/git-scm.com/tools
I think the main thing that still needs to be done here is to to add a little more "editorial" text around these community tools -- I think for most people using Git is a much better experience when using some third-party Git tooling and it would be nice to communicate that in some way.
Fixes #2070 and #2063