Шаблон:Modeling/doc — различия между версиями

One of:

• unstable (broken - do not use this extension)
• experimental (early stages of development, may change drastically.)
• beta (stable but not fully tested)
• stable (stable version)
• unknown (default)

If the status is anything other than the above, it will be ignored and the default value of 'Unknown' will be displayed in the template instead. In cases where the value is omitted, it will be categorized as unknown. In cases where the value is invalid, it will be placed in a special category so that the error can be caught and fixed.

The implementation strategy(s) employed in building this extension. This parameter is used to create categories that help programmers find examples of various MediaWiki specific implementation strategies or patterns. Although the values of this parameter sometimes coincide with the use case or purpose of an extension, that is not reason for this parameter. If the values you have chosen for this parameter do not adequately identify the purpose or possible use cases, we recommend you add additional category links as needed.

Legal values for the type1,type2,... parameters are:

• parser - catchall for uncategorized parser extensions. If you have written a parser extension, please use one of the following more specific types:
  • link - customized link markup, e.g. [[...]]
  • parser function - custom parameterized template markup, e.g. {{#name: ... }}
  • tag - custom XML tag markup, e.g. <tagname>...</tagname>
  • variable - custom unparameterized template markup, e.g. {{NAME}}
  • extended syntax - Extensions that add non-standard wiki syntax (i.e. not tags, parser functions, or variables).

• access - catchall for user access extensions, that is, extensions that create, authenticate, grant permissions, revoke permissions, or monitor the activity of users. If you have written an access extension, please use one of the following more specific types:
  • user activity - extensions that monitor user activity (logins, logouts, new user creation, etc)
  • user identity - extensions that create and delete users, and/or verify the identity of a user
  • user rights - extensions to the rights management system, e.g. changes to the way rights are assigned, apis, maintenance tools (does not include extensions that merely name the rights needed to use the features of that extension. For this purpose use the rights parameter.).

• interface - catchall for uncategorized user interface extensions.
  • media - extensions that permit the embedding of multimedia content on wiki pages by registering a file extension with $wgMediaHandlers.
  • mywiki - extensions that provide infrastructure so that users may personalize their MediaWiki experience and/or assist in the management of that infrastructure
  • notify - extensions that email users, broadcast messages and provide other forms of community notification
  • page action - extensions that enhance or modify page actions. This includes anything that implements an action that reads, writes, searches for, creates, renames, deletes, redirects or discusses a page. It does not include rights (use user rights) or logs (use user activity).
  • search - extensions that search through and select articles for users.
  • skin - extensions adding CSS or JavaScript, or implementing hook functions to change the look and feel of MediaWiki via the skins framework.
  • ajax - extensions that use Ajax programming techniques.
  • special - extensions that subclass the SpecialPage class, use one of its hooks, or patch one or more functions in SpecialPage.php. See Manual:Special pages for more information.
• other
  • api - extensions that add a new API module or extend a core API module.
  • hook - Hook extension - defines a new hook - see hook1, etc below if you want to define hooks used by your extension

• pfunc - same as parser function

• database - adds tables and/or fields to the database backing a MediaWiki installation
• db - same as database
• data extraction - Data extraction
• example - Not a real extension, but an example of how to write one

Any other value for 'type' is invalid, and will cause the extension to be placed in Category:Extensions with invalid or missing type.

Note: Many extensions have more than one type, if this applies to yours,replace |type= with |type1=|type2=|type3=.... You may define up to six types for an extension.

Entering values in this field is a good way to get exposure for your extension and help other developers. Each documented hook will automatically add the extension to a category listing extensions that use that hook. This category is autolinked to each hook article so that programmers can easily find examples of extensions that use a particular hook.

For built-in hooks:

• use the hook name alone. Please see Manual:Hooks for values (but omit introductory '/').

For custom hooks defined by extensions:

• use extensionName/hookName. For a partial list of custom hooks, see Extension hook registry.

For multiple hooks, assign the first hook to hook1, the second to hook2 and so on.

Normally left blank. Alternate values are:

• nocats - suppresses categorization. Use this value if you are adding this template to subpages of an extension or to how-to documentation of extensions. For example, the usage image above sets templatemode=nocats because this isn't an actual extension page and we don't want to add this page to any categories on account of it.

If this is left blank, this template will add the host page to Category:All extensions and to one or more additional categories, depending on the values assigned to the Content parameters.