Conversation
- Add AGENTS.md with development guidance and conventions - Create centralized DataService for managing application data - Add data.models.ts with typed interfaces for events, members, and links - Implement new footer component with social links and branding - Add member card component with staff profile support - Include staff profile images (9 new webp assets) - Refactor components to use DataService instead of local data - Update hero, projects, and event card components - Enhance main page layout and routing configuration - Update global styles for improved consistency
Deploying main-page with
|
| Latest commit: |
47f3a5d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://084be966.main-page-3fk.pages.dev |
| Branch Preview URL: | https://feat-landing-integration.main-page-3fk.pages.dev |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0eab59ae4d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| description: | ||
| 'Jornada en la UTP con charlas sobre FLOSS, Git, Python, desarrollo e inteligencia artificial de código abierto.', | ||
| location: 'UTP Sala Magistral 2', | ||
| date: '2025-10-10T08:00:00', |
There was a problem hiding this comment.
Include the venue timezone in event timestamps
These offset-less timestamps are parsed by new Date(...) in the browser's local timezone. For users outside Colombia, sorting, the upcoming/past transition, and the countdown therefore use a different instant—for example, this event becomes “past” at 08:00 in Tokyo rather than 08:00 in Pereira. Include an explicit -05:00 offset (or otherwise normalize the catalog timezone) for every event date.
Useful? React with 👍 / 👎.
| grid-template-columns: repeat( | ||
| var(--member-columns), | ||
| minmax(0, 176px) | ||
| ); |
There was a problem hiding this comment.
Keep the six-column member grid within its container
At the 1024px breakpoint the homepage passes six columns, so this rule creates 6 × 176px of tracks plus five gaps—1116px inside a section capped at 960px. The member grid consequently spills out of the section and causes horizontal overflow on common tablet/small-desktop widths. Allow the columns to shrink or keep the auto-fit layout until the viewport can accommodate all six cards.
Useful? React with 👍 / 👎.
| <img | ||
| [src]="photoUrl" | ||
| [alt]="name" | ||
| class="h-full w-full object-cover brightness-50 transition duration-300 sm:brightness-100 sm:group-hover:scale-105 sm:group-hover:brightness-50 sm:group-focus-within:scale-105 sm:group-focus-within:brightness-50" |
There was a problem hiding this comment.
Lazy-load the below-the-fold gallery images
These member cards are rendered several sections below the hero, but their images use the default eager loading behavior. The six portraits referenced by the homepage alone total about 1.3 MB, and the eagerly rendered event and project cards add roughly another 0.5 MB, so browsers begin downloading nearly 1.9 MB of imagery during the initial page load even when users never scroll to it. Add loading="lazy" to the below-the-fold member, past-event, and project images while keeping the hero eager.
Useful? React with 👍 / 👎.
Closes #89
Summary
Validation
npm run lintnpm run buildgit diff --check