Manual:MediaWiki feature list/es

Esta página contiene una lista de características que están constituidas en el software MediaWiki. Si tuvieras que usar MediaWiki para su propia wiki, depende de qué tipo de sitio web desea correr con el. El software de Wikipedia tiene muchas características útiles que surgieron de las necesidades de los usuarios y las ideas de los desarrolladores - pero hay características que también cuentan con una mala complejidad. Antes de decidirse a usar MediaWiki, por favor, eche un vistazo a otros motores wiki (véase esta lista o esta comparación) y ver si uno de ellos podría satisfacer mejor sus necesidades.

Las peticiones de nuevas características tendrán que ser enviadas a Phabricator.

¿Quiero MediaWiki?
El software y las extensiones de MediaWiki tienen características, fortalezas y debilidades; ventajas y desventajas, a pesar de que nadie ' tiene fines previstos, el software y extensiones MediaWiki pueden ser utilizados con fines únicos, inteligentes e inventivos no previstos por los programadores originales u otros instaladores. He aquí una breve lista de las características y beneficios de MediaWiki. Si se presenta una lista equivalente de sus propios objetivos y recursos, se puede comparar esta lista a su lista ', o falta de coincidencia. ¿Necesita más ayuda para decidir? Hay grupos de discusión abierta en la web y páginas de discusión "para hablar" detrás de cada página principal MediaWiki donde se puede buscar la conexión con otras personas ' y obtener experiencias.

Nota: muestra de la lista de características de las páginas 13-14, en el libro "Los administradores de MediaWiki" ' Guía Tutorial: Instalar, gestionar y personalizar la instalación de MediaWiki" por Mizanur Rahman, 2007 http://www.packtpub.com/

Por favor, mejorar y ampliar la tabla anterior ' características y beneficios para ayudar a los visitantes a conocer mejor lo que están metiendo. ¡Gracias!

Un problema recurrente es que los administradores del sistema deciden crear un wiki, sin tener en cuenta muchas cuestiones. Después de llenar la tabla anterior, hágase las siguientes preguntas, para ver si un wiki es el software adecuado para usted:
 * 1) ¿Cuál es la finalidad de mi sitio?
 * Los wikis son ideales para la edición colaborativa y la creación de contenidos; que no son muy adecuados para otros fines, como los blogs. Considerar si una wiki es una opción adecuada para sus objetivos.
 * 1) ¿A cuántos usuarios estará expuesto el wiki?
 * Con unas pocas excepciones, la instalación de software wiki es necesaria cuando hay un grupo muy pequeño de personas interesadas en la edición del wiki. Cuanto mayor sea el número de usuarios, mayor será la probabilidad de un wiki tiene más sentido para usted.
 * 1) ¿Cuántos editores activos es lo que espero para editar mi wiki?
 * Las wikis, debido a su naturaleza abierta, requiere un poco de mantenimiento. Cuanto más grande sea la base redactor, los más manos disponibles para llevar a cabo las tareas de mantenimiento.
 * 1) ¿Qué puedo hacer con MediaWiki?
 * MediaWiki es un motor wiki extremadamente versátil; que es relativamente fácil de instalar, pero lo más importante, permite el uso y la creación de extensiones. Estos permiten la instalación de MediaWiki para ser extremadamente adaptable con algunos conocimientos de PHP. Con la motivación adecuada, MediaWiki puede ser "abusado" para hacer casi cualquier cosa.
 * 1) ¿MediaWiki es adecuado para mí?
 * MediaWiki tiene sus limitaciones. Actualmente, no hay soporte para editar WYSIWYG, por lo que todos los editores necesitan aprender código wiki. Esto presenta una pequeña barrera de entrada. Una limitación más importante es que MediaWiki no está destinado a ser una lista de control de acceso. MediaWiki raison d'etre es proporcionar contenido abierto; mientras que las versiones recientes tienen un modelo de seguridad mucho más fuerte, aún existen brechas significativas en el acceso de seguridad de base individual.

Véase y Las extensiones con prórroga de autorización.

¿Cómo debo configurar MediaWiki?
Si usted ha decidido que MediaWiki es de hecho una solución apropiada, todavía hay más cosas a considerar. Estas preguntas se espera ayude a decidir cómo configurar el wiki de una manera que le permitia minimizar los problemas a largo plazo: See Manual:User rights and Help:User rights management for more ideas and information.
 * 1) ¿Quién va a leer mi wiki?
 * A pesar de todos los problemas con restricciones de página basados en el usuario, MediaWiki puede ser configurado para restringir o permitir el acceso a todo el mundo. Por lo tanto, preguntarse si quieres que todos en el Internet para ver el contenido de la wiki, o si desea restringir ese privilegio a aquellos usuarios que han creado cuentas en su wiki.
 * 1) ¿Quién va a editar mi wiki?
 * Tal vez la pregunta más común es si desea permitir a todos a editar el wiki, similar al modelo de Wikipedia. MediaWiki permite restricciones de escritura de grano fino; puede permitir a los usuarios no registrados para editar las páginas de discusión, por ejemplo, pero sólo permitirá a los usuarios con cuentas de más de una cierta cantidad de tiempo para editar sus páginas de contenido. Se puede restringir la edición a los administradores, o incluso a un grupo de usuario personalizado que se crea y delega.
 * 1) ¿Quién debe crear una cuenta en mi wiki?
 * En función de algunas de las respuestas a las preguntas anteriores, es posible que desee decidir restringir quién puede crear cuentas en un wiki. Puede permitir a cualquiera crear cuentas; o incluso se puede designar que el privilegio de los administradores, que sería entonces responsable de la creación de cuentas de nuevos usuarios a través de algún proceso de su elección.
 * 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.

