DEV Community

Sumit Mishra
Sumit Mishra

Posted on

Inside my React portfolio: a glassmorphic bento grid with generated project data

My portfolio repository, rsume-site, is a React application built around a glassmorphic bento grid. The interesting part is not just the translucent cards. It is how the page separates its presentation from a generated content file, while keeping most of the interface in a straightforward component tree.

A small frontend stack

The package configuration uses React 19, TypeScript, Vite, Tailwind CSS 4, Framer Motion, and Lucide icons. There is no application server in the implementation described here. The page imports its content from src/data/auto-content.json, rather than fetching the project list during rendering.

In src/App.tsx, the root component composes a background, floating decorations, a glass shell, and individual cards. A reusable GlassCard wraps its children in a motion element with an opacity and vertical entrance animation. Each card supplies its own delay, so the layout can appear in stages without repeating the animation configuration everywhere.

The cards cover a hero, three featured skill categories, projects, an Arka link, and contact information. The hero delegates its title and floating code brackets to separate components. That keeps those visual effects out of the main layout code.

Project data is separate from project presentation

I find the project selection logic worth making explicit. The application copies and sorts the project array, placing the configured Arka repository first and ordering the remaining entries by update time. The phone-shaped project previews then exclude Arka and take only two projects. A separate “View all” link points to the GitHub profile.

Those phone previews are illustrative UI compositions, not screenshots of the linked applications. They use gradients, translucent blocks, a project title, and a hover animation. This distinction matters when describing what a visitor is actually seeing.

The README documents a refresh command that updates the generated JSON:

npm run sync
Enter fullscreen mode Exit fullscreen mode

It also says GitHub Actions refreshes projects daily and on main-branch pushes that touch the sync script. The page therefore consumes a saved snapshot of project metadata, not a live feed on every visit.

Running the frontend

The README lists these development commands:

npm run dev
npm run build
npm run lint
Enter fullscreen mode Exit fullscreen mode

The package file confirms that the production build runs tsc -b && vite build. It also provides npm run preview. The README does not include a complete dependency-installation walkthrough, so those commands should not be mistaken for a fully documented setup sequence.

The limits of this version

Some content is intentionally fixed in code, including the featured skill categories and email contact. The LinkedIn QR image comes from an external QR-generation service. That introduces a network dependency even though the project data itself is bundled.

I would describe this version as a focused portfolio frontend, not a CMS or a real-time GitHub dashboard. This walkthrough is based on source inspection, not a fresh build or performance benchmark. The concrete takeaway is architectural: a generated data file can sit behind an expressive React layout without making the rendering layer responsible for synchronization.

Top comments (0)