Manual:MediaWiki feature list/it

Questa pagina contiene una lista di contenuti del software MediaWiki. A seconda di come vorrai usare il tuo wiki, puoi sceglierne di installare altri. Il software di Wikipedia ha molti contenuti utili, nati dai bisogni degli utenti e da idee degli sviluppatori; ma contenuti extra significano complessità extra! Prima di decidere di usare MediaWiki, guarda anche gli altri software wiki (vedi questa lista o questo confronto) e vedi quale di essi soddisfa meglio le tue necessità.

Richieste di nuove features vanno fatte a Bugzilla.

Do I want MediaWiki?
MediaWiki software and extensions have features and benefits, strengths and weaknesses, pros and cons, and in spite of anyone ' s intended purposes, MediaWiki software and extensions can be used for unique, clever, inventive purposes unforeseen by the original programmers or other installers. Here is a brief list of MediaWiki features and benefits. If you develop an equivalent list of your own goals and resources, you can compare this list to your list and see where there ' s a match, or mismatch. Need more help deciding? There are open discussion groups on the web, and "talk" discussion pages behind each main MediaWiki page where you can seek connection with other people ' s experiences.

Note: sample feature list from pages 13-14, in the book "MediaWiki Administrators ' Tutorial Guide: Install, manage, and customize your MediaWiki installation" by Mizanur Rahman, 2007 http://www.packtpub.com/

Please enhance and expand the above table ' s features and benefits to assist visitors to best know what they are getting into. Thanks!

One recurring problem is that system administrators decide to create a wiki, without taking into account many issues. After filling out the previous table, ask yourself the following questions, to see if a wiki is the right software for you:
 * 1) What is my site's intended purpose?
 * Wikis are ideal for collaborative editing and creation of content; they are not very well suited for other purposes, like blogging. Consider whether a wiki is an adequate option for your goals.
 * 1) How many users will this wiki be exposed to?
 * With a few exceptions, installing wiki software is unnecessary when there is a very small group of people interested in editing the wiki. The larger the user base, the higher the probability a wiki makes more sense for you.
 * 1) How many active editors do I expect to edit my wiki?
 * Wikis, due to their open nature, require some maintenance. The larger the editor base, the more hands available to perform those maintenance tasks.
 * 1) What can I do with MediaWiki?
 * MediaWiki is an extremely versatile wiki engine; it is relatively easy to install, but more importantly, allows for the use and creation of extensions. These allow your MediaWiki installation to be extremely customizable with some knowledge of PHP. With the proper motivation, MediaWiki can be "abused" to do almost anything.
 * 1) Is MediaWiki right for me?
 * MediaWiki has its limitations. Currently, there is no support for WYSIWYG editing, so all editors need to learn wikimarkup. That presents a small barrier to entry. A more considerable limitation is that MediaWiki is not meant to be an access control list. MediaWiki raison d'etre is to provide open content; while recent versions have a much stronger security model, there are still significant gaps in individual-based security access. See Preventing access and Security issues with authorization extensions.

How should I configure MediaWiki?
If you have decided that MediaWiki is indeed an appropriate solution, there are still more things to consider. These questions will hopefully help you decide how to configure your wiki in a way that will allow you to minimize issues in the longer term: See Manual:User rights and Help:User rights management for more ideas and information.
 * 1) Who do I want reading my wiki?
 * In spite of all the issues with individual-based page restrictions, MediaWiki can be configured to restrict or allow access to everyone. So, ask yourself whether you want everyone in the Internet to see the contents of your wiki, or if you want to restrict that privilege to those users who have created accounts in your wiki.
 * 1) Who do I want editing my wiki?
 * Perhaps the most common question is whether you want to permit everyone to edit your wiki, similar to the Wikipedia model. MediaWiki allows for fine-grained writing restrictions; you can allow unregistered users to edit talk pages, for example, but only allow users with accounts older than a certain amount of time to edit your content pages. You can restrict editing to sysops, or even to a custom user group you create and delegate.
 * 1) Who do I want creating an account on my wiki?
 * Depending on some of the answers to the questions above, you may want to decide to restrict who can create accounts in a wiki. You can allow anyone to create accounts; or you can even designate that privilege to administrators, who would then be responsible for creating accounts for new users via some process of your choosing.
 * 1) What powers do I want each user group to have?
 * One of the most important questions you need to answer is this one. Granting or removing privileges to a group can be extremely controversial in a large wiki, so having a good idea of what each user should be able to do is critical. Do you want unregistered users to create pages? Do you want registered users to create pages? Do you want wiki administrators to be able to block and delete pages, or do you want to extend more privileges to them? Who is responsible for granting more privileges? Who is responsible for removing them? Who do you want to have more fine-grained powers, such as oversight, checkuser, and rollback?
 * 1) Which extensions should I install?
 * With a few exceptions, extensions are easy to add, whether it be while installing the wiki, or after a couple of years of the wiki being run.

