Extend styleguide with content structure and audience

[verytactical]

• We mention types of articles, but do not mention how exactly they should be organized. Describe structure of documentation
• We should be explicit that this is a documentation only for developers. Add a disclaimer about this somewhere in the beginning of styleguide.

[Gusarich]

@verytactical

We mention types of articles, but do not mention how exactly they should be organized. Describe structure of documentation

isn't this what you mean?

• https://github.com/tact-lang/mintlify-ton-docs/blob/3dc9be48efec3ba196c89c130c9aa8d38aaca12f/contribute/style-guide.mdx?plain=1#L24-L28
• https://github.com/tact-lang/mintlify-ton-docs/blob/3dc9be48efec3ba196c89c130c9aa8d38aaca12f/contribute/style-guide-extended.mdx?plain=1#L667-L678

[reveloper]

I'm trying to say that we expect readers to have not only basic programming knowledge from an educational program, but also experience with JavaScript (for the front-end) and Java (for the back-end). One to two years of experience are recommended for innovative contract development.

I think our target audience should be specified for writing the most details for the recommendation. I think a good source for the target audience: https://developers.google.com/tech-writing/one/audience?_gl=1*dskyej*_up*MQ..*_ga*MTA0MDk2ODM2My4xNzU4MjU3OTkz*_ga_SM8HXJ53K2*czE3NTgyNTc5OTIkbzEkZzAkdDE3NTgyNTc5OTIkajYwJGwwJGgw