As crossposted from the main site: I. Basic Guidelines Guides should be: Legible in grammar and spelling Readable in content–a good general rule of thumb is to assume the reader has little to no prior experience in the subject you are discussing. More than just a suggestion or theory–have some nuance of “how to”, if not detailed steps Detailed, with explanations of why such steps are being offered and what might be expected Free from guidance absolutes (e.g. “My method is the ONLY way to do things”) II. In Detail A. Expectations The guides section of Tulpa.io is intended to promote free exchange of information from diverse perspectives and eclectic approaches to the process of developing and interacting with Tulpas. These guidelines exist to help contributors of all kinds meet this intended goal. A.1. The Value Of Subjectivity We understand that individual guides will be informed by personal perspectives and that authors will use their own interpretations when offering instruction on a topic. We encourage the submission of guides by different authors who approach this instruction from their own personal experience. Our community is diverse in this way, and we want to make resources available that are able to satisfy and represent that diversity. A.2. A Platform For Learning That said, guides submitted to Tulpa.io should be written with education as the primary intent. This guides section is not to be used for the purpose of advertising yourself or advocating / denouncing any particular explanation for the phenomena of Tulpas or plurality in general. Your opinions can and should be used to inform the way you offer your advice to others. They should not, however, overshadow the advice itself. Comments, too, should aim to be constructive. They should be framed from a personal perspective first and foremost; keep in mind that tulpamancy is a highly subjective process; you are welcome to state when you did not personally find a guide helpful and are encouraged to explain why. However, just because one method does not work for you, it does not mean the guide serves no purpose to anyone. Guides should be judged by their underlying logic and comprehensiveness first and foremost. Attempting to invalidate methods others have found helpful will be considered a form of derailment. B. Guiding Your Guide Any piece of technical writing can be improved with a few key features. Understanding these features and how to apply them will allow you not only to better reach the people who need your guide, but also communicate to them as effectively as possible. B.1. Who Are You Guiding? Guides exist to guide. This simple, obvious statement comes with a very important implication – that somebody out there wants to be guided. Understanding who this person is and how best to address them is an important step that will inform the rest of your work. The content of your guide will be written with a particular audience in mind, even if that audience is not immediately clear to you. This audience may be obvious – a guide on possession will be written for people who want guidance on possession. That said, there is nuance in this. Is your guide written for people who can already possess, but want to expand their skill? Is it written for someone who cannot possess but is interested in trying? Is it written for someone who has never heard the term before? Each of these audiences will come with different expectations, and you should try to make it easy for them to know whether your guide is for them, if nothing else. B.2. How Will You Guide Them? Well-organized, clear writing is important when offering instruction. While the exact structure you choose for your guide is your decision, it should be easy to follow from one point to the next without too much amendment or clarification outside of the guide itself. Keep an eye out for typos, grammar mistakes and awkward formatting. Production errors like these can have a very real impact on how well a reader can understand what you’re trying to say, and whether they’re willing to spend the energy trying to parse what you’ve written. Make sure you define your terms, especially if you intend to use your own. Someone reading your guide should be able to understand the words you use in it. You aren’t obligated to use certain terms if you are used to/prefer others, but we strongly encourage you understand the terms listed in our Terminologies page. If you do use your own terms, please at least compare them to commonly understood terms like the ones in that page for the sake of clarity. B.3. Who Guided You? Offering references to material outside of your guide is a simple, easy way to offer extra help to anyone who still has questions after reading. Try to include things that helped inspire the advice you’re presenting, or links to related topics. Not only does this turn an otherwise simple guide into a reference for further reading and consolidate resources that others may not have been exposed to, but it also helps give your audience a clearer picture of where you’re getting your information and how you’re interpreting it. If your audience is able to see some of your source material they’ll be in a better position to understand the advice you’re offering, and may even be able to come up with new ways to apply it that weren’t included in your guide! A little background can go a long way.