creativecommons / creativecommons/vocabulary-theme

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

Open
#41 1 comment 0 reactions 1 assignee Claimed by @possumbilities View on GitHub
🌟 goal: addition 🏁 status: ready for work 💻 aspect: code 📄 aspect: text enhancement 🟩 priority: low
Dominant language
PHP
Stars
6
Forks
7
Avg merge
1d 8m
Merged PRs (30d)
6

Description

## 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 `` 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](https://vox.com), 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
<!-- Provide detailed steps to reproduce the bug -->
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
<!-- Replace the [ ] with [x] to check the box. -->
- [x] I would be interested in resolving this bug.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.