-
Notifications
You must be signed in to change notification settings - Fork 48
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
Redesign showcase on splash #922
Conversation
14b2ef4
to
ec5da30
Compare
I really like where this is headed @victorlin (and it seems like most everyone agrees with this). I just made some minor tweaks. I'd be happy for this to go live except the issues with /pathogens, etc... and code clean up. I think it's your call for whether to:
|
@trvrb thanks for those tweaks, visually it's looking very polished. One more thing I want to try is border change on hover to mimic behavior of buttons on the same page. Code is quite messy so I'll clean it up with the aim to keep things visually identical. Since there are additional screenshot updates in this PR, I'll close #914 and consolidate all the screenshot changes into this PR as a single commit. |
Sounds good. Thanks @victorlin! |
fffe300
to
5e6764f
Compare
5e6764f
to
afb144b
Compare
32d2c7f
to
3711b69
Compare
cdce492
to
e71d5e1
Compare
Co-authored-by: Trevor Bedford <trevor@bedford.io>
- Add description and type - Ensure url is specific to match description - Remove "(narrative)" since new design will show type information Co-authored-by: Trevor Bedford <trevor@bedford.io>
Co-authored-by: Trevor Bedford <trevor@bedford.io>
Make each card bigger and display additional information. Static preview: <https://github.com/nextstrain/nextstrain.org/assets/13424970/b04c0f6e-d35c-4502-bd6e-b893e90b66ba> Co-authored-by: Trevor Bedford <trevor@bedford.io>
3711b69
to
08158d3
Compare
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.
Thanks for all of the work you've put into the redesign @victorlin 🌈
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.
Really nice work @victorlin! Only one little bug which needs fixing (isNarrative
prop), the rest of my comments can be split out to future work / discussion
|
||
useEffect(() => { | ||
async function getGroupLogo(group) { | ||
const response = await fetch(`/charon/getSourceInfo?prefix=/groups/${group}`); |
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.
Post-merge: check that the group logos are properly fetched (it's expected to not work on review app)
I've tested this locally with the appropriate IAM user + CONFIG_FILE="env/production/config.json"
and it works.
[following is not a request for changes, just discussion]
These requests don't feel right to me. If we used SSR then they could be made (and cached) server-side, but fundamentally it feels like data that should be hardcoded similarly to how showcase.yaml
is hardcoded. Maybe it's just fine, I don't know. Anyone else have thoughts?
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.
Hardcoding group logos in the YAML feels off to me. These aren't tracked in version control and can be changed by group owners at any time.
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.
Hardcoding group logos in the YAML feels off to me.
+1. I think the groups logo should be dynamic since we don't have control over them.
This removes the need to specify type in the YAML.
08158d3
to
c8ef39b
Compare
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 really like where this ended up @victorlin. 😀
Ideally the code can be more flexible, but right now things are looking good with the current content. Describe what sort of content is needed to keep things looking good.
bde50a3
to
13beec5
Compare
preview
Description of proposed changes
Adding more information to the showcase ("featured analyses") section.
Links
Checklist
Check if changes affect the resource index JSON revisionblab
for a group URL shows the blab group logo