[Functionality] make og:title
differ from <title>
, so that third-parties which support Open Graph data import/display utilize an alternate non-hyphenated format
#41
Labels
💻 aspect: code
Concerns the software code in the repository
📄 aspect: text
Concerns the textual material in the repository
enhancement
New feature or request
🌟 goal: addition
Addition of new feature
🟩 priority: low
Low priority and doesn't need to be rushed
🏁 status: ready for work
Ready for work
Milestone
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 apipe
orcolon
would maybe work better for certain grammatical stylings.The use of the
hyphen
oren dash
in the<title>
element is a broadly used standard across websites, and thehyphen
is often the better choice since it may be read asdash
orhyphen
by software that doesn't treat it as a pause during assistive technology use.See:
However, as found in live example on Vox's website, if you set the
og:title
to be something different than the<title>
then theog: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 friendlyog:title
property that does not mirror the<title>
exactly.Reproduction
hyphen
in a compositional space where ahyphen
is not desired and now needs manual correction by the author.Resolution
The text was updated successfully, but these errors were encountered: