Skip to content

Conversation

@fengelniederhammer
Copy link
Contributor

@fengelniederhammer fengelniederhammer commented Dec 17, 2025

resolves #977

Summary

so that in a next step, that part of the footer can actually be rendered in React (since it depends on the page state)

Screenshot

PR Checklist

- [ ] All necessary documentation has been adapted.
- [ ] The implemented feature is covered by an appropriate test.

@vercel
Copy link

vercel bot commented Dec 17, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
dashboards Ready Ready Preview, Comment Dec 19, 2025 9:54am

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR refactors the footer structure to move the "download data" button and related components closer to React-rendered content in preparation for rendering that portion of the footer in React. The refactoring removes the SecondaryFooter component and relocates footer content from the layout level to individual pages.

Key changes:

  • Removed the SecondaryFooter component and its slot-based rendering
  • Moved footer content (DataInfo, download buttons, last updated info) from layout templates into page-specific implementations
  • Restructured the DOM hierarchy to use flexbox layouts with h-screen and h-full for proper vertical spacing

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
website/src/pages/index.astro Moved DataInfo directly into page content with border styling
website/src/layouts/base/footer/SecondaryFooter.astro Deleted entire component file
website/src/layouts/base/footer/Footer.astro Removed SecondaryFooter import and slot usage
website/src/layouts/base/BaseLayout.astro Changed body from min-h-screen to h-screen, moved Header outside of grow container, removed secondary-footer slot
website/src/layouts/OrganismPage/SingleVariantOrganismPageLayout.astro Removed gs-app wrapper and LAPIS configuration (moved to parent)
website/src/layouts/OrganismPage/OrganismViewPageLayout.astro Added gs-app wrapper, footer components (AccessionsDownloadButton, LastUpdatedInfo, DataInfo) with flexbox layout
website/src/layouts/OrganismPage/DataPageLayout.astro Removed footer-related props and rendering, added flexbox container structure
website/src/components/views/compareSideBySide/GenericCompareSideBySidePage.astro Removed gs-app wrapper (now in parent component)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

</head>

<body class='flex min-h-screen flex-col'>
<body class='flex h-screen flex-col'>
Copy link

Copilot AI Dec 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing from min-h-screen to h-screen restricts the body height to exactly the viewport height. This will cause content overflow issues on pages with content taller than the viewport, preventing users from scrolling to see all content. Consider keeping min-h-screen or ensure all pages using this layout can fit within a single viewport.

Suggested change
<body class='flex h-screen flex-col'>
<body class='flex min-h-screen flex-col'>

Copilot uses AI. Check for mistakes.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The body needs a defined height so that h-full inside flex and grow works. The content does overflow the body, but it looks like it works, so I assume that this is fine?

---

<OrganismViewPageLayout view={view} downloadLinks={downloadLinks}>
<gs-app lapis={getLapisUrl(view.organismConstants.organism)}>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I deleted this line (moved to OrganismViewPageLayout) and reformatted the rest.

…ser to React-rendered content

so that in a next step, that part of the footer can actually be rendered in React (since it depends on the page state)

resolves #977
@fengelniederhammer fengelniederhammer force-pushed the 977-move-the-download-data-button-into-a-react-component branch from 6bbe89b to 98d0fc4 Compare December 19, 2025 09:54
@fengelniederhammer fengelniederhammer changed the base branch from 973-migrate-compare-side-by-side-to-react to 981-migrate-covid-compare-side-by-side-page-to-react December 19, 2025 09:54
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.

Move the "download data" button closer to React rendered content

2 participants