-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revision of title block #33
Comments
Another possibility is to keep the fixed title block but turn it into a row with other (fixed) blocks that contain:
Although this reduces the role of the first painted canvas as a kind of hero image. |
Here sketches of a title at the top of the page, a sticky menu at the bottom (that appears when scrolling the exhibition), and a chapter title. It does seem a more focussed start than the previous sketch. (We have to take into account that the exhibition will also be rendered stand-alone, without the blue header on top.) I added the arrows as a way to go to the next/previous heading. Not sure if that's useful. |
@sammeltassen Do they headings indicate a new range? |
@stephenwf Yes indeed–and I realise ranges can be more complex, like different views on the same exhibition, but this is a simple interpretation as as TOC. |
Thanks @sammeltassen we will assume a single top level range on the Manifest with non-nested ranges that include one or more canvas IDs in that case, with labels to make the ToC. What does the menu in your latest image look like when open? |
I don't have a visual of that yet. The problem I was facing is that users need to be able to unfold the TOC at the top of the exhibition, but also from the bottom menu after the heading disappeared. It would be good if both TOCs are the same. So perhaps the TOC appears in a modal (like a text panel)? Then the downward pointing arrow in the first image should be a hamburger like in the bottom bar. |
Just to clarify if my understanding is correct:
is that correct? ... so why change the first top arrow to a burger? You need the arrow to navigate to page 2, and you can open the TOC from the Table Of Contents link. |
Yes you're right. I think the modal can contain some additional information:
Instead of "table of contents" the link at the top right could read "about" |
Hi Jules. |
Yes I will, but this will need to wait until Mon |
Hi @sammeltassen with the option of truncating any labels that are too long? thanks. |
Hi @sammeltassen here is an example of the agreed form for the
|
@funkydunc Some additional sketches below for the main title, menu bar and toc. Important changes:
|
So this also means that the toc won't be available directly from the top of the page, which is fine I guess. The menu bar only appears when the first canvas block hits the top of the page. On mobile it can stay at the bottom for easy reach (we could actually give this a try on desktop as well–in which case the menu bar could be visible immediately? see the sketch). |
Hi @sammeltassen Thanks for this update. What do you think about having the sticky menu bar at the top initially, instead of the existing Exhibition title, like this? Then the menu bar is always there consistently, and the TOC is always viewable from one place. (This means retaining the Title in the bar). |
@funkydunc I think I'd prefer the sticky footer option because it doesn't compete with the real menu bar and can include the title of the first chapter, which would be too much to put at the top initially |
Elaboration of a new feature described in:
Exhibition pages always start with a title block on the top left:
This is good for recognisability (publications and collections have a similar title block in the same position) but it also limits the layout options of the first part of exhibitions. We aim to add support for IIIF ranges in exhibitions as well later this year, which would be used for making a table of contents. This adds a requirement for an overview of chapters, which needs to be taken into account for this revision.
Some solutions:
The text was updated successfully, but these errors were encountered: