Closed hepplerj closed 1 week ago
@sscott710 Okay, this Issue should collect together notes and feedback from @lmullen and @jgturner52. I've tried to break out tasks for each of us by tagging our usernames. My thinking here is you can focus on some of the content issues, while I tackle the CSS/layout issues since those might end up getting really fiddly.
The one thing to hold on for the moment is the missing images. I need to look into what's happening with the object storage and ensure those images are either missing or present on the server. I'll try and do that shortly so we can figure out a way to proceed.
Converted the placeholder URL to an Issue (#51) because there's a slightly larger issue going on with Wagtail. There are no hard-coded URLs for the scholarly essays, so the localhost URL comes from somewhere else. I imagine I missed a Wagtail setting somewhere that needs to be added.
I cannot replicate John's CSS issues in Browserstack, nor in my own local browsers (Firefox, Safari, Chrome). I'll do some more investigating but I'm not entirely certain what would cause his machine/browser to render the CSS differently.
Resolved the localhost issue for the essays: inside the wagtail CMS, under Sites, you have to set the site root. This will need to be updated manually when the site moves to its permanent location.
In general, why is Chrome + PC being inconsistent with TailwindCSS?
On mobile:
Style changes:
Specific layout issues:
Manuscript grid layout:
Data issues:
nan
values @sscott710 -- I would recommend we just edit the data in admin, and have the page number as "n/a"Essay pages:
Winterthur-specific: