Revamp New Alexandria Commentary widget

[jacobwegner]

The previous endpoint feeding the widget returns 5xx errors.

There seem to be other endpoints backing the commentaries:

• https://homer.chs.harvard.edu/read/urn:cts:greekLit:tlg0012.tlg001.perseus-grc2:1.1-1.30
• https://homer.chs.harvard.edu/api/comments/?urn_search=urn:cts:greekLit:tlg0012.tlg001.perseus-grc2:1.1&format=json
• https://homer.chs.harvard.edu/graphql

The GraphQL endpoint has the most similar structure to the old endpoint, but there are still changes to be resolved, and I've hit quite a few CORS issues trying to work through it.

Want to circle back here when we have a bit more time.

https://nicedoc.io/lokiuz/redraft may be useful rendering the newer content blocks.

[jacobwegner]

(https://tinyurl.com/gql-chs-api has a sample query)

[jacobwegner]

The CHS team tells us that the GraphQL endpoint is deprecated; they're willing to work help resolve CORS issues, but I'm also writing a small proxy that will:

• Handle CORS issues (because...proxy!)
• Render Draft.js blocks back to HTML
• Cache responses to the upstream (might also consider sticking these behind the Scaife Viewer Fastly instance)

This would allow backwards compatibility with the widget as far as the shape of the query.

There might be more to do to "rank" responses from the API (CHS team mentioned there was some custom sorting happening on the old backend), and there isn't always a 1:1 between passage provided and returned on their actual site (30 line ranges, for example), so we might want to also consider just doing an ingestion of everything in the commentary and moving to a similar model of what we've done for HMT.

In that model, we'd still make use of the proxy and image hosting, but need to ensure we're doing right by CHS as far as licensing, attributions, etc.

[jacobwegner]

(Another small snippet we might want to land on the widget is ensuring that long links don't overflow the sidebars on SV1):

a {
    text-overflow: ellipsis;
    max-width: 15vw;
    overflow: hidden;
    display: block;
    white-space: nowrap;
}

[jacobwegner]

vs

[jacobwegner]

Our proxy server was knocked offline, but I've brought it back up.

https://opencommentaries.org/ (https://codeberg.org/charles/open_commentaries) will be the new platform that we'll want to switch over to at some point.