All committers have signed the CLA.

Go through the style guide and correct the pages.

Go through the style guide and correct the pages.

What exactly wrong? I checked everything

Go through the style guide and correct the pages.

What exactly wrong? I checked everything

Start with the section "Example commands". This is not the syntax we use.

The build for this PR failed with the following error(s) at commit
cbf517558592c1d414289539a0ed484a76716f4a:

pages.ru/common/doom.md:
Error: Parse error on line 8:
...m:`{{sourceport}}`.`- Запустить с вы
---------------------^
Expecting 'NEWLINE', 'TEXT', 'DASH', 'BACKTICK', got 'COMMAND_TEXT'
pages.ru/common/doom.md:7: TLDR103 Command example is missing its closing backtick

Please fix the error(s) and push again.

Finally all checks passed

Hi @sapbotgit, thank you for this contribution!
More Information Link: The current link points to the ZDoom wiki. I think a more general link like https://doomwiki.org/wiki/Source_port_parameters would be more useful for users of any source port.

I was thinking the same. If some user is a first timer to doom server hosting, the word "sourceport" might mean nothing to them. I agree with Ivan that the best solution is likely to include zandronum-server as the binary name if it's the most popular sourceport and add to the header "> zandronum-server can be replaced with any alternative sourceport"

I've been looking into the {{sourceport}} placeholder. Am I correct in understanding that the arguments for multiplayer or modding can differ significantly between various source ports (like GZDoom vs. Zandronum)?

Almost no. Even Zandronum supports -host, -join.

That leads to a more specific point I wanted to discuss. To follow up, if we were to use a specific binary like {{path/to/zandronum-server}} instead of the generic {{sourceport}}, would all the examples on the page still work as written? I'm bringing this up because this PR is linked to the "Let's document: Headless game servers" issue (#17125). My understanding is that Zandronum is a perfect fit for this, since zandronum-server is a true headless binary (no graphics, no client). On the other hand, ports like GZDoom are peer-to-peer, where the host is also a player rendering the game.

zandronum-server has custom cli parameters, and i think more wider and better definition will be {{path/to/doom}}. (Answer/react to me if agree)

I don't think the custom parameters matter if we don't document them.

I thinked something about currently documentating standart CLI parameters, then documenting in it's own page zandronum's.

Might be useful. But lets get this page done first.

Might be useful. But lets get this page done first.

So, what, {{path/to/doom}}? Or you got a better idea?

Just {{zandronum-server}}. It's a sourceport so it's available in package managers.

Just {{zandronum-server}}. It's a sourceport so it's available in package managers.

But what about others? Maybe add in description note that you can replace {{zandronum-server}} with your port? There are SOOO much other ports.

Yeah, that was my original idea as well. Add something like > `zandronum-server` can be replaced with any sourceport.

zandronum-server can be replaced with any sourceport.

One question, zandronum-server on hosting, just zandronum on joining or what?

And I believe using zandronum-server allows us to keep the page name as doom, as this would align with the guidelines in issue #17125. This way, we also avoid creating extra pages.

zandronum-server can be replaced with any sourceport.

One question, zandronum-server on hosting, just zandronum on joining or what?

Not sure if I understand the question.

zandronum-server can be replaced with any sourceport.

One question, zandronum-server on hosting, just zandronum on joining or what?

Not sure if I understand the question.

I mean, as i understand zandronum-server is headless. So, for CLI parameters on joining/playing the game i should just put zandronum (not headless, full port)?

zandronum-server can be replaced with any sourceport.

One question, zandronum-server on hosting, just zandronum on joining or what?

Let's simplify and stick to the goal of the "Headless game servers" issue (#17125).
Here is the plan:

1. Focus only on the server-related commands.
2. Replace all instances of {{sourceport}} with {{path/to/zandronum-server}}.

zandronum-server can be replaced with any sourceport.

One question, zandronum-server on hosting, just zandronum on joining or what?

Let's simplify and stick to the goal of the "Headless game servers" issue (#17125). Here is the plan:

1. Focus only on the server-related commands.

2. Replace all instances of {{sourceport}} with {{path/to/zandronum-server}}.

OK

We can always add more examples later. Better to focus the headless nature of gameservers first as they're more likely to be used from the terminal.

We can always add more examples later. Better to focus the headless nature of gameservers first as they're more likely to be used from the terminal.

ready

Highlight the line you want to change and then press the button next to "Preview" to suggest a change.

the placeholders in the Russian version should be translated, as per the project's style guide.

- `{{zandronum-server}} -iwad {{wad}} +map {{map}} -host {{players}}`
+ `{{zandronum-server}} -iwad {{wad}} +map {{карта}} -host {{число_игроков}}`

- `{{zandronum-server}} -iwad {{wad}} +map {{map}} -host {{players}} -deathmatch`
+ `{{zandronum-server}} -iwad {{wad}} +map {{карта}} -host {{число_игроков}} -deathmatch`

fixed