Draft: start of document for certain implementation details about obofoundry.github.io

[nataled]

@cthoyt that was the first method considered and ultimately rejected. You're only seeing part of what this list will be, and some has nothing to do with issues. Also, we don't want to create a label for a one-time project.

[nataled]

From issue tracker (some of these are potential additions not necessarily proposed for a principle):
Term adoption #2330 (also #2324)
External axioms #1443 & #1991 | these might form a new "what to do with terms" principle (we can make it p14)
Versioning term identifiers #1347 /
Linking term to discussion on tracker #1097
Language tags #479 (also #325)
Synonym types #2450
Ontology root terms annotation #2149
Short ontology descriptions #1968
Documentation for license #1840
Publications metadata #1671
Ontology merging #1548
Discourage BFO shadow classes #1539
Exemplar classes #899
Ignoring NCIT (no issue, but has come up that NCIT is not well-formed enough to be a concern re: things like overlap)
Ontology metadata requirements #1365
Standardized xref prefixes in ontologies #525
Proposals here: #482 (comment)
Ontology subsets documentation #466
Referring to taxa not in NCBITaxon #434
Standardizing how imported ontologies are noted #424
Document how to add logo #72
Modeling metaclasses #2454 (thanks @cthoyt, that's a good addition)

[cthoyt]

@nataled simplest way might be to create a new label for the issue tracker / PRs

[cthoyt]

Another one for this list: #2454

[nataled]

Bill H: Reviewed principles 1-8. No eligible text except for 'Term adoption' in P8.
Hande: Reviewed last 5. No eligible text.
EWG: Reviewed P9 & P10. No eligible text.