Add some JSON-LD data to pages #1564
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NickSto
added
the
new-feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the start of an implementation of #1442.
This inserts the data into a
<script>tag in the<head> of each page. Here's an example (formatted for readability):{ "@context": "http://schema.org/", "@type": "Event", "name": "Galaxy Community Call: Release 22.05", "startDate": "2022-06-23", "endDate": "2022-06-23", "contact": [ { "@type": "Person", "name": "John Davis" }, { "@type": "Person", "name": "Marius van den Beek" } ], "url": "https://galaxyproject.org/events/2022-06-23-community-call/" }One issue this faces is that the
contactandauthorsfields are currently just raw strings. We're moving to a structured format, which this PR is compatible with, but for now it does its best by trying to split these fields on commas.