Merge pull request #1 from github-samples/init

chore: initialize Next.js project with TypeScript and Tailwind CSS

Author: LadyKerr

.github/copilot-instructions.md

@@ -0,0 +1,81 @@
+# Copilot Instructions for Gitfolio
+
+## Project Overview
+Gitfolio is a **single-page portfolio template** for developers. All user-customizable content lives in `app/page.tsx`. This is a beginner-friendly template—keep changes simple and well-commented.
+
+## Architecture
+
+### Single-File Content Model
+- **`app/page.tsx`** - Contains ALL portfolio content and components (nav, hero, projects, about, contact, footer)
+- Components are defined at bottom of file: `ProjectCard`, `SocialLink`, `ArrowRightIcon`, `ArrowUpRightIcon`
+- No separate component files—intentionally flat for beginner accessibility
+
+### GitHub Pages Deployment Pattern
+This project uses a **dual-environment basePath** pattern for local dev + GitHub Pages:
+
+```tsx
+// In page.tsx - for images
+const basePath = process.env.NODE_ENV === "production" ? "/gfbs3-portfolio-demo" : "";
+src={`${basePath}/me.png`}
+
+// In next.config.ts - for routing
+basePath: isProd ? "/gfbs3-portfolio-demo" : "",
+```
+
+**Critical**: When users fork this repo, they must update the repo name in BOTH files.
+
+## Design System
+
+### Color Palette (Tailwind classes)
+| Color | Primary Use | Tailwind Classes |
+|-------|-------------|------------------|
+| Cyan | Links, accents, tech | `cyan-400`, `cyan-500`, `cyan-700` |
+| Fuchsia | Highlights, emphasis | `fuchsia-400`, `fuchsia-500`, `fuchsia-600` |
+| Yellow | CTAs, warnings | `yellow-400`, `yellow-500` |
+| Purple | Gradients | `purple-400`, `purple-500` |
+
+### Glow Effects Pattern
+```tsx
+// Text glow
+className="drop-shadow-[0_0_8px_rgba(34,211,238,0.6)]"
+
+// Box glow on hover  
+className="hover:shadow-[0_0_20px_rgba(34,211,238,0.4)]"
+```
+
+### ProjectCard Component
+```tsx
+<ProjectCard 
+  title="PROJECT_NAME"      // UPPERCASE_SNAKE_CASE convention
+  description="..."
+  tags={["REACT", "API"]}   // Uppercase tags
+  color="cyan"              // cyan | fuchsia | purple | yellow
+  href="https://..."
+/>
+```
+
+## Key Files
+
+| File | Purpose |
+|------|---------|
+| `app/page.tsx` | All content + components |
+| `app/layout.tsx` | Metadata, fonts (Geist) |
+| `app/globals.css` | Tailwind imports only |
+| `next.config.ts` | Static export + basePath |
+| `.github/workflows/deploy.yml` | GitHub Pages CI/CD |
+| `public/me.png` | Profile image location |
+
+## Commands
+```bash
+npm run dev    # Local development at localhost:3000
+npm run build  # Production build (static export to /out)
+npm run lint   # ESLint check
+```
+
+## When Helping Users
+
+1. **Content changes** → Edit `app/page.tsx` only
+2. **Adding images** → Place in `/public`, use `${basePath}/filename` pattern
+3. **Deployment issues** → Check basePath matches repo name in both config files
+4. **Styling** → Use existing Tailwind classes; maintain cyberpunk aesthetic
+5. **New sections** → Follow existing section pattern with `id` for nav linking

.github/workflows/deploy.yml

