Rather than putting more work into our HTML transformation (which is good but not incredible), it might be a good idea to just ship Lens Viewer alongside our stack the same way we've done with the Substance Editor; Lens Viewer is one of the nicest JATS article browser viewers, and it's still being supported by eLife and Substance. Could link to it at the bottom of job status page (like the Substance editor link) and provide stable API endpoints for viewing documents in Lens.
Rather than putting more work into our HTML transformation (which is good but not incredible), it might be a good idea to just ship Lens Viewer alongside our stack the same way we've done with the Substance Editor; Lens Viewer is one of the nicest JATS article browser viewers, and it's still being supported by eLife and Substance. Could link to it at the bottom of job status page (like the Substance editor link) and provide stable API endpoints for viewing documents in Lens.