git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Toon Claes <toon@iotcl.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Cc: "Matt Burke" <spraints@gmail.com>,
	"Victoria Dye" <vdye@github.com>,
	"Matthias Aßhauer" <mha1993@live.de>,
	"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
	"Todd Zullinger" <tmz@pobox.com>, "Johannes Sixt" <j6t@kdbg.org>,
	"Matthias Aßhauer" <mha1993@live.de>,
	"Toon Claes" <toon@iotcl.com>, "Taylor Blau" <me@ttaylorr.com>
Subject: Re: git-scm.com is now a static website
Date: Thu, 26 Sep 2024 10:30:28 +0200	[thread overview]
Message-ID: <87o74a4y1n.fsf@iotcl.com> (raw)
In-Reply-To: <c3e372f6-3035-9e6b-f464-f1feceacaa4b@gmx.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> This was truly a team effort, and I would like to celebrate everyone who
> contributed:

Amazing job everyone, it's really impressive!

> - Toon Claes for not only pointing out that the style sheet for the search
>   results needs fixing but also for fixing it right away,

I only wrote five lines of CSS, but thanks for having me take part.

> You will note that the site looks pretty similar to the version before,
> and this is of course intentional.

That's the best thing. Nobody's gonna know...

> 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?

Yeah, serving static images makes a lot more sense. Unfortanately I'm
not familiar with d3.js.

But I will have a look at the GitHub issue tracker if there's anything
else I can help out with.

-- 
Toon

  parent reply	other threads:[~2024-09-26  8:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24 22:07 git-scm.com is now a static website Johannes Schindelin
2024-09-24 22:19 ` Taylor Blau
2024-09-30 16:11   ` Taylor Blau
2024-10-09 16:09     ` Taylor Blau
2024-10-09 17:33       ` Junio C Hamano
2024-09-24 22:28 ` brian m. carlson
2024-09-24 22:29 ` Jeff King
2024-09-24 23:53 ` Junio C Hamano
2024-09-26  8:30 ` Toon Claes [this message]
2024-09-26 13:53 ` Patrick Steinhardt
2024-09-29  8:41 ` Scott Chacon
2024-09-30  7:46   ` Christian Couder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o74a4y1n.fsf@iotcl.com \
    --to=toon@iotcl.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=mha1993@live.de \
    --cc=spraints@gmail.com \
    --cc=tmz@pobox.com \
    --cc=vdye@github.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).