[Functionality] make `og:title` differ from `<title>`, so that third-parties which support Open Graph data import/display utilize an alternate non-hyphenated format

[possumbilities]

Description

Third-party services like Google Docs enable the conversion of a URL into its respective title, linked. However, this proves a challenge when working in a compositional space where a hyphen is not typically used as a separator and a pipe or colon would maybe work better for certain grammatical stylings.

The use of the hyphen or en dash in the <title> element is a broadly used standard across websites, and the hyphen is often the better choice since it may be read as dash or hyphen by software that doesn't treat it as a pause during assistive technology use.

See:

• NY Times
• Wikipedia
• Mozilla
• Slack
• WordPress
• (and many many more)

However, as found in live example on Vox's website, if you set the og:title to be something different than the <title> then the og:title takes precedence.

Currently, the og:title tags are displayed with a third-party plugin, and there's hope to move that into core theme functionality at some point. In the meantime, it might be possible to override this behavior to output a better more compositional friendly og:title property that does not mirror the <title> exactly.

Reproduction

1. create an empty Google Doc
2. paste a URL from creativecommons.org
3. click the now pasted link and click the button "convert url to its title?"
4. See the <title> be imported with a hyphen in a compositional space where a hyphen is not desired and now needs manual correction by the author.

Resolution

• I would be interested in resolving this bug.

[TimidRobot]

@possumbilities please coordinate with me when you're ready to implement this so we can add Open Graph data to the CC Legal Tools at the same time