Rerouted (regenerated, verified). Same repository and tag, but GitHub now builds the zip with different bytes, so it no longer matches the SHA-1 package.elm-lang.org recorded. The Lamdera package server serves a copy recovered from https://github.com/dillonkearns/elm-pages-v3-beta.
What we checked: Tag 8.0.0 is still on github.com/dillonkearns/elm-pages-v3-beta; its commit b7735572454e is from 2023-01-17 05:49 UTC, before the version was published (2023-01-17 05:52 UTC); elm.json is byte-identical to package.elm-lang.org's; the exposed modules match docs.json; the zip's SHA-1 is not the published one (GitHub's zip no longer comes out byte for byte the same), so the contents were checked instead.
The Lamdera compiler uses this copy and prints a one-line notice saying so. elm itself fails to download this version.
Details · package.elm-lang.org's zip: https://github.com/dillonkearns/elm-pages-v3-beta/zipball/8.0.0/
https://ogp.me/# https://developers.facebook.com/docs/sharing/opengraph
This module encapsulates some of the best practices for SEO for your site.
elm-pages will pre-render each of the static pages (in your content directory) so that
web crawlers can efficiently and accurately process it. The functions in this module are for use
with the head function that you pass to your Pages config (Pages.application).
import Date
import Head
import Head.Seo as Seo
-- justinmimbs/date package
type alias ArticleMetadata =
{ title : String
, description : String
, published : Date
, author : Data.Author.Author
}
head : ArticleMetadata -> List Head.Tag
head articleMetadata =
Seo.summaryLarge
{ canonicalUrlOverride = Nothing
, siteName = "elm-pages"
, image =
{ url = Pages.images.icon
, alt = articleMetadata.description
, dimensions = Nothing
, mimeType = Nothing
}
, description = articleMetadata.description
, locale = Nothing
, title = articleMetadata.title
}
|> Seo.article
{ tags = []
, section = Nothing
, publishedTime = Just (Date.toIsoString articleMetadata.published)
, modifiedTime = Nothing
, expirationTime = Nothing
}Will be displayed as a Player card in twitter See: https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/player-card
OpenGraph audio will also be included.
The options will also be used to build up the appropriate OpenGraph <meta> tags.
Will be displayed as a large card in twitter See: https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/summary
The options will also be used to build up the appropriate OpenGraph <meta> tags.
Note: You cannot include audio or video tags with summaries.
If you want one of those, use audioPlayer or videoPlayer
Will be displayed as a large card in twitter See: https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/summary-card-with-large-image
The options will also be used to build up the appropriate OpenGraph <meta> tags.
Note: You cannot include audio or video tags with summaries.
If you want one of those, use audioPlayer or videoPlayer
Will be displayed as a Player card in twitter See: https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/player-card
OpenGraph video will also be included.
The options will also be used to build up the appropriate OpenGraph <meta> tags.
These fields apply to any type in the og object types See https://ogp.me/#metadata and https://ogp.me/#optional
Skipping this for now, if there's a use case I can add it in: