karlm/portfolio
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
41 commits 1 branch 0 tags 1.2 MiB
Find a file
Vercel 204f3a1249 Add Vercel Web Analytics to Next.js 
Implemented Vercel Web Analytics for Next.js

Summary:
Successfully installed and configured Vercel Web Analytics in this Next.js App Router project.

Changes Made:

1. Installed @vercel/analytics package:
   - Added @vercel/analytics@^1.6.1 to package.json dependencies
   - Updated package-lock.json with new dependency tree

2. Modified app/layout.tsx:
   - Added import statement: import { Analytics } from '@vercel/analytics/next'
   - Added <Analytics /> component inside the <body> tag, after <SpeedInsights />
   - Maintained existing code structure and formatting

3. Verification:
   - Build completed successfully with no errors (npm run build)
   - No linting errors (no lint script configured in project)
   - No test failures (no test script configured in project)
   - All changes follow Next.js App Router best practices

Implementation Details:
- The Analytics component is placed at the end of the body tag, following the existing pattern used for SpeedInsights
- The component will automatically track page views and Web Vitals data
- Works seamlessly with the existing SpeedInsights integration
- No environment variables or additional configuration required

Files Modified:
- app/layout.tsx (added Analytics import and component)
- package.json (added @vercel/analytics dependency)
- package-lock.json (updated with new dependency tree)

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
2026-02-13 09:28:59 +00:00
app Add Vercel Web Analytics to Next.js 2026-02-13 09:28:59 +00:00
.gitignore Initial commit from Create Next App 2025-10-17 20:22:21 +02:00
next.config.ts Initial commit from Create Next App 2025-10-17 20:22:21 +02:00
package-lock.json Add Vercel Web Analytics to Next.js 2026-02-13 09:28:59 +00:00
package.json Add Vercel Web Analytics to Next.js 2026-02-13 09:28:59 +00:00
postcss.config.mjs Initial commit from Create Next App 2025-10-17 20:22:21 +02:00
README.md docs(README): enhance project overview and structure for clarity 2026-02-09 15:10:32 +01:00
tsconfig.json Initial commit from Create Next App 2025-10-17 20:22:21 +02:00

README.md

1. Home / Landing

Goal: instant context

  • Name + role “Software Developer focused on X”
  • 1-line value statement “I build reliable backend systems and clean UIs.”
  • Primary CTA: View Projects or GitHub

2. Projects (most important page)

This is where hiring decisions start.

For each project:

  • What it is (1 sentence)
  • Tech stack
  • Your role (solo / team / size)
  • Key challenges & decisions
  • What you’d improve next

Examples:

  • “Self-hosted document management system (Docker, Python, PostgreSQL)”
  • “Matrix server setup & federation experiments”
  • “WPF app solving UI threading issues”

👉 3–5 good projects beat 10 shallow ones.

3. About (technical, not fluffy)

Think “senior dev intro”, not life story.

Include:

  • What kind of problems you enjoy solving
  • How you approach learning & debugging
  • What environments you work best in

Keep it to ~2 short paragraphs.

4. Skills / Tech Stack

Grouped, not buzzword soup.

Example:

  • Languages: …
  • Frameworks: …
  • Infrastructure / DevOps: Docker, Linux, CI/CD
  • Databases: …
  • Concepts: REST, async, threading, security basics

Bonus points:

  • “Comfortable with” vs “Familiar with”

5. Experience

  • Jobs, freelance, serious hobby projects
  • Focus on impact, not duties

Example:

“Maintained and extended internal tooling used by X users”

6. Resume (PDF)

  • One click download
  • Matches the portfolio (no contradictions)

7. Contact

  • Email
  • GitHub
  • LinkedIn
  • (Optional) location / timezone