Depends on:
The pages that Via shows when sites are blocked aren't very good, either in visual design or in wording. Re-design and re-write them to be better.
The block pages are implemented in Checkmate
The code for these block pages can be found in Checkmate:
See below for screenshots and example links for the different block pages.
Checkmate's block pages are used by Via, Via 3 and Via HTML
All three Via's redirect to these Checkmate-hosted block pages when a page is blocked, so any changes made to the block pages in Checkmate apply to all three Via's. In particular, changes apply to both public Via and LMS's Via.
The design should be consistent with other pages in Via 3
The visual design should match the design of existing error pages in Via 3 so that the combined Via / Via 3 / Via HTML UI can be consistent. Via 3's existing error pages also match the design used in the LMS app, so that the combined LMS / Via experience is consistent.
The code for Via 3's error pages is here:
Here's what a Via 3 error page looks like:
The design should work in the LMS context
We can't tell LMS users to install the browser extension. You can't log in to your LMS account in the browser extension, so this instruction doesn't make sense in the LMS context.
The Via 3 error page above features a white box floating on a grey background. The grey background is needed in the LMS context to distinguish our iframe from the surrounding LMS. If the background is white then the user can't see where Canvas ends and Hypothesis begins and can't tell whether the error message is coming from Hypothesis or Canvas.
The horizontal and vertical centering of the dialog is also important for this reason.
Here's what the Via 3 error dialog looks like in the LMS context:
Current pages
Current page when the domain is not on our allow-list
Current page when the domain is marked as malicious on our blocklist
Current page when a publisher has requested that we block their site
Current page when a domain is an our blocklist for any other reason
E.g. when we block sites like YouTube.
Depends on:
Serve block warning pages from Checkmate(done)The pages that Via shows when sites are blocked aren't very good, either in visual design or in wording. Re-design and re-write them to be better.
The block pages are implemented in Checkmate
The code for these block pages can be found in Checkmate:
See below for screenshots and example links for the different block pages.
Checkmate's block pages are used by Via, Via 3 and Via HTML
All three Via's redirect to these Checkmate-hosted block pages when a page is blocked, so any changes made to the block pages in Checkmate apply to all three Via's. In particular, changes apply to both public Via and LMS's Via.
The design should be consistent with other pages in Via 3
The visual design should match the design of existing error pages in Via 3 so that the combined Via / Via 3 / Via HTML UI can be consistent. Via 3's existing error pages also match the design used in the LMS app, so that the combined LMS / Via experience is consistent.
The code for Via 3's error pages is here:
Here's what a Via 3 error page looks like:
The design should work in the LMS context
We can't tell LMS users to install the browser extension. You can't log in to your LMS account in the browser extension, so this instruction doesn't make sense in the LMS context.
The Via 3 error page above features a white box floating on a grey background. The grey background is needed in the LMS context to distinguish our iframe from the surrounding LMS. If the background is white then the user can't see where Canvas ends and Hypothesis begins and can't tell whether the error message is coming from Hypothesis or Canvas.
The horizontal and vertical centering of the dialog is also important for this reason.
Here's what the Via 3 error dialog looks like in the LMS context:
Current pages
Current page when the domain is not on our allow-list
Current page when the domain is marked as malicious on our blocklist
Current page when a publisher has requested that we block their site
Current page when a domain is an our blocklist for any other reason
E.g. when we block sites like YouTube.