Potential content sync mapping updates

[jeffpaul]

Is your enhancement related to a problem? Please describe.

The following are existing mappings in https://github.com/globeandmail/sophi-for-wordpress/blob/develop/includes/functions/content-sync.php that might be worth considering how future WordPress publishers might want different data sent to Sophi:

• [ ] accessCategory perhaps something other than free access (see https://github.com/globeandmail/sophi-for-wordpress/blob/e551ace09cbe7866bb5aed8c10408dbbe5a34b65/includes/functions/content-sync.php#L270)
• [x] alternate taxonomies besides what's sent in allSections (https://github.com/globeandmail/sophi-for-wordpress/blob/e551ace09cbe7866bb5aed8c10408dbbe5a34b65/includes/functions/content-sync.php#L274), sectionNames (https://github.com/globeandmail/sophi-for-wordpress/blob/e551ace09cbe7866bb5aed8c10408dbbe5a34b65/includes/functions/content-sync.php#L275), and tags (https://github.com/globeandmail/sophi-for-wordpress/blob/e551ace09cbe7866bb5aed8c10408dbbe5a34b65/includes/functions/content-sync.php#L277) if a site is using different ways to classify their posts
• [ ] isSponsored perhaps something other than false (see https://github.com/globeandmail/sophi-for-wordpress/blob/e551ace09cbe7866bb5aed8c10408dbbe5a34b65/includes/functions/content-sync.php#L285)
• [ ] perhaps some custom field (e.g. sophiCustomData) that by default gets nothing but could have a WordPress hook to adjust what gets sent in that field if a new WordPress client has something new, different, or otherwise unique and we don't want to wait for a plugin and Sophi release cycle to add support for a new field to be able to flex and capture that data? Perhaps a couple different custom fields representing different possible, expected data types?

Designs

n/a

Describe alternatives you've considered

Keep the $data variables as-is and make changes as needed in the future (e.g. shift the time and work to the future when we "know" that its needed versus trying to anticipate now and avoid an emergency change in the future).

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[jeffpaul]

Note that #308 covers the checkbox item above on categories/tags.