SEO StucturedMarkup
![Software License][ico-license]
![Coverage Status][ico-scrutinizer]
![Total Downloads][ico-downloads], (*1)
Note: Replace :author_name :author_username :author_website :author_email :vendor :package_name :package_description with their correct values in README.md, CHANGELOG.md, CONTRIBUTING.md, LICENSE.md and composer.json files, then delete this line. You can run $ php prefill.php in the command line to make all replacements at once. Delete the file prefill.php as well., (*2)
This is where your description should go. Try and limit it to a paragraph or two, and maybe throw in a mention of what
PSRs you support to avoid any confusion with users and contributors., (*3)
Structure
If any of the following are applicable to your project, then the directory structure should follow industry best practises by being named the following., (*4)
bin/
config/
src/
tests/
vendor/
Install
Via Composer, (*5)
``` bash
$ composer require kdaviesnz/seostructuredmarkup, (*6)
## Usage
``` php
$product = array(
"title" => "A widget",
"images" => array(
"large" => array(
"src" => "http://example.com/image.jpg"
)
),
"description" => "This is a widget",
"brand" => "Widget Brand",
"rating" => "8",
"currency" => "USD",
"merchant" => "Widget Co",
"price" => "100.00",
"organization" => "Widget Org"
);
$structuredMarkup = new \kdaviesnz\seostructuredmarkup\SEOStructuredMarkup("product", $product);
echo $structuredMarkup;
Change log
Please see CHANGELOG for more information on what has changed recently., (*7)
Testing
bash
$ composer test, (*8)
Contributing
Please see CONTRIBUTING and CODE_OF_CONDUCT for details., (*9)
Security
If you discover any security related issues, please email :author_email instead of using the issue tracker., (*10)
Credits
License
The MIT License (MIT). Please see License File for more information., (*11)
seostructuredmarkup
Wallogit.com
