Welcome to kdarrow's series of guided lessons for general editing in the Vault Academy. I am glad you are here at Nukapedia and interested enough in editing to take these mini courses! I hope they will help in making editing more fun, efficient, and fulfilling for you.
Purpose[edit | edit source]
The first lesson consists of this long-winded document. I want to encourage you to think about our purpose, why you and I are here, among our editing peers and millions of viewers each week. We all love Fallout and want to make sure all the information possible is available to everyone, in an easily accessible and understandable format. A labor of love, really.
Collaboration[edit | edit source]
The wiki is based on the idea that all of us when combined have a wider breadth of knowledge than any one person individually. In addition, since our subject matter is fictional, we all contribute different viewpoints and experiences with the games and related information. Blending these varied understandings together is what creates a thorough and solid base of knowledge and strengthens our community.
Our work today is built on the legacy and effort of those who have come before us, many that are only names in an edit history, but important to acknowledge, remember, and appreciate nonetheless as we continue onward.
Assume good faith[edit | edit source]
A common sentiment here and across the wikis and for good reason. It means that we should always give the benefit of the doubt with other editors and assume the work they do is to help and not to hurt. The first interactions with new users are the only chance we have to make a good impression and encourage them to continue.
If you notice a mistake has been made, it is a teaching opportunity. Everyone has to have a first day, and taking the time to explain what they did wrong so they can learn and feel encouraged at the same time is beyond important. I remember my first day and how kind the editors were to me, despite my errors. I still make mistakes and ask questions, every day. No shame in it at all.
Even if you are new, there will always be someone even newer, and we should be patient with them. Newcomers will be unfamiliar with the guidelines, but are excited to join in and help. The policy pages will not make sense to them at that moment, even if they do read them. It is our job to guide them in a kind way and give them a chance to learn. On the flip side, if you see someone making a lot of progress, consider sending a compliment their way to keep them energized.
Ask questions[edit | edit source]
Always feel comfortable asking questions, no matter what. It is good to be both confident and learn from those more experienced. No one will be upset or think less of you for asking. Honestly when people ask me questions I kinda feel excited and my ego gets big for a little bit. Remember that it is ok to be wrong or not to know the answer to something. I am wrong a lot, I don't know things a lot, and I ask questions a lot, and this is all aok. Being receptive and approachable is important, even if it kinda sux a little. Hey look at us! A growing experience!
Don't feel insecure or upset to see staff members visit articles you recently worked on. Our job is to do this, with all edits! If we change anything, you can learn just from watching what it was. And if it looks bizarre, send a talk page message to chat about it - more on that soon. If we let you know something, it is only to help.
And remember, as your mentor, I will always be here for you and you can always come to me if someone is being disrespectful or pushy. I am really, really protective of my precious mentees, and we can learn how to navigate those tricky situations together, usually just by smothering with kindness. Woo! Additional growth!
Quiz 1 (Intro)[edit | edit source]
You get a freebie for your first quiz. Alongside this long narrative, I will give one assignment that will be ongoing, which is making sure the edit summary is utilized, underneath the text-addy-field when editing. You can explain briefly what your changes were which will serve to share your thought processes, as well as provide guidance to new editors, who can watch and learn in real-time.
This brings up the importance of keeping edit summaries constructive and polite, and that they stay on the edit history in perpetuity. Here are some examples of my expectations for mentees:
- edit summary: "terrible punctuation"
- edit summary: "remember to keep periods and commas inside of quotation marks"
General, loose guidelines I would like to see roughly followed:
- all substantial edits summarized
- most brief edits summarized
- no summary needed for minor changes, but check "minor edit" box
- all summaries polite, no exceptions
In the same general area of the edit summary, you can click to see what your edit will look like by clicking "show preview" and see the actual changes side by side with the previous version by clicking on "show changes." Selecting "this is a minor edit" if you are just say, adding a space. It says to staff that it is a tiny change that may be able to be looked at later on after review of larger changes.
Under preferences you can change a variety of settings, in editing section you can select "mark all edits minor by default" if that is your style. For all of my instructions and examples, I use the "source editor" option in case you want to match. Not required, though, just an FYI. You can have some fun changing your preferences around to find exactly what fits you best.
|Use edit summary box consistently and constructively||A+|