Skip to content

Add landing page for GitHub Pages#26

Open
munezaclovis wants to merge 2 commits intomainfrom
feat/landing-site
Open

Add landing page for GitHub Pages#26
munezaclovis wants to merge 2 commits intomainfrom
feat/landing-site

Conversation

@munezaclovis
Copy link
Contributor

Summary

  • Adds a static single-page marketing site in docs/ for GitHub Pages deployment
  • Dark theme with blueprint-style SVG grid pattern (inspired by soloterm.com)
  • Animated terminal demo cycling through pv install, pv link, and pv php install commands
  • Feature cards, how-it-works steps, install command with copy-to-clipboard button

Files

File Purpose
docs/index.html Full single-page site — navbar, hero, problem/solution, features, how-it-works, install, footer
docs/style.css All styles with CSS custom properties — blueprint SVG pattern, responsive layout, terminal window
docs/script.js Terminal typewriter animation, copy-to-clipboard, scroll fade-in, smooth scroll

Design

  • No build tools, no npm, no frameworks — pure HTML/CSS/JS
  • Blueprint grid pattern is a pure SVG data URI in CSS (no static image files)
  • Responsive: single column on mobile (< 768px), two-column features grid on desktop
  • Fonts: Inter (body) + JetBrains Mono (terminal/code) from Google Fonts
  • Colors: dark navy hero (#0b0f1a), electric blue accent (#155dfc)

To deploy

Enable GitHub Pages in repo settings → source: Deploy from a branch → branch: main, folder: /docs

Static single-page marketing site showcasing pv's capabilities.
Dark theme with blueprint grid pattern, animated terminal demo,
feature cards, installation instructions, and copy-to-clipboard.

No build tools or dependencies — pure HTML, CSS, and JS.
Floating button in the bottom-right cycles through 10 palettes
(blue, emerald, violet, rose, amber, cyan, orange, pink, teal,
indigo). Refactors all hardcoded accent rgba values to CSS custom
properties so the JS switcher can update everything at once.
munezaclovis added a commit that referenced this pull request Mar 6, 2026
…izard (#26)

- Replace nested subcommands with colon-namespaced top-level commands:
  `pv php install` → `pv php:install`, `pv service add` → `pv service:add`, etc.
- Move `pv use php:X` → `pv php:use X` (direct version arg, no prefix)
- Add `pv setup` — interactive wizard using charmbracelet/huh for choosing
  PHP versions, tools (Composer, Mago, Colima), services, and TLD
- Add standalone install commands: `pv composer:install`, `pv mago:install`,
  `pv colima:install`
- Update `pv install` description to clarify it's the non-interactive path
- Update all user-facing strings, help text, doctor fixes, shims, and E2E
  scripts to use new command format
- Delete parent command files (cmd/php.go, cmd/service.go, cmd/use.go)
munezaclovis added a commit that referenced this pull request Mar 6, 2026
…27)

* Refactor CLI to colon-namespaced commands and add interactive setup wizard (#26)

- Replace nested subcommands with colon-namespaced top-level commands:
  `pv php install` → `pv php:install`, `pv service add` → `pv service:add`, etc.
- Move `pv use php:X` → `pv php:use X` (direct version arg, no prefix)
- Add `pv setup` — interactive wizard using charmbracelet/huh for choosing
  PHP versions, tools (Composer, Mago, Colima), services, and TLD
- Add standalone install commands: `pv composer:install`, `pv mago:install`,
  `pv colima:install`
- Update `pv install` description to clarify it's the non-interactive path
- Update all user-facing strings, help text, doctor fixes, shims, and E2E
  scripts to use new command format
- Delete parent command files (cmd/php.go, cmd/service.go, cmd/use.go)

* Move Colima binary to ~/.pv/internal/bin/ to avoid PATH pollution

Users may have their own Colima installed. Placing ours in
~/.pv/internal/bin/ (not on PATH) avoids shadowing it. All pv code
already calls Colima via config.ColimaPath() (full path).

* Add tests for InternalBinDir, ColimaPath, and ColimaSocketPath
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.

1 participant