git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: git@vger.kernel.org
Cc: "Matt Burke" <spraints@gmail.com>,
	"Victoria Dye" <vdye@github.com>,
	"Matthias Aßhauer" <mha1993@live.de>
Subject: Migration of git-scm.com to a static web site: ready for review/testing
Date: Fri, 17 Nov 2023 14:25:43 +0100 (CET)	[thread overview]
Message-ID: <6f7d20b4-a725-0ef9-f6d3-ff2810da9e7a@gmx.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]

Hi,

the idea of migrating https://git-scm.com/ from a Rails app to a static
site has been discussed several times on this list in the past.

Thanks to the heroic, multi-year efforts of Matt Burke, Victoria Dye and
Matthias Aßhauer, there is now a Pull Request, ready for review:
https://github.com/git/git-scm.com/pull/1804

This Pull Request is not for the faint of heart, mainly because of the
sheer amount of generated pages that are committed to the repository (such
as the book, the manual pages, etc, a design decision necessary to run
this as a static website).

These pages are generated by GitHub workflows that are intended to run on
a schedule, and the scripts that generate them are part of the Pull
Request. For that reason, I do not consider it necessary to review those
generated pages, those reviews have been done in the upstream sources from
which the pages were generated.

At this point, the patches are fairly robust and I am mainly hoping for
help with verifying that the static site works as intended, that existing
links will continue to work with the new site (essentially, find obscure
references to the existing website, then insert `git.github.io/` in the
URL and verify that it works as intended).

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/.

Thank you,
Johannes

             reply	other threads:[~2023-11-17 13:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 13:25 Johannes Schindelin [this message]
2023-11-17 16:26 ` Migration of git-scm.com to a static web site: ready for review/testing 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
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=6f7d20b4-a725-0ef9-f6d3-ff2810da9e7a@gmx.de \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --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).