Skip to content
This repository was archived by the owner on Jun 28, 2026. It is now read-only.
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 4 additions & 30 deletions src/app/about/page.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -91,36 +91,10 @@ export default function AboutPage() {
Frontend
</Typography>
<ul>
<li>Next.js 14 + TypeScript</li>
<li>Material-UI (MUI) v5 + Emotion</li>
<li>SWR / React Query</li>
<li>NextAuth.js</li>
</ul>
</CardContent>
</Card>
</Grid>
<Grid size={{ xs: 12, md: 6 }}>
<Card
sx={{
height: '100%',
borderRadius: 2,
boxShadow: '0 4px 12px rgba(0, 0, 0, 0.05)',
}}
>
<CardContent>
<Typography
variant="h6"
component="h3"
gutterBottom
sx={{ color: 'primary.main', fontWeight: 600 }}
>
Backend
</Typography>
<ul>
<li>NestJS 10 + TypeScript</li>
<li>tRPC</li>
<li>Prisma ORM</li>
<li>GitHub API (Octokit)</li>
<li>Next.js 16 + TypeScript</li>
<li>Material-UI (MUI) v9 + Emotion</li>
<li>TanStack Query v5</li>
<li>Tailwind CSS</li>
Comment on lines +94 to +97

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The GitHub API (Octokit) dependency is still present in package.json (line 29) and is a core part of this application's architecture (fetching data in a static frontend-only app). It should be included in the technology stack list to accurately reflect the project's dependencies as intended by this PR.

                    <li>Next.js 16 + TypeScript</li>
                    <li>Material-UI (MUI) v9 + Emotion</li>
                    <li>TanStack Query v5</li>
                    <li>Tailwind CSS</li>
                    <li>GitHub API (Octokit)</li>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify Tailwind CSS configuration and usage in the project

echo "=== Checking for Tailwind configuration files ==="
fd -t f 'tailwind.config' -x echo "Found: {}"

echo -e "\n=== Checking for Tailwind imports in CSS files ==="
rg -n '@import.*tailwind|@tailwind' -g '*.css' -g '*.scss'

echo -e "\n=== Checking for Tailwind class usage (sample) ==="
rg -n 'className=.*\b(bg-|text-|p-|m-|flex|grid|rounded)' --type tsx --type ts -C 1 | head -20

echo -e "\n=== Checking package.json for Tailwind ==="
cat package.json | jq '.dependencies.tailwindcss // .devDependencies.tailwindcss // "not found"'

Repository: kanywst/IssueHub

Length of output: 354


Remove Tailwind CSS from the About page technology stack.

Tailwind CSS v4 is properly configured in the project (@import 'tailwindcss' in globals.css), but it is not actually used anywhere in the codebase. The component and all styling rely exclusively on Material-UI's sx prop. The technology stack should accurately reflect only the libraries actively in use.

Either remove Tailwind CSS from the displayed stack, or refactor styling to use Tailwind instead of Material-UI.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/app/about/page.tsx` at line 97, The About page shows Tailwind CSS in the
technology stack but the component uses Material-UI sx styles (no Tailwind
classes); remove the incorrect entry by deleting the <li>Tailwind CSS</li>
element from the tech stack list in src/app/about/page.tsx (or alternatively, if
you prefer Tailwind, replace Material-UI sx usage with Tailwind utility classes
across the component); reference the tech list JSX and the Material-UI sx usages
when making the change.

</ul>
</CardContent>
</Card>
Comment on lines 91 to 100

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The PR description mentions fixing the Grid layout structure, but the current change only removes the boundary between the two grid items (previously lines 101-102). This effectively merges them into a single grid item. However, if the opening <Grid> tag (not visible in this diff) still has size={{ md: 6 }}, the card will remain at half-width on medium screens. To properly fix the layout for a single card, the opening tag should be updated to size={{ xs: 12 }} or the grid item wrapper should be removed entirely.

Expand Down