Changeset 1423926

Timestamp:

05/25/2016 09:44:28 AM (10 years ago)

Author:

dnljhnmrsdn

Message:

Additional Assets & Readme Update

Location:

simple-custom-google-map

Files:

• assets/banner-772x250.jpg (added)
• assets/icon-128x128.png (added)
• assets/icon-256x256.png (added)
• trunk/readme.txt (modified) (2 diffs)

simple-custom-google-map/trunk/readme.txt

@@ -13 +13 @@
 == Description ==
 
-This is the long description.  No limit, and you can use Markdown (as well as in the following sections).
-
-For backwards compatibility, if this section is missing, the full length of the short description will be used, and
-Markdown parsed.
-
-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've *successfully used to test the plugin*. Note that it might work on
-higher versions... this is just the highest one you'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'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 -- as long as the trunk'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's where
-you put the stable version, in order to eliminate any doubt.
+Simple custom Google Map adds a simple, intuitive interface to create and style a Google Map to suit your website's styling. Simple drag and drop interface means that you can drag the pointer to any position on the admin preview map, and this will be mirrored on your website front-end.
 
 == Installation ==
 
-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
+1. Upload the plugin files to your plugins directory, or install the plugin via WordPress.
+2. Activate the plugin through the 'Plugins' screen.
 3. Use the 'Map Styles' screen to configure the plugin
 4. Configure the map to your heart's content, use built in widget, or add '[styled_google_map]' shortcode.
@@ -52 +25 @@
 == Screenshots ==
 
-1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
-the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets 
-directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png` 
-(or jpg, jpeg, gif).
-2. This is the second screen shot
+1. The Simple Custom Google Maps configuration screen.
 
 == Changelog ==