'Use Narrowest Category possible' in wiki/Help:Categorization plus more

Question

Is there an area that lists published 'best practise' to users in order of importance (the best-practise entry that generates the least real-world work, should be at the top) and a reminder to adhere regardless of honor/honour code to it?

https://www.wikitree.com/wiki/Best_Practise:narrowing or https://www.wikitree.com/wiki/BestPractise:narrowing

I am using the FQDN path each time as per https://www.wikitree.com/wiki/Help:Categorization

---

With regard to convention and 'accepted convention' may I suggest https://www.wikitree.com/wiki gets relayed to https://www.wikitree.com/wiki/Category:WikiTree_Help for the few users that type URL's in. You could try it out on a http version first so it does not use a certificate.

The above can be used as a convention and used site-wide as it will stop/reduce

1. The need to ask end users to make an action (challenged people-mental and physical)
2. The need to type up a http/s page
3. Reduce the 'how many clicks to target?' result (Rule of 3!)
4. Stop 404's which bots and crawlers use in their data harvesting. Use a 301 forward/redirect to retain 90 to 99% of link equity.
5. The difficulty of satisfying HTML5 and CSS3 demands. Currently https://www.wikitree.com/ has 46 errors and 14 warnings. To balance this out it has a 100% result for Adobe Flash not being present. :-)

---

Psychologically most people wish to be or do the best thing. Using best-practise will attack, at root cause level, the things that generate lots of work (eg: 

• does wikitree allow Gedcom uploads or not; and if it does why does it state it does not and does it give strong advice on cleaning up trees before exporting from 3rd party apps/databases and then importing Gedcoms to wikitree, 
• merged profiles
• delinking
• 'dupes' or duplication of tree entries (surname/givenname/middlename) 
• text analysing for cuss/swear words etc
• forceable correction of words typed in ALL UPPERCASE (can be used to attempt to acquire dominance/importance as known as 'shouting' in messaging systems) to all lower case. (C++ usues 'is' and 'to' with 'upper' 'lower' 'alpha' 'digit' etc. Example: 

/* isupper example */

#include <stdio.h>
#include <ctype.h>
int main ()
{
  int i=0;
  char str[]="Test String.\n";
  char c;
  while (str[i])
  {
    c=str[i];
    if (isupper(c)) c=tolower(c);
    putchar (c);
    i++;
  }
  return 0;
}

Answer 1

Philip, I am trying very hard to understand this post, but is there something specific you're asking? Please explain this further.

Comments

Is there an area that lists published 'best practise' to users? Asking them to do things in a certain way to stop and reduce workloads being created that are not needed?