Skip to content

Implement a new header #601

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Implement a new header #601

wants to merge 1 commit into from

Conversation

m-mohr
Copy link
Collaborator

@m-mohr m-mohr commented May 20, 2025

When working on functionality to handle "external" STAC files better, it occured that the header is all mixed up. Some buttons belong to the root entity, some belong to the current entity (e.g. an item). This tries to bring the elements closer to where they belong.

Before:
Old

After (option A):
Option A

After (option B):
Option B

I'd highly appreciate feedback!

@silvester-pari
Copy link

Could you show in a screenshot where the API and source buttons have moved? Are they behind the "i" button(s) somewhere?

In general, I have the impression that now it feels more "split up" than before - before it was clear, everything related to navigation is on the top left, so going to the root, up, collection, browsing and searching; while on the top right it was everything related to "doing something with this", so source and share. I agree that maybe "API" and "language" didn't fit too well in the upper right corner.

How about keeping the catalog title and catalog browsing-related things in the top left and the language top right, and one level lower, the item title and item related navigation things in the top left and the source and sharing top right? E.g.:

image

@m-mohr
Copy link
Collaborator Author

m-mohr commented May 21, 2025

Thanks for the feedback, @silvester-pari.

The API and Source information is now the "i" button, indeed. The reason why up/collection/... are on the right side is that this gives them a predictable location. When quickly navigating, you had an unpredicable location of the buttons before due to the different length of the titles. The other buttons you usually only use once and thus there it's not so important to have predictable locations.

I also had a different version where the API title was on the left side and the browse/search was on the right. Would the following be better in your opinion? (also added above)

Option B

@silvester-pari
Copy link

That makes sense with the predictable position.

It looks better now, just the language button feels a bit out of place in the midst of the navigation buttons.

Plus, the "i" button is present twice, so it could be confusing, maybe still use a "source" button on the item level?

@m-mohr
Copy link
Collaborator Author

m-mohr commented May 21, 2025

I'm thinking about removing the i button from the site name and moving the information there to the landing page, where the metadata is.

The language button (it would also show authentication in the same button group, if available) is indeed a bit out of place, but I also don't see a better spot yet.

@m-mohr m-mohr added this to the 3.4.0 milestone Jun 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants