Skip to content

Add freelance route with Tailwind rebrand and transparent Toggl reporting - #14

Open
volcodes wants to merge 1 commit into
mainfrom
claude/portfolio-rebranding-9yff78
Open

Add freelance route with Tailwind rebrand and transparent Toggl reporting#14
volcodes wants to merge 1 commit into
mainfrom
claude/portfolio-rebranding-9yff78

Conversation

@volcodes

Copy link
Copy Markdown
Owner

Overview

Adds a new, trend-forward /freelance route that positions you for freelance & contract work, with a centerpiece section demonstrating how you report time transparently with Toggl. Built with Tailwind CSS, introduced as the styling foundation for new pages.

A core constraint of this PR: existing pages are not broken or restyled — only new routes are added, plus a few small additive links for discoverability.

What's new

New route: /freelance

  • Hero — "available for freelance" status, gradient headline, trust stats, dual CTAs
  • Services — bento-style grid (frontend architecture, AI integration, full-stack, performance/observability, IaC, technical leadership)
  • Engagement models — Hourly / Project-based / Retainer
  • Transparent time reporting with Toggl — explains your tracking & reporting cadence, with a live, illustrative weekly-report mockup (daily bar chart + project breakdown)
  • Process — Discovery → Proposal → Build with reports → Delivery
  • CTA — start a conversation / email / socials

Additive, non-breaking touches

  • Homepage freelance teaser section (self-contained component)
  • Freelance link in the header nav and footer
  • /freelance registered for prerendering and the sitemap

Tailwind setup (safe coexistence with existing SCSS)

  • Tailwind preflight is disabled so it never resets the existing bespoke SCSS pages
  • All utilities are scoped under .tw (via important: '.tw'), so Tailwind reliably wins inside the new pages and the old SCSS pages are completely unaffected (this resolves a .grid class-name collision between Tailwind and the existing global SCSS)
  • Theme mirrors assets/styles/colors.scss (navy background, green brand accent) so new and old stay visually consistent

Verification

  • npm run build succeeds; /freelance prerenders
  • Rendered and screenshot-checked on desktop (1440px) and mobile (390px)
  • eslint clean on all new/modified files; existing test suite passes

Note (pre-existing, unrelated)

pages/projects.vue references four screenshots that are not committed (edtech-admin-screenshot.jpg, edtech-infra-screenshot.jpg, student-reading-screenshot.jpg, voice-clone-screenshot.jpg) — likely missed in a recent project update. These break a full production build independently of this PR. I verified my work with temporary local placeholders (not committed). Adding the real screenshots will make the production build green.

🤖 Generated with Claude Code


Generated by Claude Code

…ting

Introduce a new /freelance route showcasing freelance/contract services
with a modern, trend-forward design built in Tailwind CSS.

- New /freelance page (hero, services bento grid, engagement models,
  Toggl-based time-reporting section with a live report mockup, process
  timeline, and contact CTA)
- Set up Tailwind CSS scoped to new routes only: preflight disabled and
  utilities scoped under `.tw` so the existing bespoke SCSS pages are
  untouched and never restyled
- Add an additive freelance teaser section on the homepage and Freelance
  links in the header and footer
- Register /freelance for prerendering and the sitemap

Existing pages and styling are left fully intact.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KQoxb1kAhj9b2wmztSALAm
@vercel

vercel Bot commented Jun 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
volcodeorg-app Error Error Jun 27, 2026 11:28pm

Sign up for free to 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.

2 participants