-
Notifications
You must be signed in to change notification settings - Fork 3
Update item page #49
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
Update item page #49
Conversation
oliverroick
commented
Mar 26, 2025
- Updates page header to match other pages
- Adds links (ref [STAC] Add Assets list and Links in HTML item page #43).
- Adds items assets (ref [STAC] Add Assets list and Links in HTML item page #43). The asset display is the same as the one on the collection page. Additional properties are shown in a disclosure, otherwise the page would be very long and convoluted.
- Updates the styling of item properties using columns and pretty print for property values, which makes complex JSON object more readable. (I'll update other pages to match this once the change is approved here)
- Update map positioning, it now stays in place when you scroll. (I'll update other pages to match this once the change is approved here)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a few ideas for improving the asset details formatting, but nothing big. I love the sticky map when you scroll through the item/asset properties!
<p class="small text-monospace text-muted mb-0">{{ key }}</p> | ||
{% if asset.title %}<p class="mb-0"><b>{{ asset.title }}</b></p>{% endif %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm not pleased with how that looks either. It's very convoluted and I'd like to revisit that at some point, maybe we can get some help from a designer.
In the meantime, I've tried your suggestion and it looks ... ok.

I've tried some other options as well.
I like Option A, because it has a clear header. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Option A looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could get a designer to contribute to https://github.com/developmentseed/stac-fastapi-html-middleware
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Option A looks good to me!
Pushed the update with that option
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could get a designer to contribute to https://github.com/developmentseed/stac-fastapi-html-middleware
I'll forward the change to the templates 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😍
Co-authored-by: Henry Rodman <[email protected]>