2 ms·

Guidelines is the correct word.

• microflash 3y ago
  Unfortunately, "guidelines" can also be weaponized as something that's optional, something subject to exceptions, leading to so many exceptions that the guidelines themselves are forgotten, and eventually outright ignored. Nevertheless, this is the term I've been using lately, mostly with a statement of guideline followed by its benefits or reasoning behind it. It is gentler and inoffensive to those who have tender sensibilities, thus enabling a productive embracement of the guidelines, a useful critic on them or an eventually better guideline, instead of inflamed egos inciting flamewars.
• haswell 3y ago
  I think guideline is a good word, and I’ve used it to describe/summarize the purpose of the “best practice” content I’ve written. But it’s not always a good top level category. This will depend on the product and the space used to publish the content. I worked on content that was published to a developer portal, which also had an integrated community, and this community had published guidelines for participating. In terms of content discoverability/SEO, guidelines is often overloaded. I started to look at this content as a direct extension of the overall product. And when thinking about naming things, it often most effective to meet users where they are. The technically correct label on a button is often not the label that actually resonates with users. Same goes for content, IMO (within reason). I think most of this is solved by a summary/abstract describing the content and what the user should take from it.