-
Notifications
You must be signed in to change notification settings - Fork 2
Roadmap
Mike Sukmanowsky edited this page May 28, 2015
·
1 revision
Basically a port of the wp-parsely WordPress plugin: https://github.com/Parsely/wp-parsely and https://wordpress.org/plugins/wp-parsely/screenshots/. Module that works with Drupal v7 and up.
Before reading the list below, please give http://www.parsely.com/docs/integration/tracking/basic.html and http://www.parsely.com/docs/integration/metadata/jsonld.html a read to understand the information required for a Parse.ly integration.
Most tricky thing for this initial version that we need help with is figuring out how to populate the metadata parse.ly requires for:
- Page type: post or non-post?
- Image Thumbnail URL
- Authors
- Section (single-valued)
- Tags (multi-valued)
- Publish date
- Headline
Some of these we've taken cracks at but need review, others haven't been started.
- Users have the ability to set a Parse.ly API key (aka Site ID) used in javascript config
- Users can configure which nodes in the CMS are posts via module admin (determines json+ld's
@type
attribute being set toNewsArticle
) - Users can configure how the thumbnail image URL, author, section and tag metadata are loaded and this information is sent via Parsely metadata tags (see http://www.parsely.com/docs/integration/metadata/jsonld.html) via module admin
- Check code on currently implemented metadata https://github.com/Parsely/parsely-drupal/blob/master/parsely.module#L248-L259
- Users can set optional settings via module admin:
- Content ID Prefix: a string to ensure that when using multiple CMSs, there's no conflict on post IDs (default: blank)
- Track authenticated users: a boolean that indicates whether Parse.ly javascript is loaded if a user is logged into Drupal (default: true)
- Parse.ly javascript is loaded on all pages close to closing
</body>
tag assuming Parse.ly API Key is provided - Parse.ly metadata is loaded and configured properly on all metadata pages