Merge pull request #378 from ipfs/add/code-persona

Add/code persona

Author: johnnymatthews

docs/community/contribute/code-persona.md

@@ -1,9 +1,16 @@
 ---
 title: Code persona
-sidebarDepth: 0
 description: Find out how to create interesting code examples, and keep the IPFS documentation consistent.
 ---
 
 # Code persona
 
-<ContentStatus />
+Docs can be confusing, especially for increasingly complex topics like IPFS. There are lots of moving parts and it's easy to get confused. Example use-cases and code-blocks often serve to make things easier to understand and allows for a more _hands-on_ experience. However, examples that come from different use-cases and projects make it harder for the reader to understand the topic. The solution is to create a _theme_ for all samples to be based off.
+
+Having a single theme keeps code examples self-contained and consistent. It doesn't make the problems any less complicated or less technical, but it makes the reader need to _think_ less. The reader doesn't have to spend time continually re-visualizing the larger project at hand if the main project is something they're already familiar with.
+
+## The theme
+
+The _interplanitary_ part of _InterPlanitary File System_ comes with obvious space connotations, so it makes sense that example use-cases and code examples are based around the final frontier. With this in mind, when creating code-examples to illustrate your ideas, try to keep them within this space theme.
+
+We can expect the vast majority of IPFS users to be familiar with the planets within our solar system and some of the more famous telescopes, satellites, and space rocket names. However, it would help if you tried to stay away from more _exotic_ or niche planitary bodies. Not everybody is going to be familiar with the andromeda galaxy, and it may confuse some readers. Also, keep in mind that many language translators will be able to deal with common planet names like Jupiter or Mars, but may struggle with less common names.