Closed HughP closed 4 years ago
This issue has been automatically marked as stale because it has not had any recent activity. The resources of the Academic team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically close soon if no further activity occurs. Thank you for your contributions.
Issues #1664 and #1663 are related.
This issue has been automatically marked as stale because it has not had any recent activity. The resources of the Academic team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically close soon if no further activity occurs. Thank you for your contributions.
@gcushen
What about an approach like this:
allow the end user to define any schema.org attribute they want in the header and include that in the JSON+LD payload?
It might work like this:
schema_copyrightHolder = "Hugh Paterson III"
schema_isPartOf ""
schema_xsomeproperty
Then "scoop" all values of properties which start with schema_
package those into the payload. There might be better ways to guarantee exactly accurate information, but this would give end users a great deal of power.
I'm not sure how we might mark up something like the following:
"copyrightHolder": {
"@type": "Person",
"name": "Hugh Paterson III"
}
Greetings,
I am reading through the JSON+LD metadata files in the Academic Theme and I would appreciate some feedback (or guidance) from other theme users.
Two examples for discussion and improvement:
{{with author}}
this works for single author pages, but does not work with two (or more) authored pages. Is this a bug? or is this a "design feature"? can someone help me understand this particular situation?In general it is unclear to me if the goal of
/article.html
is just about describing blog posts — single pages which are part of the website, or if it is also about describing a publication which a particular webpage might be describing? If it is about describing blog posts then it would appear that the schema.org recommendation is to use https://schema.org/blogPost or https://schema.org/blogPosting be used. and https://schema.org/blogPosts on agregation pages like taxonomy lists. Some clear feedback here would be appreciated.config.toml
file and which are accessible via params so, they could theoretically be added to the JSON+LD payload. Is there a compelling story as to why they are not currently included? (I present a brief look at the uses of the Hugo-Academic and schema.org terms in a gist) per https://github.com/gcushen/hugo-academic/blob/c5b26892a9c6edd861c86993fce1c4cc234b9408/layouts/partials/jsonld/website.htmlAgain I seek feed back and information about the narrative for development. should I fork and send small commits?