The man page file was contributed by community, but I'm not familiar the man page file syntax.

Any contribution is welcome.

Neofetch used help2man to generate a manpage using output from --help. Another option is to use pandoc to convert from any format (eg. markdown) to a manpage.

I think that pandoc would be best because then you can convert the JSON schema to a manpage too.

Any documentation is better than none and is the Man page really the best place to document what really should end up in the config.jsonc file? As such, I suggest just keeping the current release version and the JSON Schema pages in sync. Right now the latest version of Fastfetch is v25, released 5 days ago while the JSON Schema document was last edited two weeks ago, Cheers Mac

I fixed the man page I will send a pull request

To someone wants to fix this

1. We don't need the generated .1 file. We need a (python?) script to generate it, in order to regenerate it in future release.
2. It should be generated directly from https://github.com/fastfetch-cli/fastfetch/blob/dev/src/data/help.json, not fastfetch --help

I'll see if I can have a go at it this weekend or next week. I've studied a bit of the format used for manpages (roff) to be familiar with it and I've seen other projects generate their manpage using a python script as you mentioned (also thanks for mentioning that help.json file, that really makes things easier).

I see that my pull request was outdated and not in the way that was requested, I will take a try at making a script to fix this issue