Manual:MediaWiki feature list/ja

このページではMediaWikiソフトウェアに組み込まれている機能のリストを説明します. 独自wikiのためにMediaWikiを使用するかどうかはwikiで運営したいウェブサイトの種類によります. Wikipediaのソフトウェアにはユーザのニーズと開発者のアイディアから由来する多くの便利な機能があります -- しかし多機能は複雑であることも意味します. MediaWikiの利用を始める前に、他のwikiエンジンを調べて(リストもしくは比較表をご覧下さい)あなたの要件により合うものがあるかどうか見て下さい.

新しい機能のリクエストは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.

ルックアンドフィール

 * ショートカット付きのリンク, 並びはスキンによります
 * スキン: サイトを表す異なる方法はPHPTalテンプレートの使用によって拡張することが出来ます..
 * Monobook、アクセスキーとツールチップを持つモダンなスキン
 * 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.
 * ユーザスタイル:ユーザはユーザページ上でカスタムCSSを通してサイトのルックアンドフォールを編集することが出来ます.
 * "Stub" threshold(スタブスレショールド・スタブの敷居): ユーザは異なる色でレンダーされたあるサイズ以下の記事へのリンクを見ることが出来ます
 * Printable versions(印刷可能なバージョン)の記事を生成することが出来ます
 * 自動連番の見出し: 記事(オプション)
 * 内部ページアンカー (見出しのために自動的に生成され、 ... を伴います)
 * 内容のテーブルの生成 長い記事のため (オプション)
 * 自動的にISBN番号を書籍販売業者が編集可能なリンクに変換する
 * XHTML-互換の出力 (もしくはそれに近いものに見繕う)、tidyの統合

マルチメディアとエクステンション

 * ファイルのアップロード機能 グラフィックもしくはサウンドファイルをアップロードすることを可能にします. 実行方法についてはSpecial:Uploadをご覧下さい. Manual:Configuring file uploads/jaとManual:Image administration/jaに説明があります. アップロードされたファイルは最近更新したページにリスト表示され、Special:Log/uploadにも記録されます.
 * LaTeX構文を使用した数式表示: texvcをご覧下さい
 * ImageMagickもしくはlibgdを使用した画像の自動的なリサイジングと画像の短い説明文と画像の配置のためのシンプルな構文
 * WikiHiero 古代エジプトのためのヒエログラフ(個別にコンポーネントをインストールする必要があります)
 * EasyTimeline タイムチャート用(個別にコンポーネントをインストールする必要があります)

編集の追跡

 * ウォッチリスト すべてのページには"ウォッチリストに追加"のリンクがあります. 興味があると宣言した記事の変更を追跡するためにSpecial:Watchlistを使用します; ウォッチされた記事は最近更新したページのリストにも太文字で表示されます.
 * ユーザの投稿記録 それぞれのユーザページのサイドバーにユーザが投稿したすべての記事をデータベースに従ってリスト表示します.
 * 拡張された最近の更新 同じ記事へのダイナミックな変化と差分ｊへの素早いリンク、記事の履歴を表示する、ユーザページを表示する、トークページを表示する、もしくはユーザをブロックする(シスオペ用)
 * "最近更新されたページ": 現在のページからリンクされたページの最近の更新をフィルターしたバージョンで閲覧します.
 * 並んでいる差分 - 差分は並んで表示され、行の変更された部分はハイライトされ、何が何であるかを大いに見やすくしています. 加えて、差分は編集の衝突の間に表示されるので、再統合する必要があるものが何であるのかが正確にわかります.
 * 本名 ユーザは(オプションで)ユーザクレジットのために"本名"を指定することが出来ます.
 * ページ上のクレジット アドミニストレータはクレジットをページの編集者に付与するページ上のパラグラフを有効にすることが出来ます.

構造と構文

 * デフォルトでは、制限されたHTMLの使用だけが許可されます. HTMLをフルに使うオプションは存在します.
 * UseModに基づいた構文を編集する、wiki構文とHTMLをサポートします. リンクのためにフリーなリンクのみがサポートされます. キャメルケースはサポートされません(入念なデザイン決定)
 * 名前空間は内容の分離を可能にします(名前空間を表すために、 Namespace:Page title を使用します).
 * 討論 (Talk:) ページは記事ページから分離されています. "meta"プロジェクトページは内容のページから分離することが出来ます. 画像ページは画像の説明のために使用されます.
 * MediaWikiの名前空間はすべてのユーザインターフェイステキストを含むので、他のwikiページと同じように編集することが出来ます
 * Template: カスタムメッセージのための名前空間です. テンプレートは呼び出したページからテンプレートに渡される特定の値を置き換える文字列の変数を含むことが出来ます.
 * 名前空間にある任意のページのトランスクルージョン: .  テンプレートをご覧下さい
 * 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.

編集

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

スパムおよび荒らし

 * 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

議論

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

多言語対応

 * 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

バックエンド

 * 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

権限

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

検索とクエリ

 * 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
 * 画像の一覧
 * 利用者の一覧
 * サイトの統計
 * 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

その他

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