We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
og:site_name
Beware that when building with 0.112.3, we lose og:site_name:
-- a/404.html +++ b/404.html @@ -3,7 +3,7 @@ <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> -<meta name="generator" content="Hugo 0.110.0"> +<meta name="generator" content="Hugo 0.112.3"> <meta name="robots" content="noindex, nofollow"> @@ -23,7 +23,7 @@ <meta property="og:title" content="404 Page not found" /> <meta property="og:description" content="Docsy does docs" /> <meta property="og:type" content="website" /> -<meta property="og:url" content="/404.html" /><meta property="og:site_name" content="Docsy" /> +<meta property="og:url" content="/404.html" /> <meta itemprop="name" content="404 Page not found"> <meta itemprop="description" content="Docsy does docs"><meta name="twitter:card" content="summary"/> <meta name="twitter:title" content="404 Page not found"/> diff --git a/about/index.html b/about/index.html index bbd685d..b0c6445 100644
We'll have to investigate this carefully. It's not clear to me whether this is a Hugo "bug" or a sign that our config needs to be updated.
The text was updated successfully, but these errors were encountered:
Upgrade Hugo to 0.112.7 (google#1531)
bb46cd6
en
Nice catch! The latter is the case, our config needs to be updated. This is done in #1534.
Sorry, something went wrong.
Upgrade Hugo to 0.112.3 (google#1531)
e538970
8665490
<title>
Successfully merging a pull request may close this issue.
Beware that when building with 0.112.3, we lose
og:site_name
:We'll have to investigate this carefully. It's not clear to me whether this is a Hugo "bug" or a sign that our config needs to be updated.
The text was updated successfully, but these errors were encountered: