#77 and #78 added support for different images on Twitter and Facebook, an advanced feature of SEO
Tag Gem. The implementation has led to complications updating JSON-LD data in #151. Under Pareto
principal we can reasonably assume this feature is not often used, and, as such, should be removed.
The result of which simplifies template logic, offers a fallback experience by leverages Twitter's
use of `og:image` in place of `twitter:image` (sees twitter card tag ref) and helps unblock #151.
Users can no longer specify a separate twitter and Facebook image. If both a Facebook (Open Graph)
and Twitter image are provided in the `image` object, the Facebook image will take precedence.
Replaces the "-" used as a title separator with "|".
Ref: https://moz.com/learn/seo/title-tag
Also updates docs to specify title optional and fix errata.
This adds the rest of the JSON fields to pass all errors and blog postings.
- Adds page.image.url for the image url. (Will default to image if not present).
- Add page.image.height and page.image.width for an image object (Will default back to image url if not present).
- Add dateModified (will capture from yaml if present, if not it will use datePublished)
- (I feel there should be a manual option for this as I sometimes save parts of my blog that shouldn't update the modified field, but still
change the file timestamp).
This should create JSON that will pass all warnings/strong recommendations/errors from [Google's Structured Data Testing Tool](https://search.google.com/structured-data/testing-tool).
Ben Balter
Kyle Niewiada
Kyle Niewiada
Aaron Gustafson
Ben Balter
Josh Habdas
Frank Taillandier
renshuki