From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: "Matt Burke" <spraints@gmail.com>,
"Victoria Dye" <vdye@github.com>,
"Matthias Aßhauer" <mha1993@live.de>,
git@vger.kernel.org
Subject: Re: Migration of git-scm.com to a static web site: ready for review/testing
Date: Thu, 12 Sep 2024 00:18:42 +0200 (CEST) [thread overview]
Message-ID: <c36ce70c-59ad-c53e-8ef6-cce779e428eb@gmx.de> (raw)
In-Reply-To: <807be06c-e70c-4ee4-8851-bb8d82b68ac2@gmail.com>
Hi Kaartic,
On Fri, 24 Nov 2023, Kaartic Sivaraam wrote:
> On 17/11/23 18:55, Johannes Schindelin wrote:
> >
> > To that end, I deployed this branch to GitHub Pages so that anyone
> > interested (hopefully many!) can have a look at
> > https://git.github.io/git-scm.com/ and compare to the existing
> > https://git-scm.com/.
> >
>
> Thanks for hosting it to easily check things!
>
> I gave a quick try at the search and it seems to be behaving a bit strangely.
>
> For instance, I searched for 'commit' and 'log'. I was hoping to see the
> corresponding reference page show up in the results but they don't seem to
> show up. At least they don't show up in the first few results. They show up in
> the first few results in the existing site.
>
> Here are some screenshots:
>
> Existing site: https://ibb.co/pZHx9TM
>
> New site:
> https://ibb.co/dMpNth3
> https://ibb.co/h26J5Rx
>
> This not always the case, though. Some terms like 'checkout' seem to bring the
> relevant results properly in the top results.
This was quite the adventure to figure out. I worked with the maintainer
of Pagefind in the meantime, to add better controls regarding how much
impact various dimensions should have on the search results. And I am
happy to report that the fruit of these labors is now available to all, in
the form of Pagefind v1.1.1.
I have integrated this into https://github.com/git/git-scm.com/pull/1804.
Ciao,
Johannes
next prev parent reply other threads:[~2024-09-11 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 13:25 Migration of git-scm.com to a static web site: ready for review/testing Johannes Schindelin
2023-11-17 16:26 ` Todd Zullinger
2023-11-18 1:14 ` Johannes Schindelin
2023-11-18 2:57 ` Todd Zullinger
2023-11-21 14:25 ` Johannes Schindelin
2023-11-28 1:54 ` Todd Zullinger
2024-09-11 22:18 ` Johannes Schindelin
2023-11-18 9:41 ` Johannes Sixt
2023-11-18 9:46 ` Johannes Schindelin
2023-11-23 18:53 ` Kaartic Sivaraam
2024-09-11 22:18 ` Johannes Schindelin [this message]
2024-09-11 22:18 ` Johannes Schindelin
2024-09-11 22:20 ` Johannes Schindelin
2024-09-12 7:53 ` Toon Claes
2024-09-14 18:41 ` Johannes Schindelin
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=c36ce70c-59ad-c53e-8ef6-cce779e428eb@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=mha1993@live.de \
--cc=spraints@gmail.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).