FANDOM


The Troye Sivan Wiki is meant to be a place where both fans of Troye and strangers to his work can learn, contribute, chat, and create. Part of the reason why a wiki can thrive because of its community, which is why we take measures to make sure that our community is a friendly one. Below are policies and guidelines we've enacted to ensure that all users on this wiki are treated with kindness and respect. If you still have questions about our policies or if you wish to request temporary editing access of this page, please contact an admin please.

Community

Wikis are all about working together, and that takes care, tolerance, and understanding. Treat people well, and talk to each other, and you will have a better chance of building a great community together.

Be Respectful

We don't allow homophobic language, ethnic slurs or religious hate. That means no language or content that encourages hatred or violence, or that disparages others on the basis of their race, gender, sexuality, religion, country of origin and so on.

Look Out For Each Other

It goes without saying that harassment, threats, bullying and intimidation are not okay. But try to go further, and speak up for others if you see them being attacked - not by attacking back, but by trying to calm the situation and help people get along.

Be Cautious

The Internet is a wonderful place but it's not the same as the offline world. You can never be sure who you are talking to online, or that they will always be friendly. So always protect yourself by keeping private stuff private. Your real name, address, school name, photos of yourself or your friends and family - all of these are things you should think twice about sharing. Remember, once it's out online, it's out and you can't get it back. Just ask Beyonce! Respect people's privacy It's especially important not to try and get personal or account info from people under 18, but it's often unnecessary and even rude to bother anyone for information about their offline life.

Editing

Build, build, build!

Communities work best when they have lots of interesting stuff to bring in new readers and convert them to new editors. So the more good content you can add, the better chance the wikia has of becoming successful. Remember that the content is what brings the community to the wikia; it is what you have in common, so focusing on that will help bind the community together

Attribute fairly

Wikia believes in the open source movement. Creating content that can be shared and enjoyed by others is a big part of what we do. But, that doesn't mean we should ignore other's rights. Whether you use text, or images under license, with the author's permission, or under "fair use" guidelines, it's always polite to give the proper attribution.

Don'ts

Illegal Content

Don't do anything illegal on Wikia, or encourage other people to.
That includes linking to illegal content (including links to copyrighted movie or TV shows) or creating a wikia that gives instructions on how to do something illegal.

Explicit Content

Don't post explicit or inappropriate content
For text, content that just mentions characters have sex is usually OK. But content that describes exactly how they have sex, is not.

Impersonation

Don't try to fool people into believing you are someone else.
That means don't impersonate other users, or anyone else - including famous people. Of course, some wikias are all about roleplaying or parodies, but those aren't meant to mislead people. You can role-play as Batman, but don't convince people you are Batman (what do you mean he's not real?)

Spam

Don't spam.
It's not okay to use Wikia to advertise other sites or services. A link to another site might be useful information on a page, but not if it's purpose is to advertise that site. Even worse is if you are adding the link repeatedly, or in places where it's totally off-topic "Spam" can also mean repeatedly pasting the same thing on wikias or in chat, even if it's not an advert.

No one likes to think they have to follow rules, but rules have their place in most organizations. Wiki communities are no different. Wikis often have policies that talk about what kinds of pages you can write, how you should act on chat, or how and why an administrator can block you. In general, policies are very simple codes of conduct that make sure wikis run as smoothly as possible. What should policies be like, though?

Policies should be created when there's a need for policies. They form a manual of style for pages so people know how to write. They make sure that vandalism, spam, and trolling are known to be unacceptable. They ensure that people are polite and respectful to one another on chat. There are all sorts of policies that can be created, but it's important to remember a few things before you set about creating them.

A policy should accomplish something

Policies should be clear and concise overviews that guide the editing process and the interactions of the community. To do that effectively, policies need to be practical solutions to actual problems. That's something communities often make the mistake of forgetting. One notable community, which will remain nameless, would often create policies for unimportant issues; you could not have more than 20 user-boxes on your user page, you could not have more than one video on your user page, and you had to have a category on your article or the entire article would be deleted.

Do those sound like real problems, and do their solutions seem necessary? They were all made based on the preferences of the admins rather than the need to fix real problems. That brings us to another very important point.

Keep It Simple, Stupid

No, you're not stupid, don’t worry! The KISS (Keep It Simple, Stupid) method to success is a way of making sure that your rules and things you want to teach people are as simplified and understandable as possible without losing their meaning or value. It's an incredibly valuable concept that should guide your policy creation and management.

In the case of those unnecessary policies that were already mentioned, one thing you want to avoid is "instruction creep." The idea of instruction creep has been around for awhile, often in corporate settings, and it's what happens when rules and regulations increase in size and quantity until they can no longer be readily understood or effectively enforced. This can hinder the success of a community, because it is directly contradictory to the KISS method. The primary way it hinders success is that users either can't comprehend that many policies, or they simply choose to ignore them when they see so many. Who wants to read 20 policies - not just 20 rules, but sets of rules - anyway?

Let's paint a scenario that sometimes occurs. Say you have a lot of policies. What happens? Often, people don’t read them. That means they miss some of the most important ones, like manuals of style that teach them how to create and format pages. You then have a situation where people are creating lots of pages and edits that don't follow your guidelines. What is the usual reaction to this by administrators? Unfortunately, unless they've come to recognize that they have too many policies, it is likely to add more policies or begin blocking people - both of which go against what the community needs to succeed.

If you need to create policies, consider whether those policies are necessary. Look at the area of wiki editing or community interaction that the policy aims to cover. Is that area a problem? If not, then don't try to fix what isn't broken. If it is a problem, is the policy you're implementing a practical solution? If not, consider trimming it down. This leads to another important point.

Set realistic expectations for your community

If you expect people to quickly learn your policies, don't give them 20 new sets of rules to read right off the bat. That's not a realistic expectation to have of anyone. This is especially important for new communities. If you've just founded a community, then you don't need a lot of policies. That can be very harmful to the future of your community if you try to control everything at once, especially when there's nothing there to control yet. Let your community evolve naturally, and fill in policies when and if they are needed.

You also need to remember the nature of wikis, because they're not like other websites. A wiki is not a blog, it's not a social network, and it's not a message board. It's a little bit of everything all wrapped into one, so it's a very unique format. Because of that, it inherently has a learning curve. Not everyone is going to learn at the same pace, and that pace can very much be affected by how many policies a community has and how simple or complex those policies are. Some admins are fond of thinking "I learned fast, so you should too!" In reality, though, that's a meaningless statement. Not everyone will learn at your preferred speed, so don't expect them to. Everyone is different, and everyone should be given a chance to learn at their own pace so long as they're not disrupting the community. That's how new, inexperienced users become great editors.

Final thoughts

In summary, keep things simple. Don't try to solve problems that don't exist. Avoid instruction creep. Everyone learns at their own pace, so make sure you're making things as easy as possible for people so long as it doesn't detract from the business of the community.

Do you need further help in crafting your policies? Feel free to check out our Community Forum or Community Chat, where users from across Fandom can give you the assistance you need.

Read more

Further help and feedback

Community content is available under CC-BY-SA unless otherwise noted.