Skip to content

chore: reorganize aireadi project page style#739

Open
Aydawka wants to merge 7 commits intomainfrom
project-style
Open

chore: reorganize aireadi project page style#739
Aydawka wants to merge 7 commits intomainfrom
project-style

Conversation

@Aydawka
Copy link
Collaborator

@Aydawka Aydawka commented Feb 19, 2026

Summary by Sourcery

Update the AI-READI project page content and layout and refine the shared ProjectAbout feature styling.

New Features:

  • Add a FAIRhub Portal hero button link on the AI-READI project page.
  • Introduce a responsive grid layout that adapts feature card columns based on the number of items in ProjectAbout.
  • Add a project timeline section describing year-by-year development milestones for AI-READI.

Enhancements:

  • Revise AI-READI project copy to be more concise and goal-focused, including goal, AI-readiness strategy, and FAIR Data Innovations Hub role descriptions.
  • Reorder and separate sections on the AI-READI project page to highlight funding, research partners, development approach, and timeline more clearly.
  • Restyle ProjectAbout feature cards with updated spacing, typography, and icon treatment for improved readability and visual hierarchy.

Documentation:

  • Update external links and labels on the AI-READI project page to point to the main project website and NIH award details.

@Aydawka Aydawka requested a review from megasanjay as a code owner February 19, 2026 07:47
@fairdataihub-bot
Copy link

Thank you for submitting this pull request! We appreciate your contribution to the project. Before we can merge it, we need to review the changes you've made to ensure they align with our code standards and meet the requirements of the project. We'll get back to you as soon as we can with feedback. Thanks again!

@vercel
Copy link

vercel bot commented Feb 19, 2026

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

Project Deployment Actions Updated (UTC)
fairdataihub-website Ready Ready Preview, Comment Mar 19, 2026 6:48am

Request Review

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Feb 19, 2026

Reviewer's Guide

Refines the AI-READI project page content and layout, updates external links, introduces a timeline and partners section earlier in the page, and modernizes the ProjectAbout feature grid styling and responsiveness.

File-Level Changes

Change Details Files
Update hero CTA buttons to point to the main AI-READI site and FAIRhub portal with improved accessibility attributes.
  • Change primary hero button URL from the docs subdomain to the main AI-READI website and update its aria label text.
  • Add a second hero button linking to the FAIRhub portal, opened in a new tab with appropriate rel attributes.
src/pages/aireadi.tsx
Revise AI-READI feature card content to use more concise, project-focused copy.
  • Retitle and rewrite the project goal feature card to a shorter, clearer description that highlights AI-ready, ethically sourced T2DM data.
  • Remove the data collection feature card to streamline the feature list.
  • Retitle the AI-readiness feature card and slightly adjust its description while preserving the FAIR/AI-ready emphasis.
  • Shorten and clarify the FAIR Data Innovations Hub role description to focus on FAIRhub tooling for researchers.
src/pages/aireadi.tsx
Reorder project sections to surface funding, partners, and timeline before development approach, and keep GitHub details grouped together.
  • Move the funding ProjectInfoSection higher on the page and remove its GitHub-related imagery and props.
  • Insert the ResearchPartners component immediately after funding instead of later in the page.
  • Insert the HorizontalTimeline component immediately after research partners and remove its previous placement at the end of the page.
  • Move the development approach ProjectInfoSection (with GitHub logo, URL, and links) to come after the new timeline section and restore its side image and alt text there.
src/pages/aireadi.tsx
Improve the ProjectAbout feature grid layout to adapt column count to feature length and refresh the visual design of feature cards.
  • Introduce a gridCols variable that chooses between two or three columns on medium screens based on the number of features.
  • Adjust the grid container spacing and top margin for better separation from the section header.
  • Redesign feature cards with softer rounded corners, lighter background, tweaked borders and shadows, and smoother hover transitions.
  • Change the header row within cards to horizontally align the icon and title, enlarging the icon and title typography.
  • Increase body text size and spacing for better readability while keeping optional link rendering intact, simplifying link classes slightly.
  • Add a trailing template literal space at the end of the section (likely a no-op/cleanup artifact).