With those answers, you should be able to configure the most critical aspects of your wiki. You can proceed to beginning the installation process in your operating system.

Aspetto e stile

 * Link e collegamenti, l'aspetto dipende dalla skin.
 * Skin: Diversi modi di presentare il sito, possono essere espanse con i template PHPTal..
 * Monobook, una skin moderna con barre degli strumenti e chiavi d'accesso.
 * Vector, an even more modern skin with easier to read text, large amount of content space, and has an extension of the same name that adds drop down functionality to the menus.
 * User style: Gli utenti possono adattare il look del sito tramite il CSS delle loro pagine utente.
 * Segnalazione "Stub": Gli utenti possono decidere di modificare la visualizzazione del collegamento ad una voce sotto un certo numero di KB.
 * Versione stampabile degli articoli.
 * Auto-numerazione sezioni degli articoli (opzionale).
 * Collegamenti interni alla pagina (automaticamente generati per le sezioni e con ... ).
 * Indice automatico per articoli lunghi (opzionale).
 * Conversione automatica di codici ISBN in link a liste di libri.
 * Integrazione XHTML con output compatibile.

File multimediali ed estensioni

 * Caricamento file consente il caricamento di immagini o file sonori, via Special:Upload, vedi Caricamento file, I file caricati sono riportati nelle Ultime modifiche e registrati in Special:Log/upload.
 * Formule matematiche in sintassi LaTeX: vedi texvc
 * Ridimensionamento automatico delle immagini usando ImageMagick o libgd, semplice sintassi per l'uso di file.
 * WikiHiero per geroglifici egiziani (necessita componenti aggiuntivi)
 * EasyTimeline per linee del tempo (necessita componenti aggiuntivi)

Tenere traccia delle modifiche

 * Osservati speciali Ogni pagina ha un link segui. Usa Special:Watchlist per vedere tutte le tue pagine seguite modificate di recente. Gli articoli seguiti sono anche segnati in grassetto nelle Ultime modifiche.
 * Contributi utente nella sidebar di ogni pagina utente c'è un link con tutti i contributi dell'utente.
 * Ultime modifiche avanzate che accorpa tra loro tutte le modifiche ad un articolo.
 * Modifiche correlate: Vedi una versione delle ultime modifiche filtrata con le pagine linakte dalla pagina dove ti trovi.
 * Differenze Le differenze tra due edit sono segnate ed evidenziate. Additionally, a diff is shown during an edit conflict so you can see exactly what you need to reintegrate.
 * Real names. Gli utenti possono anche specificare il loro pseudonimo che vogliono usare per i crediti.
 * Crediti sulla pagina. Gli amministratori possono abilitare un paragrafo che visualizza chi ha lavorato ad una pagina.

