Attività e strumenti
Prima di iniziare
Prima di tutto
- Chiunque può contribuire a UserBase, ma è consigliabile creare un account. La pagina Avvio rapido ti spiega come registrarti e connetterti.
- Sii consapevole che che il tuo contributo verrà gestito secondo le licenze Gnu Free Document Licence e Creative Commons. Fai clic sulle immagini nel pannello di navigazione per leggere i dettagli.
- Utilizza la pagina Discussione per comunicare con gli altri contributori o per chiedere aiuto.
Pertinenza
Il tuo contributo dovrebbe riguardare il software KDE, direttamente o indirettamente. Pensato quindi:
- per i nuovi utenti, come aiuto per iniziare;
- per gli utenti comuni, per imparare nuove funzioni e per suggerimenti;
- per gli utenti esperti, ma utilizzando sottopagine.
- Non per gli sviluppatori: Techbase è il sito a loro dedicato.
Come contribuire
Update Existing Content
- Update an image, replacing an outdated image with a newer one.
- Create a screenshot
- Modify existing content, fix a spelling, clarify a description, add more details.
Add New Pages
- Create a new page, showcase an application, introduce a new concept.
- Write a manual. You need to know an application quite well, and probably to be in contact with the author. We can help you.
Working with Languages
- Preparing a page for translation needs more patience than skill. If you can spare short periods of time, frequently, this is a very helpful task.
- Translate a page. You need to be fluent in a language, but not a professional translator to translate a wiki page. Translating manuals is the skill of a special team.
- Translate with Off-Line Tools. Get the essentials for Gettext and Import.
- How To Convert UserBase Manual to Docbook gives you an insight into the process that takes place on your finished manual.
Remember
It's important to be consistent, so here are some general rules:
- Take care with heading levels - we start at second level (Mediawiki uses top level for page-name), using "=="
- Make sure you refer frequently to this page and to typographical guidelines
- Check if all table cells have space after the pipe character. This rule conforms with traditional wiki formatting.
- Make application name formatting consistent (avoid using Amaroks, do use Amarok's).
- For screenshots and other images, .png format is preferred. The Upload page lists the file types that are acceptable. .
- Remove all non-printable characters from image names.
Hints and Tips
Some Preferences that will help -
- If you don't have [edit] links against the sections, open your (in the section of the sidebar) then look for and in the set
- While you are in those settings, enable - while you are editing you can glance at the original display for reference
- The default display is to show the preview first, with the edit box below. If you prefer the edit box at the top you can change that setting in the same place