Improve documentation for website development

[ihhub]

Preliminary checks

• I've checked that there aren't other open issues on the same topic.

Describe the problem requiring a solution

After reading the documentation I noticed that there are some moments that developers might find not clear so it is important to make the documentation as clear as possible.

Describe the possible solution

This is a list of improvements we can do:

• specify required / recommended version for each tool or package. Only Ruby has this
• a developer on macOS doesn't need to install innoextract so running brew bundle --file=script/macos/Brewfile.dev_tools makes not sense. We should replace this command with brew "clang-format" and specify why we need this. Later in the document we run npm based linter, so do we even need clang-format?
• we should replace command git add . with git add docs as a web developer will work only within docs directory. This reduces the risk of committing unwanted changes
• should we use a link to the official Jekyll installation rather than explaining how to set it up for a single OS?

Additional info

No response

[oleg-derevenetz]

so do we even need clang-format?

Yes, we still need the clang-format to format the *.js files. npm run format-js just runs this.

we should replace command git add . with git add docs as a web developer will work only within docs directory. This reduces the risk of committing unwanted changes

By the time these commands are executed, the developer is already in the docs directory. Otherwise, he would not have been able to execute the previous npm run commands. git add . will work in either case, but git add docs will not work if developer is already in the docs directory.