Skip to content

About - #32

Merged
skywalkerSam merged 8 commits into
mainfrom
about
Jul 17, 2025
Merged

About#32
skywalkerSam merged 8 commits into
mainfrom
about

Conversation

@skywalkerSam

@skywalkerSamskywalkerSam commented Jul 17, 2025

Copy link
Copy Markdown
Owner

About Remastered

Summary by CodeRabbit

  • New Features

    • Introduced an animated introduction, biography, and about-me section to the About page using new modular components.
    • Added animated text and emoji effects for a more engaging About page experience.
  • Style

    • Updated button and navigation menu components with reduced horizontal padding for a sleeker appearance.
    • Added new CSS animations for text sliding effects on the About page.
  • Chores

    • Added new dependencies to support advanced animations.
  • Content Update

    • Improved project description punctuation for clarity.

@vercel

vercelBot commented Jul 17, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

NameStatusPreviewCommentsUpdated (UTC)
skywalkersam-dev✅ Ready (Inspect)Visit Preview💬 Add feedbackJul 17, 2025 11:22am

@coderabbitai

coderabbitaiBot commented Jul 17, 2025

Copy link
Copy Markdown

Walkthrough

The changes introduce new modular React components and CSS animations for the About page, including an animated introduction, biography, and personal narrative. They add supporting constant data and GSAP animation dependencies. Minor UI padding adjustments are made for buttons and navigation menu triggers, and a project description is slightly refined.

Changes

File(s)Change Summary
_data/constants.tsNew module exporting nameList, doList, and emojiList as arrays of { text: string }.
src/app/about/_components/AboutMe.tsx
src/app/about/_components/Bio.tsx
src/app/about/_components/animated-intro.tsx
src/app/about/_components/intro.tsx
Four new React components: AboutMe, Bio, AnimatedIntro, and Intro, each rendering About page sections.
src/app/about/_components/animated-intro.cssNew CSS file defining animated text intro styles and keyframes.
src/app/about/page.tsxRefactored About page to use new modular components, removing previous inline content.
package.jsonAdded dependencies: @gsap/react and gsap.
src/components/ui/button.tsx
src/components/ui/navigation-menu.tsx
Reduced horizontal padding (px-4 → px-3) for button and navigation menu trigger.
_data/projects/ex-projects.tsMinor edit to "JS 101" project description punctuation.

Sequence Diagram(s)

sequenceDiagram
participant User
participant AboutPage
participant AnimatedIntro
participant Bio
participant AboutMe
User->>AboutPage: Visit /about
AboutPage->>AnimatedIntro: Render AnimatedIntro
AboutPage->>Bio: Render Bio
AboutPage->>AboutMe: Render AboutMe
Loading
sequenceDiagram
participant AnimatedIntro
participant constants.ts
participant GSAP
AnimatedIntro->>constants.ts: Import nameList, doList, emojiList
AnimatedIntro->>GSAP: useGSAP to animate headings on mount
AnimatedIntro->>AnimatedIntro: Render headings with animated text and emojis
Loading

Poem

A hop, a skip, a brand new day,
The About page shines in a modular way!
Animated intros jump and spin,
With GSAP magic tucked within.
Padding’s trimmed, the code feels light—
This bunny’s heart is full of delight! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/app/about/_components/animated-intro.css

