You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With MyST, we are positioning XRefs as the way to share content. That means we're encouraging scholarly authors to use XRefs to connect content across their own work, and further afield.
But, we currently build and deploy XRef information through a site build, which implicitly encodes assumptions about the web vs print distinction, such as image formats. Further down the road, we will increasingly want to distinguish how content is handled on web and print, and we must be careful not to end up in a situation where XRef content performs poorly when embedded in e.g. print media.
A concise summary of this topic is that we need to be careful to treat XRefs as a canonical sharing format.
Things to think about
image resolution / formats
only branching nodes
placeholder types
The text was updated successfully, but these errors were encountered:
With MyST, we are positioning XRefs as the way to share content. That means we're encouraging scholarly authors to use XRefs to connect content across their own work, and further afield.
But, we currently build and deploy XRef information through a site build, which implicitly encodes assumptions about the web vs print distinction, such as image formats. Further down the road, we will increasingly want to distinguish how content is handled on web and print, and we must be careful not to end up in a situation where XRef content performs poorly when embedded in e.g. print media.
A concise summary of this topic is that we need to be careful to treat XRefs as a canonical sharing format.
Things to think about
only
branching nodesThe text was updated successfully, but these errors were encountered: