Skip to content
Snippets Groups Projects
Commit 2b8228b2 authored by Lauren's avatar Lauren
Browse files

Edits to readme file

parent 2525e838
No related branches found
No related tags found
No related merge requests found
how to use: === LBDesign Button Shortcode ===
Contributors: lepittenger
[button link="http://something.com" color="red" size="big"]Call to Action![/button] Tags: shortcode
Requires at least: 3.0.1
How to style (can also be found in LBD Client Theme): Tested up to: 4.0.1
Stable tag: 4.3
/* DEFAULT button shortcode styles */ License: GPLv2 or later
a.button { License URI: http://www.gnu.org/licenses/gpl-2.0.html
background: $color_buttons; /* Old browsers */
color: #fff !important; A simple plugin for adding call-to-action buttons to post & page content via a shortcode.
text-decoration: none;
font-weight: bold; == Description ==
padding: 15px 20px;
display: inline-block; This simple plugin allows you to add call-to-action buttons to post and page content via a shortcode.
text-transform: uppercase;
margin-bottom: 20px; There are five styles included:
border: 0; * Default
} * Primary
a.button:hover, * Action
a.button:focus { * Info
background: $color_buttons_hover; /* Old browsers */ * Warning
}
/* COLOR button styles */ There are three sizes:
a.button.orange { * Default (medium)
background: $color_buttons_alt; /* Old browsers */ * Small
} * Large
a.button.orange:hover,
a.button.orange:focus { == Installation ==
background: $color_buttons_alt_hover;
} This section describes how to install the plugin and get it working.
/* SIZE button styles */
a.button.big { e.g.
padding: 25px 20px;
font-size: 1.2em; 1. Upload `lbdesign-button-shortcode` to the `/wp-content/plugins/` directory
} 2. Activate the plugin through the 'Plugins' menu in WordPress
\ No newline at end of file 3. Add buttons to post and page content using the insert button on the WordPress editor
== Frequently Asked Questions ==
None yet.
== 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
== Changelog ==
== Upgrade Notice ==
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment