Changeset 1726837
- Timestamp:
- 09/08/2017 01:57:15 PM (7 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
mobil-cihazlar-icin-hizli-iletisim/trunk/readme.txt
r1726794 r1726837 13 13 == Description == 14 14 15 This is the long description. No limit, and you can use Markdown (as well as in the following sections). 16 17 For backwards compatibility, if this section is missing, the full length of the short description will be used, and 18 Markdown parsed. 19 20 A few notes about the sections above: 21 22 * "Contributors" is a comma separated list of wordpress.org usernames 23 * "Tags" is a comma separated list of tags that apply to the plugin 24 * "Requires at least" is the lowest version that the plugin will work on 25 * "Tested up to" is the highest version that you've *successfully used to test the plugin*. Note that it might work on 26 higher versions... this is just the highest one you've verified. 27 * Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use `/trunk/` for 28 stable. 29 30 Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so 31 if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that'll be used 32 for displaying information about the plugin. In this situation, the only thing considered from the trunk `readme.txt` 33 is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in 34 your in-development version, without having that information incorrectly disclosed about the current stable version 35 that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag. 36 37 If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where 38 you put the stable version, in order to eliminate any doubt. 15 Mobil seo’nun önem kazandığı bu zamanlarda, sitelerimize mobilden cihazlardan erişim artmış durumda. Bu durumda ziyaretçileriniz ile daha hızlı iletişim kurmak için bu eklentiyi geliştirdik. Sadece mobil cihazlardan erişim yapıldığında görülen telefon ve whatsapp butonları sayesinde ziyaretçilerinizi müşteriye dönüştürün. Eklenti ile ilgili destek almak için<a href="https://www.muratbutun.com/wordpress-mobil-cihazlar-icin-hizli-iletisim-eklentisi.html" target="_blank"> bu sayfayı </a>kullanabilirsiniz 39 16 40 17 == Installation == 41 18 42 This section describes how to install the plugin and get it working. 43 44 e.g. 45 46 1. Upload the plugin files to the `/wp-content/plugins/plugin-name` directory, or install the plugin through the WordPress plugins screen directly. 47 1. Activate the plugin through the 'Plugins' screen in WordPress 48 1. Use the Settings->Plugin Name screen to configure the plugin 49 1. (Make your instructions match the desired user flow for activating and installing your plugin. Include any steps that might be needed for explanatory purposes) 19 Eklentiyi indirip /wp-content/plugins dizinine atın. WordPress eklentiler ekranından aktif edin. İletişim bilgilerinizi girmek için Eklentiler > Mobil İletişim sayfasına tıklayın. Eklenti kurulumu ile ilgili detaylı bilgi için tıklayınız. 50 20 51 21 52 22 == Frequently Asked Questions == 53 23 54 = A question that someone might have=24 = = 55 25 56 An answer to that question.26 . 57 27 58 = What about foo bar? =28 = ? = 59 29 60 Answer to foo bar dilemma.30 . 61 31 62 32 == Screenshots == 63 33 64 1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from 65 the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets 66 directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png` 67 (or jpg, jpeg, gif). 68 2. This is the second screen shot 34 screenshot-1.jpg 35 screenshot-2.jpg 69 36 70 37 == Changelog == 71 38 72 39 = 1.0 = 73 * A change since the previous version. 74 * Another change. 75 76 = 0.5 = 77 * List versions from most recent at top to oldest at bottom. 40 * Eklenti wordpress.org'a Merhaba Dedi 78 41 79 42 == Upgrade Notice == 80 43 81 44 = 1.0 = 82 Upgrade notices describe the reason a user should upgrade. No more than 300 characters. 45 Eklenti wordpress.org'a Merhaba Dedi 83 46 84 = 0.5 = 85 This version fixes a security related bug. Upgrade immediately. 47 == Eklenti Videosu == 86 48 87 == Arbitrary section == 49 <iframe width="560" height="315" src="https://www.youtube.com/embed/WVK-seVc5i0?rel=0&showinfo=0" frameborder="0" allowfullscreen></iframe> 88 50 89 You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated 90 plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or 91 "installation." Arbitrary sections will be shown below the built-in sections outlined above. 51 == Murat Bütün == 92 52 93 == A brief Markdown Example == 94 95 Ordered list: 96 97 1. Some feature 98 1. Another feature 99 1. Something else about the plugin 100 101 Unordered list: 102 103 * something 104 * something else 105 * third thing 106 107 Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax]. 108 Titles are optional, naturally. 109 110 [markdown syntax]: http://daringfireball.net/projects/markdown/syntax 111 "Markdown is what the parser uses to process much of the readme file" 112 113 Markdown uses email style notation for blockquotes and I've been told: 114 > Asterisks for *emphasis*. Double it up for **strong**. 115 116 `<?php code(); // goes in backticks ?>` 53 Wordpress ve WooCommerce ile ilgili kısa kodlar güncel yazılar için <a href="https://www.muratbutun.com/blog" title="Wordpress WooCommerce Blog" target="_blank">blog</a> sayfamı takip edebilirsiniz.
Note: See TracChangeset
for help on using the changeset viewer.