Integrate git.github.io

[To1ne]

git.github.io has been the site for people contributing to Git. But it also hosts "Git Rev News", a monthly(?) newsletter about Git. We should merge that into the website.

See also git/git.github.io#729

[alvin-dennis]

How can/should we integrate

[alvin-dennis]

Also y not migrate the current hugo site to nextjs or smthg while keeping the same ui

[dscho]

y not migrate the current hugo site to nextjs

And, pray tell, why would we want to do that? We just converted the site from a Rails application to a static web site so that the Git project does not have to pay for hosting, but the site can be hosted on GitHub Pages instead.

[alvin-dennis]

Nextjs can be hosted on pages. wont support api routes tho

y not migrate the current hugo site to nextjs

And, pray tell, why would we want to do that? We just converted the site from a Rails application to a static web site so that the Git project does not have to pay for hosting, but the site can be hosted on GitHub Pages instead.

[dscho]

Nextjs can be hosted on pages. wont support api routes tho

Sure. And it can be using Svelte, too, even with static sites.

The question remains, though, why spend that much effort?

For the Hugo migration, there was a good reason. We didn't do that because Hugo is such a nice word and also the first name of the excellent actor who gave us Agent Smith and Elrond. We didn't do it because it is a shiny new technology. We did it because we needed to save money, the site could be a static website, and Jekyll simply didn't perform well enough for the size.

So now we're talking in circles that we could put in a lot of work to... achieve what exactly?

[alvin-dennis]

Just a suggestion

[dscho]

Just a suggestion

I am still waiting for a rationale for that suggestion. These discussions cost time, you know? So I'd like to know why we spent time talking about next.js.

[To1ne]

How can/should we integrate

@alvin-dennis There are currently two possible ideas:

• Merge data in with --allow-unrelated-histories (see Moving to git-scm.com git.github.io#729 (comment) )
• Import the data just like we do with the Pro Git book (see Moving to git-scm.com git.github.io#729 (comment) )

I don't have a strong opinion on either idea.

[dscho]

There are currently two possible ideas

And a third one:

• Simply add links at the appropriate places to the relevant parts of git.github.io site, e.g. to Git RevNews from https://git-scm.com/community.

[alvin-dennis]

Thats a good idea.

[dscho]

Thats a good idea.

To be completely honest, coming from the person who suggested to use Next.js, that does not boost my confidence 😆