Full deployment history for this project.
⚡ Bolt: [performance improvement] Apply Next.js optimized fonts to DOM The `Geist` and `Geist_Mono` fonts were being initialized in `app/layout.tsx` but their resulting classes/variables were never applied to the DOM. This meant the application fell back to downloading and rendering unoptimized default system fonts, missing out on Next.js's font optimization features (like zero layout shift and automatic preloading). This commit fixes the issue by updating the font initializers to output CSS variables and setting `display: 'swap'` for better rendering behavior. These variables are then passed to the `<body>` element. Finally, `tailwind.config.ts` is updated to map the `sans` and `mono` font families to these variables. Additionally, cleaned up duplicate `maxLength` props in `app/page.tsx` input fields that were causing lint errors. Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
🎨 Palette: Add aria-label to scroll down indicator link Added an `aria-label` to the animated scroll-down indicator link to ensure it's accessible and provides context to screen reader users. Also resolved duplicate `maxLength` props found on multiple inputs during linting. Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
🎨 Palette: Enhance form required indicators and add aria-label to anchor link - Added `aria-label` to the "#about" scroll link for screen reader accessibility. - Added visible `focus-visible` ring to the "#about" scroll link for keyboard navigation. - Added visual required indicator (*) with `aria-hidden="true"` to Name, Email, and Discord Username inputs in the RSVP form. - Fixed duplicate `maxLength` props on input fields. Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
🛡️ Sentinel: [security improvement] Add input length limits to form fields Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
🛡️ Sentinel: Add client-side input validation Add required and maxLength attributes to the RSVP form's input fields (name, email, discord) to prevent rudimentary denial-of-service (DoS) via excessively large inputs and to enforce basic data integrity without breaking existing functionality. Includes a minor pnpm-lock.yaml refresh triggered by pnpm install, needed to run pnpm lint. Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
Optimize ParticlesBackground by converting to React Server Component Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
Merge pull request #5 from mbarbine/bolt-extract-particles-6571945452627096433 ⚡ Bolt: [performance improvement] Enable React Server Component for Home Page
Merge pull request #6 from mbarbine/sentinel-secure-cookie-1634625605775909452 🛡️ Sentinel: [security improvement]
🛡️ Sentinel: Secure cookie implementation for sidebar state Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
Merge pull request #3 from mbarbine/sentinel-add-security-headers-11496788952964497257
Merge pull request #4 from mbarbine/palette-a11y-music-controls-14729073178294324185
⚡ Bolt: Extract ParticlesBackground to enable Server Component for page Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
feat: add aria labels and focus styles to music player controls Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
Add baseline security headers to next.config.mjs Added standard HTTP security headers (X-Content-Type-Options, X-Frame-Options, X-XSS-Protection, Referrer-Policy, and Strict-Transport-Security) to mitigate common web vulnerabilities like clickjacking and MIME-sniffing. Recorded the security learning in .jules/sentinel.md. Co-authored-by: mbarbine <3211492+mbarbine@users.noreply.github.com>
Fix React Server Components CVE vulnerabilities Updated dependencies to fix Next.js and React CVE vulnerabilities. The fix-react2shell-next tool automatically updated the following packages to their secure versions: - next - react-server-dom-webpack - react-server-dom-parcel - react-server-dom-turbopack All package.json files have been scanned and vulnerable versions have been patched to the correct fixed versions based on the official React advisory. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>