Starbeamrainbowlabs

I wasn't aware of this issue before. As far as I was aware it was `os_name` first, which then falls back to `common`. The page resolution logic has been standardised...

Perhaps @zdroid, but that seems to me like more work that just contributing the first page lol :P

Sounds interesting. I think we agreed recently though to document PowerShell commands under `windows` rather than `common` since it's on Windows that PowerShell is usually used though? The other changes...

Using doublle quotes *everywhere* could significantly confuse pages. I think it's probably best to only use them: 1. When they are required for a command to function correctly 2. When...

That sounds good, but it's really situationally specific. While conventions exist, there are always exceptions to those conventions - and even then such conventions aren't implemented equally by everyone.

This is an excellent issue to raise. I think that compliance with the client specification might be a good place to start. What about if a client hasn't made progress...

> Of course, this requieres for our part to review every X months if the clients still accomplish the client specification or if there have had progress with the client...

We could even fill in which client spec version clients support? But that might be too much work. I really like the idea of automatically opening an issue when we...

@bl-ue that's an interesting idea, but even within the idea of a CLI client you'll have a job developing a universal client that works on all platforms: Windows, macOS, Linux,...

You raise some good points. We do have a reference client in Node.js over in the tldr-node-client repo. But writing a new client requires lots of effort and work -...