section on presenting JSON, SQL and code in other prog. languages (#79)

[Man1ek27]

Closes #79

[slayoo]

🚀 reviewers: @mshupliakou & @filbet4

[mshupliakou]

screenshot of the reviewed section from the pdf generated on CI

[mshupliakou]

Hi! Thank you for the great Pull Request. The new section on 'Code listings' is very well-written, easy to understand, and fits perfectly into the handbook. Great job explaining why we should use code blocks instead of screenshots and keeping the explanations concise!

[mshupliakou]

Please don't forget to add your name to the colophon-authors

[mshupliakou]

Consider suggesting keywords like code listings, syntax highlighting, JSON validation, SQL linting to be added to the README file

[filbet4]

Nice addition to the handbook. The section provides practical examples for several common formats (JSON, SQL, and other programming languages), making it easier for readers to apply the formatting conventions consistently. The examples are clear and easy to follow. Great section!

[Man1ek27]

Please don't forget to add your name to the colophon-authors

Thanks for the reminder!

[Man1ek27]

Nice addition to the handbook. The section provides practical examples for several common formats (JSON, SQL, and other programming languages), making it easier for readers to apply the formatting conventions consistently. The examples are clear and easy to follow. Great section!

Thanks for the review :)

[Man1ek27]

Consider suggesting keywords like code listings, syntax highlighting, JSON validation, SQL linting to be added to the README file

Good advice, thanks a lot. I will consider it.

[slayoo]

Few more comments:

• the hint "use line numbers only for ..." is not supplemented with info on how to enable line numbering
• the hint "use the most specific language tag ..." is not supplemented with explanation of what is a language tag
• it is unclear if the listing with output-dir: _book is just a random example or part of instruction on how to setup Quarto