Oops! Something went wrong! :(

ESLint: 9.23.0

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.

src/app/about/_components/animated-intro.tsx

Oops! Something went wrong! :(

ESLint: 9.23.0

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0d89bce and 8b626a6.

📒 Files selected for processing (2)
  • src/app/about/_components/animated-intro.css (1 hunks)
  • src/app/about/_components/animated-intro.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • src/app/about/_components/animated-intro.css
  • src/app/about/_components/animated-intro.tsx
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (9)
src/components/ui/navigation-menu.tsx (1)

43-45: Align spacing token via a shared constant to avoid future drift
Both this trigger and the default button now hard-code px-3. Consider extracting the horizontal padding value into a shared Tailwind plugin or a const CONTROL_HORIZONTAL_PADDING = "px-3" and referencing it through cva, so a single change updates every interactive control consistently.

_data/constants.ts (1)

1-11: Mark the arrays readonly (or as const) for safer, zero-cost immutability

These values act as design-time data. Lock them against accidental mutation:

-export const nameList: { text: string }[] = [+export const nameList = [
{ text: "Sam" },
{ text: "Skywalker" },
-];+] as const;-export const doList: { text: string }[] = [+export const doList = [
{ text: "Write" },
{ text: "Build" },
-];+] as const;-export const emojiList: { text: string }[] = [{ text: "👋" }, { text: "✌️" }];+export const emojiList = [{ text: "👋" }, { text: "✌️" }] as const;

TypeScript will infer literal types while preventing runtime cost.

src/app/about/_components/animated-intro.css (2)

6-8: Duplicate .slide selector may cause specificity confusion

Two separate .slide blocks target the same elements—one scoped under .hero-text, the other global. Rename the inner class or chain it (.hero-text .slide-inner) to make intent explicit and avoid overrides.

Also applies to: 11-15


17-22: Add will-change: transform for smoother 60 fps animation

The wrapper animates large translateY transforms for 21 s loops. Hinting the browser helps promote the layer and reduce jank:

 .wrapper {
display: flex;
flex-direction: column;
+ will-change: transform;
animation: wordSlider 21s infinite cubic-bezier(0.9, 0.01, 0.3, 0.99);
}

Also applies to: 23-48

src/app/about/_components/AboutMe.tsx (2)

4-27: Refactor punctuation styling for better maintainability and readability.

The current approach of wrapping each punctuation mark in individual <span> elements creates verbose JSX that's hard to maintain. Consider creating a utility function or using CSS classes to handle the styling more efficiently.

Here's a cleaner approach:

+const StyledText = ({ children }: { children: React.ReactNode }) => (+ <span className="text-sky-400">{children}</span>+);
export default function AboutMe() {
return (
<div className="flex min-h-screen flex-col items-center justify-center p-4">
- <p className="mx-auto max-w-3xl text-lg md:max-w-4xl md:text-xl md:tracking-wide lg:text-2xl">- A wise man once said, <span className="text-sky-400">"</span>To define- is to limit.<span className="text-sky-400">"</span> Nevertheless- <span className="text-sky-400">,</span> here we go- <span className="text-sky-400">...</span> i- <span className="text-sky-400">'</span>ve been learning to code for{" "}- <span className="text-sky-400">~</span>6 years now- <span className="text-sky-400">.</span>+ <p className="mx-auto max-w-3xl text-lg md:max-w-4xl md:text-xl md:tracking-wide lg:text-2xl">+ A wise man once said, <StyledText>"</StyledText>To define+ is to limit.<StyledText>"</StyledText> Nevertheless+ <StyledText>,</StyledText> here we go+ <StyledText>...</StyledText> i+ <StyledText>'</StyledText>ve been learning to code for{" "}+ <StyledText>~</StyledText>6 years now+ <StyledText>.</StyledText>

This approach reduces repetition and makes the code more maintainable.


3-3: Consider using semantic HTML for better accessibility.

The current div wrapper could be enhanced with more semantic HTML. Consider using <section> or <article> tags to provide better document structure for screen readers.

- <div className="flex min-h-screen flex-col items-center justify-center p-4">+ <section className="flex min-h-screen flex-col items-center justify-center p-4" aria-labelledby="about-me-heading">+ <h2 id="about-me-heading" className="sr-only">About Me</h2>
src/app/about/_components/intro.tsx (2)

14-19: Consider making the profile image URL configurable.

The GitHub profile image URL is hardcoded, which could make it difficult to maintain or reuse this component. Consider moving this to a configuration file or accepting it as a prop.

+interface IntroProps {+ profileImageUrl?: string;+ githubUsername?: string;+}+export default function Intro({ + profileImageUrl = "https://github.com/skywalkerSam.png",+ githubUsername = "skywalkerSam"+}: IntroProps) {

Or move it to a constants file:

+import { PROFILE_IMAGE_URL } from '_data/constants';
<Image
- src="https://github.com/skywalkerSam.png"+ src={PROFILE_IMAGE_URL}

8-12: Consider using semantic HTML for better accessibility.

The heading structure could be improved with proper semantic HTML and heading hierarchy.

 <div className="mt-36">
- <h1 className="py-9 text-xl md:text-3xl lg:text-4xl">+ <h1 className="py-9 text-xl md:text-3xl lg:text-4xl" role="banner">
👋 i'm Sam, i write and build things...
</h1>
</div>
src/app/about/page.tsx (1)

4-4: Consider removing commented-out code.

The commented-out Intro component import and usage suggest it might be temporary. If this component is no longer needed, consider removing it to keep the codebase clean.

-// import Intro from "./_components/intro";
- {/* <Intro></Intro> */}

If you're keeping it for A/B testing or future use, consider adding a comment explaining why it's commented out.

Also applies to: 9-9

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9871f3b and 0d89bce.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (11)
  • _data/constants.ts (1 hunks)
  • _data/projects/ex-projects.ts (1 hunks)
  • package.json (2 hunks)
  • src/app/about/_components/AboutMe.tsx (1 hunks)
  • src/app/about/_components/Bio.tsx (1 hunks)
  • src/app/about/_components/animated-intro.css (1 hunks)
  • src/app/about/_components/animated-intro.tsx (1 hunks)
  • src/app/about/_components/intro.tsx (1 hunks)
  • src/app/about/page.tsx (1 hunks)
  • src/components/ui/button.tsx (1 hunks)
  • src/components/ui/navigation-menu.tsx (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
src/app/about/page.tsx (3)
src/app/about/_components/animated-intro.tsx (1)
  • AnimatedIntro (7-60)
src/app/about/_components/Bio.tsx (1)
  • Bio (3-12)
src/app/about/_components/AboutMe.tsx (1)
  • AboutMe (1-30)
src/app/about/_components/animated-intro.tsx (1)
_data/constants.ts (3)
  • emojiList (11-11)
  • nameList (1-4)
  • doList (6-9)
🔇 Additional comments (11)
src/components/ui/button.tsx (1)

24-24: Confirm the 25 % reduction in horizontal padding doesn’t hurt tap-target accessibility
px-4px-3 drops the internal spacing by 4 px overall. On a h-9 (≈ 36 px) control that may already be at the WCAG minimum of 44 × 44 px when rendered on mobile, this could push the effective active area below the recommendation if the label is short (e.g. a single icon or 1–2 letters).

Before we propagate this token-size change across the palette, please sanity-check in the design system and on small touch devices.

package.json (1)

19-33: Prefer exact or peer-pinned GSAP versions to curb bundle regressions

Adding @gsap/react and gsap with a caret (^) means any future minor/patch can slip into builds and potentially break animations or inflate bundle size. Consider:

- "@gsap/react": "^2.1.2",- "gsap": "^3.13.0",+ "@gsap/react": "2.1.2",+ "gsap": "3.13.0",

or list them as peerDependencies if only the host app should own them.

src/app/about/_components/animated-intro.css (1)

1-9: Ensure CSS-nesting support is active

Nested rules (img { … }, .slide { … } inside .hero-text) rely on the CSS-Nesting spec. Tailwind requires tailwindcss/nesting (or postcss-nesting) in postcss.config.js. Without it, these styles collapse at build time.

_data/projects/ex-projects.ts (1)

16-19: LGTM – punctuation tweak only

src/app/about/_components/Bio.tsx (1)

3-11: Verify you don’t generate multiple <h1> tags on the About page

If AnimatedIntro or AboutMe already render an <h1>, this additional heading could break accessibility semantics. Consider demoting to <h2> or using aria-level when multiple level-one headings are unavoidable.

src/app/about/_components/intro.tsx (1)

21-28: Good security practices for external links.

The Twitter link correctly implements security best practices with target="_blank", rel="noopener noreferrer", and proper hover styling.

src/app/about/page.tsx (2)

1-3: Excellent modular component structure.

The refactoring from a monolithic About page to separate, focused components (AboutMe, AnimatedIntro, Bio) demonstrates good separation of concerns and maintainability.


10-12: Clean component composition.

The simple composition of the three components creates a clear, readable structure for the About page.

src/app/about/_components/animated-intro.tsx (3)

8-14: Well-implemented GSAP animation.

The GSAP animation is properly structured with good timing parameters (stagger: 0.2, duration: 1, ease: "power2.inOut") and uses the useGSAP hook correctly for React integration.


21-25: Good use of React keys and consistent structure.

The mapping over arrays with proper React keys and consistent styling approach is well implemented across all three sections (emojiList, nameList, doList).

Also applies to: 34-38, 46-50


3-3: No action needed: absolute imports from project root are valid

  • tsconfig.json defines "baseUrl": "." (line 27), enabling root-level imports.
  • _data/constants.ts exists at the project root and will resolve correctly.

Comment threadsrc/app/about/_components/animated-intro.tsx Outdated
@skywalkerSam
skywalkerSam merged commit 9bc11e5 into mainJul 17, 2025
4 checks passed
@coderabbitaicoderabbitaiBot mentioned this pull request Jul 20, 2025
@coderabbitaicoderabbitaiBot mentioned this pull request Aug 30, 2025
@coderabbitaicoderabbitaiBot mentioned this pull request Oct 17, 2025
@coderabbitaicoderabbitaiBot mentioned this pull request Dec 23, 2025
Sign up for freeto 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.

1 participant

@skywalkerSam