Struttura e sintassi

 * Di default solo una parte del codice HTML può essere usata. C'è anche un opzione per consentirlo in toto.
 * Sintassi di modifica basata su UseMod, che supporta il mox di wikicode ed HTML. Non è supportato CamelCase
 * Namespace consentono la separazione del contenuto (per linkare un namesace, usa Namespace:Pagina ).
 * Discussione (Talk:): pagine separate per discutere sul contenuto di una pagina.
 * MediaWiki: namespace contiene i messaggi di sistema
 * Template: contiene pezzi di codice riutilizzabili. Templates may contain string variables which are replaced with certain values passed to the template from the calling page.
 * Inclusione di pagina arbitrarie in ogni namespace: . Vedi Templates
 * Link con estensione di parole: Se fai un link italiani, il sistema lo mostra automaticamente come italiani -
 * Parentesi nascoste Se fai un link kernel (matematica), il sistema lo mostra automaticamente come kernel . This is useful for disambiguating different meanings of a word without making linking too difficult or cluttering up the text of articles. Questo vale anche per i nomi di namespace; ad esempio Copyrights diventa Copyrights
 * Link a sezioni di un articolo es MediaWiki roadmap (questi link possono essere inutili se le sezioni vengono cambiate. Per compensare ciò c'è stata una proposta.)
 * Supporto per sottopagine
 * Keyword speciali per l'inserimento di dati dinamici come il nome della pagina, la data e l'ora; vedi Help:Variables/it
 * Multiple Categorie che possono essere assegnate ad ogni pagina. Category pages automatically list all pages assigned to them, including sub-categories. Categories allow classification and hierarchical browsing of the content.

Editing

 * Section editing. Users can enable an option that allows them to edit individual sections of an article (separated by headlines) instead of loading the entire article.
 * Edit toolbar (JavaScript-based) for formatting text as bold, italic etc. (fully works in Mozilla and IE, other browsers use it to show the syntax, but cannot format text inside the text area because their JavaScript implementation does not support it). If JavaScript is disabled, the toolbar is not shown.
 * Edit summary which is shown in "Recent changes". Will be prefilled with section title when section editing.
 * Double click editing: Users can enable an option that allows them to edit articles by double clicking them.
 * Edit preview (can be shown before or after edit box)
 * Handle edit conflicts (page being saved by a user while still being edited by another one, then saved again). MediaWiki will merge changes automatically if possible and otherwise require the user to do a manual merge.
 * Mark edits as minor; users can decide to hide such edits from the Recent Changes list. Only signed in users can mark edits as minor.

Spam and Vandalism

 * Anti-spam features: Prevent link spamming, and other forms of abusive editing.
 * Spam blacklist: List of spammer's domain names which users are not allowed to link to.
 * Manual:Combating vandalism: Helpful hints and links to some extensions for dealing with vandalism

Discussions

 * Talk pages: Each user (including every anonymous user) and every article has an associated page where messages can be left. These are separate namespaces (see above), "Talk:" and "User talk:".
 * Message notification (user gets a "You have new messages" notice if someone else has edited their user discussion page); this also works for anonymous users, but not for shared IP users
 * Automatic signature: Just type three tildes (~) when you edit, and on saving the page, it will be replaced with your user name and a link to your user page. If you use four tildes, the current date will be added as well. Mainly intended for Talk pages.
 * Support for emailing users through the wiki (email address not shown to the user)

Multilanguage support

 * Translated into many languages (see en:Wikipedia:Multilingual coordination for details)
 * Interlanguage links: handy method for linking articles between wikis in different languages (each language requires its own database)
 * UTF-8 support

Backend

 * Database-driven (MySQL/MariaDB, PostgreSQL, and SQlite are supported)
 * Parser caching: rendered pages are cached to reduce redundant processing
 * Output caching: complete page output can be optionally saved as static HTML files for serving to other clients; support for Squid proxies
 * Cookie-based account and login system, but anonymous users can also edit pages
 * All revisions of an article are stored (optionally compressed)
 * RSS syndication available for many special pages, such as Special:Newpages and Special:Recentchanges
 * RDF metadata

Permissions

 * Different rights for anonymous users, signed in users, sysops, bureaucrats and developers.
 * Signed in users can:
 * move and rename pages
 * upload files
 * have and use a watchlist
 * mark edits as minor edits (eg. typo correction)
 * Admins/Sysops can:
 * protect pages from editing
 * delete and undelete pages
 * edit protected pages
 * ban users by IP address
 * ban users by username, if this option is enabled
 * run SQL queries on the database, if this option is enabled (see Extension:Asksql)
 * Bureaucrats can:
 * create sysops
 * rename users
 * flag bots
 * Developers can:
 * lock the database
 * run various maintenance tasks
 * Other permission schemes (e.g. only signed in users can edit pages) can be configured.

Search and Queries

 * Full text search
 * "Go" button allows direct viewing of a specified article's contents (tries near match if no exact hit)
 * "What links here": View pages that link to the current page (backlinks)
 * Special report pages:
 * New pages: List of newly created articles
 * Ancient pages: Articles sorted by timestamp, ascending
 * List of images
 * List of users
 * Site statistics
 * Orphaned articles (articles that have no links pointing to them)
 * Orphaned images
 * Popular articles (articles by number of visits, works only if counters are enabled)
 * Most wanted articles (non-existent articles sorted by number of links pointing to them)
 * Short articles
 * Long articles
 * List of all pages by title
 * Query API - allows scripted access to various metadata

Misc.

 * Random article display function
 * Users can configure their timezone, which is used on all report timestamps
 * The attributes of many report pages (number of results etc.) can be set in the user preferences

Empty set of help pages
Note that the files in the installation contain many links pointing to documents that are not included in the download. Most important is the empty set of help files, which will be needed by any new user of the site. To remedy these broken links, you must either a) export from this site or manually copy and modify help pages to your installation or b) modify the installation's parameters to change the help link targets to this site, either of which may require a substantial time investment.

Coming soon

 * See Special:MyLanguage/MediaWiki roadmap.