Plugin yìí kò tíì ṣe àyẹ̀wò pẹ̀lú àwọn ìtújáde mẹ́ta pàtàkì tó kẹ́yìn ti WordPress. Ó lè jẹ́ pé a kò tọ́jú tàbí ṣe àtìlẹ́yìn fún un mọ́, ó sì lè ní àwọn ọ̀ràn ìbámu nígbà tí a bá lò ó pẹ̀lú àwọn ẹ̀yà WordPress tuntun.

Awesome Newsletter

Àpèjúwe

Use shortcode ( [newsletter_form] ) to show the subscriber form

A few notes about the sections above:

  • “Contributors” is a comma separated list of wordpress.org usernames
  • “Tags” is a comma separated list of tags that apply to the plugin
  • “Requires at least” is the lowest version that the plugin will work on
  • “Tested up to” is the highest version that youÌtumọ̀ Yorùbá: ’ve successfully used to test the plugin. Note that it might work on
    higher versions… this is just the highest one youÌtumọ̀ Yorùbá: ’ve verified.
  • Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for
    stable.

    Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so
    if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt thatÌtumọ̀ Yorùbá: ’ll be used
    for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt
    is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in
    your in-development version, without having that information incorrectly disclosed about the current stable version
    that lacks those changes Ìtumọ̀ Yorùbá: — as long as the trunkÌtumọ̀ Yorùbá: ’s readme.txt points to the correct stable tag.

    If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if thatÌtumọ̀ Yorùbá: ’s where
    you put the stable version, in order to eliminate any doubt.

Arbitrary section

You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
plugins where more information needs to be conveyed that doesnÌtumọ̀ Yorùbá: ’t fit into the categories of “description” or
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.

A brief Markdown Example

Ordered list:

  1. Some feature
  2. Another feature
  3. Something else about the plugin

Unordered list:

  • something
  • something else
  • third thing

HereÌtumọ̀ Yorùbá: ’s a link to WordPress and one to MarkdownÌtumọ̀ Yorùbá: ’s Syntax Documentation.
Titles are optional, naturally.

Markdown uses email style notation for blockquotes and IÌtumọ̀ Yorùbá: ’ve been told:

Asterisks for emphasis. Double it up for strong.

<?php code(); // goes in backticks ?>

Ìgbéwọlẹ̀

This section describes how to install the plugin and get it working.

e.g.

  1. Upload the plugin files to the /wp-content/plugins/plugin-name directory, or install the plugin through the WordPress plugins screen directly.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress
  3. Use the Settings->Plugin Name screen to configure the plugin
  4. (Make your instructions match the desired user flow for activating and installing your plugin. Include any steps that might be needed for explanatory purposes)

FAQ

A question that someone might have

An answer to that question.

What about foo bar?

Answer to foo bar dilemma.

Àwọn àgbéyẹ̀wò

Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.

Àwọn Olùkópa & Olùgbéejáde

“Awesome Newsletter” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

Túmọ̀ “Awesome Newsletter” sí èdè rẹ.

Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.

Àkọsílẹ̀ àwọn àyípadà

1.0

  • A change since the previous version.
  • Another change.

0.5

  • List versions from most recent at top to oldest at bottom.