-
Notifications
You must be signed in to change notification settings - Fork 16
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
structured data on codebase landing pages + codemeta integration #351
Comments
https://codemeta.github.io/user-guide/ List of codemeta terms we should be mapping our metadata onto: https://codemeta.github.io/terms/ |
Example codemeta from codemeta: https://github.com/codemeta/codemeta/blob/master/codemeta.json Example codemeta from ASCL: https://ascl.net/1010.051/codemeta.json |
crosswalk in progress at https://docs.google.com/spreadsheets/d/1huJnxvk41AiMRpDwcdSX-Vg_Aw4_GHv1bhUFZyP_Ehs/edit?usp=sharing |
minor refactoring, need to still run `fs_api.add_codemeta()` to add to the FS
The root object is an instance of https://schema.org/SoftwareSourceCode
|
Example:
Response:
The From https://meta.discourse.org/t/embedding-discourse-comments-via-javascript/31963/394 |
add dedicated sponsors and funding fields to Codebase metadata as well as emitted codemeta |
minor refactoring, need to still run `fs_api.add_codemeta()` to add to the FS
Each codebase release should have its own specific CodeMeta associated with it. Embed structured json-ld data in the landing page, and provide it in the downloaded archive.
Google's schema.org testing tool (ignore warning about deprecation - https://developers.google.com/search/blog/2020/07/rich-results-test-out-of-beta):
https://search.google.com/structured-data/testing-tool/u/0/
https://search.google.com/test/rich-results
The text was updated successfully, but these errors were encountered: