Page data
Authors Emilio Velis
Felipe Schenone
Chris Watkins
Published 2012
License CC-BY-SA-4.0
Derivatives Ayuda:Introducción
Impact Number of views to this page. Views by admins and bots are not counted. Multiple views during the same session are counted as one. 14,627

This list of help topics will help you set up your Appropedia account and start contributing. If you cannot find what you were looking for, please open a topic at the talk page. In a rush? Check How to use Appropedia for a crash course on the basics of using Appropedia. Always feel free to connect by email at support[ᵃᵗ]appropedia[·]org

How to edit Appropedia

For a crash course on editing Appropedia, check Help:Editing. You can also see the following guides for examples to add and edit content.

Using Appropedia as a tool

These are some use cases for Appropedia as a research or educational tool.

Documentation workflow

Learn the basics of documenting on Appropedia from start to finish at Help:Documentation workflow. Here are some resources to get you started.

Where to begin[edit | edit source]

One great thing about a wiki is that it's straightforward to contribute. You don't need to set aside a day or even an hour to start contributing. Being a wiki, you can come back anytime and add another sentence, paragraph, or section. Others can also add to it. Just be bold!

At the beginning, you don't need to worry about formatting or categories —all you need to do is start editing. It is much more important that an entry is clear and full of information, rather than stylistically perfect: in Appropedia the substance is far more precious than the form. Writing well is an art and Appropedia, while it isn't a novel, is still a work with a purpose (knowledge, its collection and dissemination).

The purpose of an Appropedia entry is to inform people from all backgrounds: therefore, as already mentioned, the substance is more important than the form. However, when you write, you should always keep in mind the recipient of what you write. An entry is meant to be read by everyone, therefore it is recommended to write in a flat and simple way, without big words or phrases in technical jargon.

See also[edit | edit source]

In other languages[edit | edit source]