Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[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

Open
1 task done
possumbilities opened this issue Oct 24, 2023 · 1 comment
Assignees
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

Comments

@possumbilities
Copy link
Contributor

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.
@possumbilities possumbilities added enhancement New feature or request 🟩 priority: low Low priority and doesn't need to be rushed 🌟 goal: addition Addition of new feature 📄 aspect: text Concerns the textual material in the repository 💻 aspect: code Concerns the software code in the repository labels Oct 24, 2023
@possumbilities possumbilities self-assigned this Oct 24, 2023
@possumbilities possumbilities changed the title [Functionality] make og:title differ from <title>, so that third-parties support Open Graph data import/display utilize an alternate non-hyphenated format [Functionality] make og:title differ from <title>, so that third-parties which support Open Graph data import/display utilize an alternate non-hyphenated format Oct 24, 2023
@possumbilities possumbilities added this to the v1.1 milestone Oct 24, 2023
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Oct 25, 2023
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Nov 1, 2023
@possumbilities possumbilities modified the milestones: v1.2, v1.3 Nov 1, 2023
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Nov 2, 2023
@possumbilities possumbilities modified the milestones: v1.3, v1.4 Nov 3, 2023
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Nov 4, 2023
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Mar 20, 2024
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Mar 27, 2024
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Apr 3, 2024
@TimidRobot TimidRobot added 🏁 status: ready for work Ready for work and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Apr 8, 2024
@possumbilities possumbilities modified the milestones: v1.4, v1.5 May 7, 2024
@TimidRobot
Copy link
Member

@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

@TimidRobot TimidRobot moved this to Backlog in WebDev Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Status: Backlog
Development

No branches or pull requests

3 participants