I might tackle this page in a few weeks, but why on the static website? Wouldn't this make more sense on-wiki?

In T112#3916, @Dmehus wrote:

I might tackle this page in a few weeks, but why on the static website? Wouldn't this make more sense on-wiki?

The wiki is mainly technical documentation. The website is what's user facing.

In T112#3918, @RhinosF1 wrote:

In T112#3916, @Dmehus wrote:

I might tackle this page in a few weeks, but why on the static website? Wouldn't this make more sense on-wiki?

The wiki is mainly technical documentation. The website is what's user facing.

I suppose that's the case, but arguably, we need to be better utilize the wiki. For example, the "commands" page should be migrated to the wiki, as it's easier to update wikitext on-wiki than GitHub. So, I think we should have a larger discussion on the sort of the content we want on the website, and make it more of a landing page, linking to content elsewhere

as it's easier to update wikitext on-wiki than GitHub

But we're automating the documentation for commands

In T112#3920, @RhinosF1 wrote:

as it's easier to update wikitext on-wiki than GitHub

But we're automating the documentation for commands

Okay.