Good find, I think the link should be replaced with https://expressjs.com/en/guide/using-template-engines.html.

Honestly I think we talked about deleting the wiki someday. It is not at all well kept up and was mainly from the old days before all this stuff was on the website. I wonder if we should just delete it entirely?

Good find, I think the link should be replaced with https://expressjs.com/en/guide/using-template-engines.html.

In this case this page should be patched too, as it refers to the wiki to list the template engines, which then redirects the user to the deleted page (as seen above)

See Template Engines (Express wiki) for a list of template engines you can use with Express.

@kristofferjansson if you still need the content of the page, this is the most recent snapshot of the wayback machine that doesn't 404.

Hey @njanssoone 👋

Thank you for pointing it out. However, I agree with @wesleytodd on this. I believe there should be a single source of truth. And maintaining a single place is much simpler to keep it updated.

We should do the following,

• Make sure the website includes everything that has to be included from the Wiki
• Set the Wiki homepage saying users to read docs from the website
• Delete other pages from Wiki

@IamLizu, would you like to work on this and prepare a PR(s) for the content migration?

Edit: I transferred the issue for visibility

@UlisesGascon, sure, I will get started on this.

Hi guys, sorry I didn't see this sooner.

Yes, the wiki has a bunch of old/irrelevant info that should be deleted. The original distinction between the wiki and the expressjs.com doc site was that the wiki was mostly for WIP notes and for internal info, as well as a kind of archive for low-value material that was not deemed important enough to maintain or translate.

The easiest thing to do would be to delete anything that no longer has any value or is inaccurate, and clearly mark the rest as ARCHIVE or whatever. Moving it to the doc site will incur additional maintenance and potential translation burdens that I' doubt is worthwhile.

There is also a wiki for the expressjs.com repo with one or two things wiki that we should keep somehwere. For example the Documentation style guide -- this is pretty "down in the weeds" info for doc contributors; not sure it belongs on the website. Much of that page is English-specific, too; translation would be problematic. When I have a moment, I'll review that wiki for anything else worth keeping.

I see @IamLizu opened expressjs/expressjs.com#1565. I'll comment there, too.