quarto-dev / quarto-dev/quarto-cli
Missing Open Graph tags
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
At present Quarto inserts a number of Open Graph tags into blog posts.
There are, however, a couple of important tags missing:
og:typeandog:url.
These tags were also mentioned in https://github.com/quarto-dev/quarto-cli/issues/4882.
See also https://github.com/quarto-dev/quarto-cli/pull/14305 for proposed solution.
I have:
- searched the issue tracker for similar issues;
- installed the latest version of Quarto CLI; and
- formatted my issue following the Bug Reports guide.
Steps to Reproduce
Create a Quarto blog. Check <head> in rendered content.
Actual Behaviour
<meta property="og:title" content="">
<meta property="og:description" content="">
<meta property="og:image" content="">
<meta property="og:site_name" content="">
<meta property="og:image:alt" content="">
Expected Behaviour
<meta property="og:title" content="">
<meta property="og:description" content="">
<meta property="og:image" content="">
<meta property="og:site_name" content="">
<meta property="og:url" content="">
<meta property="og:type" content="">
<meta property="og:image:alt" content="">
Environment
This issue applies to Quarto 1.8.27 on Linux but I believe will be present in other versions and on other platforms.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed solution in pull request #14305 and reproduce the issue by creating a Quarto blog. Inspect the rendered content's and compare its Open Graph metadata with the expected tags in this issue. Done means the rendered head includes og:url and og:type alongside the existing tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100