Look and feel

 * Links with shortcuts, arrangement depends on skin.
 * Skins: Different ways to present the site
 * Monobook, a modern skin with accesskeys and tooltips.
 * 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 styles: Users can adapt the look and feel of the site through custom CSS on their user pages.
 * "Stub" threshold: Users can see links to articles below a certain size rendered in a different color.
 * Printable versions of articles can be generated.
 * Auto-number headings in an article (optional).
 * Intra-page Anchors (automatically generated for headings, and also with ... ).
 * Automatically generate a table of contents for long articles (optional).
 * Automatically turn ISBN numbers into links to an editable list of booksellers.
 * XHTML- or HTML5-compatible output (or darn close to it), tidy integration.

Multimedia and extensions

 * File upload feature allows to upload graphics or sound files, see Special:Upload to see in operation, and Uploading files for description. Uploaded files are listed on Recent Changes and they are also logged on Special:Log/upload.
 * Mathematical formulas using LaTeX syntax: see texvc
 * Automatic resizing of images using ImageMagick or libgd, simple syntax for image captions and image alignment
 * WikiHiero for Egyptian hieroglyphs (needs separate installed components)
 * EasyTimeline for time charts (needs separate installed components)

Keeping track of edits

 * Watchlist Every page has a link "Watch this article for me". Use Special:Watchlist to track changes on the articles you declared as interesting; watched articles are also bolded in the Recent changes list.
 * User contributions in the sidebar of each user page list all articles the user has worked on, according to the database.
 * Extended recent changes with dynamic collapsing of edits to the same article and quick links to diff the edit, show the article history, show the user page, show the user talk page, or block the user (for sysops)
 * "Related changes": View a filtered version of Recent Changes to the pages linked from the current page.
 * Side-by-side diffs - the diffs are shown side-by-side, and changed portions of lines are highlighted, making it much easier to see what's what. Additionally, a diff is shown during an edit conflict so you can see exactly what you need to reintegrate.
 * Real names - Users can (optionally) specify a "real name" they want to use for author credits.
 * On-page credits. Administrators can enable an on-page paragraph giving credit to editors who've worked on a page.

Structures and syntax

 * By default, only restricted use of HTML is allowed. There is an option to allow full use of HTML.
 * Editing syntax based on UseMod, with support for mixing wiki-syntax and HTML. Only free links are supported for linking, not CamelCase (deliberate design decision).
 * Namespaces allow content separation (to address the namespace, use the Special:MyLanguage/Namespace:Page title syntax).
 * Discussion (Talk:) pages are separate from article pages, "meta" project pages can be separated from content pages, image pages are used for image descriptions.
 * MediaWiki: namespace contains all user interface texts, so that they can be edited like any other wiki page
 * Template: namespace for custom messages. Templates may contain string variables which are replaced with certain values passed to the template from the calling page.
 * Transclusion of arbitrary pages in any namespace: . See Templates
 * Word-extension linking: If you include a link of the form Special:MyLanguage/wars, or Special:MyLanguage/wartime , the system will automatically display it as if you had typed wars or wartime , respectively, saving some typing.
 * Parenthetical hiding ("pipe tricks") If you include a link of the form Special:MyLanguage/kernel (mathematics), the parenthetical portion will be hidden in the link: kernel. This is useful for disambiguating different meanings of a word without making linking too difficult or cluttering up the text of articles. This also works with cropping out namespaces when you want a cleaner-looking link: Special:MyLanguage/Wikipedia:Copyrights becomes Copyrights
 * Link to individual sections of an article, e.g. (these links may become invalid if sections are retitled or removed.)
 * Support for subpages (link to "Foo/Bar" from "Foo" by just typing "/Bar", "Foo/Bar" contains a backlink to "Foo"), these can be enabled or disabled by namespace (e.g., Wikipedia currently supports subpages on discussion pages, to make archiving easy, and on user pages, to give users space for personal pages)
 * Special keywords for inserting dynamic data such as the name of the current page, the current date, the number of articles, etc.
 * Multiple Categories can be assigned to any page, including categories themselves, creating a hierarchy of categories. 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

 * 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.