[Idea] A guide to initiate newcomer devs to our language

Suggested by user `soushi88` on Discord:

> Maybe it could be nice to assume the current naming while proposing a nice guide to initiate tech people to this wor(l)d ?

It could be a fun, lighthearted way to get devs up to speed while not needing to change our language. An alternative to the thorough but dry glossary.

Start by reviewing the existing thorough glossary mentioned in the issue and compare its coverage and tone with the proposed lighthearted newcomer guide. Define the audience, structure, terminology, and scope before identifying documentation files to change. Done means the guide has an agreed purpose and content plan, but the issue does not yet specify acceptance criteria.

Written by the indexing model from the issue text.