@@ -0,0 +1,93 @@
+# Sample workflow for building and deploying a Next.js site to GitHub Pages
+#
+# To get started with Next.js see: https://nextjs.org/docs/getting-started
+#
+name: Deploy Next.js site to Pages
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["main"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Detect package manager
+        id: detect-package-manager
+        run: |
+          if [ -f "${{ github.workspace }}/yarn.lock" ]; then
+            echo "manager=yarn" >> $GITHUB_OUTPUT
+            echo "command=install" >> $GITHUB_OUTPUT
+            echo "runner=yarn" >> $GITHUB_OUTPUT
+            exit 0
+          elif [ -f "${{ github.workspace }}/package.json" ]; then
+            echo "manager=npm" >> $GITHUB_OUTPUT
+            echo "command=ci" >> $GITHUB_OUTPUT
+            echo "runner=npx --no-install" >> $GITHUB_OUTPUT
+            exit 0
+          else
+            echo "Unable to determine package manager"
+            exit 1
+          fi
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: ${{ steps.detect-package-manager.outputs.manager }}
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+        with:
+          # Automatically inject basePath in your Next.js configuration file and disable
+          # server side image optimization (https://nextjs.org/docs/api-reference/next/image#unoptimized).
+          #
+          # You may remove this line if you want to manage the configuration yourself.
+          static_site_generator: next
+      - name: Restore cache
+        uses: actions/cache@v4
+        with:
+          path: |
+            .next/cache
+          # Generate a new cache whenever packages or source files change.
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json', '**/yarn.lock') }}-${{ hashFiles('**.[jt]s', '**.[jt]sx') }}
+          # If source files changed but packages didn't, rebuild from a prior cache.
+          restore-keys: |
+            ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json', '**/yarn.lock') }}-
+      - name: Install dependencies
+        run: ${{ steps.detect-package-manager.outputs.manager }} ${{ steps.detect-package-manager.outputs.command }}
+      - name: Build with Next.js
+        run: ${{ steps.detect-package-manager.outputs.runner }} next build
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: ./out
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex, sexual characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+*   Using welcoming and inclusive language
+*   Being respectful of differing viewpoints and experiences
+*   Gracefully accepting constructive criticism
+*   Focusing on what is best for the community
+*   Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+*   The use of sexualized language or imagery and unwelcome sexual attention or advances
+*   Trolling, insulting/derogatory comments, and personal or political attacks
+*   Public or private harassment
+*   Publishing others' private information, such as a physical or electronic address, without explicit permission
+*   Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at opensource@github.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing to Gitfolio
+
+First off, thanks for taking the time to contribute! 🎉
+
+The following is a set of guidelines for contributing to this project. These are mostly guidelines, not rules. Use your best judgment and feel free to propose changes to this document in a pull request.
+
+## 🚀 Getting Started
+
+1.  **Fork the repository** on GitHub.
+2.  **Clone your fork** locally:
+    ```bash
+    git clone https://github.com/your-username/gfbs3-portfolio-demo.git
+    cd gfbs3-portfolio-demo
+    ```
+3.  **Install dependencies**:
+    ```bash
+    npm install
+    ```
+4.  **Run the development server**:
+    ```bash
+    npm run dev
+    ```
+    Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
+
+## 🛠️ Development Workflow
+
+1.  Create a new branch for your feature or fix:
+    ```bash
+    git checkout -b feature/amazing-feature
+    ```
+2.  Make your changes.
+3.  **Lint your code** to ensure it meets the project's standards:
+    ```bash
+    npm run lint
+    ```
+4.  Commit your changes with a descriptive message.
+
+## 🎨 Style Guidelines
+
+*   **Aesthetic:** Maintain the "Retro-Futuristic" / Cyberpunk 1985 vibe.
+*   **Tailwind CSS:** Use utility classes for styling.
+*   **Colors:** Stick to the defined palette (Cyan, Fuchsia, Yellow, Deep Space Black).
+*   **Typography:** Use `font-mono` for text elements.
+
+## 📬 Submitting a Pull Request
+
+1.  Push your branch to your fork:
+    ```bash
+    git push origin feature/amazing-feature
+    ```
+2.  Open a Pull Request on the original repository.
+3.  Provide a clear description of the changes and why they are necessary.
+4.  Wait for review!
+
+## 🤝 Code of Conduct
+
+Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms. Be kind and respectful to others.