src/components/project/about.tsx

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@fairdataihub-bot
Copy link

Thanks for making updates to your pull request. Our team will take a look and provide feedback as soon as possible. Please wait for any GitHub Actions to complete before editing your pull request. If you have any additional questions or concerns, feel free to let us know. Thank you for your contributions!

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've found 2 issues, and left some high level feedback:

  • The trailing { } at the end of ProjectAbout renders an extra text node with a space; it looks accidental and should be removed.
  • In ProjectAbout, the gridCols logic uses features.length > 3 ? md:grid-cols-2 : md:grid-cols-3; consider confirming this is intentional since more items resulting in fewer columns is a bit counterintuitive and may not match the intended layout.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The trailing `{` ` ` `}` at the end of `ProjectAbout` renders an extra text node with a space; it looks accidental and should be removed.
- In `ProjectAbout`, the `gridCols` logic uses `features.length > 3 ? md:grid-cols-2 : md:grid-cols-3`; consider confirming this is intentional since more items resulting in fewer columns is a bit counterintuitive and may not match the intended layout.

## Individual Comments

### Comment 1
<location> `src/pages/aireadi.tsx:21` </location>
<code_context>
       target: `_blank`,
-      ariaLabel: `AI-READI Documentation`,
+      ariaLabel: `AI-READI website`,
+      rel: `noopener`,
+    },
+    {
</code_context>

<issue_to_address>
**🚨 suggestion (security):** Consider using `noopener noreferrer` for external links opened in a new tab.

For `target="_blank"` links, it’s best to use `rel="noopener noreferrer"` to prevent both `window.opener` access and referrer leakage. Since there are several such buttons, consider applying this consistently wherever referrer data isn’t required.

Suggested implementation:

```typescript
    {
      text: `Learn more`,
      href: `https://aireadi.org/`, // update later if AI-READI gets its own docs URL
      target: `_blank`,
      ariaLabel: `AI-READI website`,
      rel: `noopener noreferrer`,

```

```typescript
      text: `Learn more`,
      href: `https://aireadi.org/`, // update later if AI-READI gets its own docs URL
      target: `_blank`,
      ariaLabel: `AI-READI website`,
      rel: `noopener noreferrer`,

```

Search the rest of `src/pages/aireadi.tsx` (and the broader codebase, if desired) for any link or button configs with `target: '_blank'` (or `target: "_blank"`). For each, add or update the `rel` property to `rel: 'noopener noreferrer'` (or backticked/quoted consistently with local code style) unless you explicitly need to send referrer data for that link.
</issue_to_address>

### Comment 2
<location> `src/components/project/about.tsx:73` </location>
<code_context>
+                        height={18}
+                      />
+                    </span>
+                    <span className="absolute -bottom-1 left-1/2 h-[2px] w-0 bg-pink-600 transition-all duration-300 group-hover:left-0 group-hover:w-full" />
+                  </a>
+                </div>
</code_context>

<issue_to_address>
**suggestion (bug_risk):** Hover underline currently responds to card hover instead of link hover.

Since `group` is on the card container, the `group-hover:*` classes fire when the whole card is hovered, not just this link. If you only want the underline to animate on link hover, move `group` onto the `<a>` or create a separate grouped wrapper for the link and scope the hover to that element instead.

Suggested implementation:

```typescript
                    className="group/link text-primary relative inline-flex items-center gap-1 text-sm font-semibold transition-colors duration-300 hover:text-pink-700"

```

```typescript
                    <span className="absolute -bottom-1 left-1/2 h-[2px] w-0 bg-pink-600 transition-all duration-300 group-hover/link:left-0 group-hover/link:w-full" />

```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

… into project-style

# Conflicts:
#	src/pages/aireadi.tsx
@megasanjay
Copy link
Member

megasanjay commented Feb 19, 2026

@megasanjay
Copy link
Member

@Aydawka could you fix the sourcery comments. We can merge this in for aireadi i think

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