Skip to content

Comments

Website redesign proposal#30

Draft
tallpsmith wants to merge 18 commits intomainfrom
website-redesign
Draft

Website redesign proposal#30
tallpsmith wants to merge 18 commits intomainfrom
website-redesign

Conversation

@tallpsmith
Copy link

@tallpsmith tallpsmith commented Feb 2, 2026

Screenshot 2026-02-02 at 11 39 02 am Screenshot 2026-02-02 at 11 39 39 am

I got Claude, including it's Frontend-design skill, to rearchitect and redesign the PCP website to bring it to a more 'fresh' and 'modern' look, as well as completely change how the website is built using some modern tooling but still keeping it easy to edit.

Marking this a more a proposal at this stage. It looks like Claude decided to do all the work inside a new-site directory, leaving the existing one in place (not recognising we're in a branch for safety), but I guess that gives you an opportunity to see both sides easy enough..?

Makes installation easier for macOS users via brew tap/install commands.
Keeps DMG installer as alternative option. Adds Ruby version compatibility
docs to CLAUDE.md for future development.
Replaces deprecated Ruby/Compass stack - builds working homepage.
Outputs to docs/ for GitHub Pages. See new-site/README.md for setup.
Add CodeBlock component for terminal-style code display.
Migrate Features page with 4 sections (Collect, Analyze, Distributed, Extend).
Migrate Download page with platform-specific install commands.

- CodeBlock component with copy button
- Alternating section backgrounds for visual rhythm
- Platform cards with OS logos and install commands
- Source code repos with git clone commands
- GPG signature download link
- Configure Astro to output .html files (not directories) for URL compat
Track completion of Features and Download pages.
Built proper nav structure with CSS-only dropdowns and full mobile support.
- Header now matches footer's category structure (About/Resources/Community)
- NavDropdown component: hover/focus-within support, cyan glow on active
- MobileMenu: slide-in drawer with backdrop blur and escape key support
- Optimized SVG logo from 655-line Inkscape bloat down to 48 lines
- Download button styled as CTA with cyan accent

Navigation requires zero JavaScript on desktop, minimal JS for mobile toggle.
Break migration into 6 sub-phases:
1. Content collections for structured content (news, GSoC, GSoD, conference)
2. Core pages (docs, community, FAQ) - Priority 1
3. Supporting pages (team, testimonials, gallery) - Priority 2
4. Content collection pages with dynamic routing - Priority 3
5. Miscellaneous cleanup
6. New components (Accordion, TeamCard, Quote, Gallery)

Strategy: Incremental commits per page, use Astro content collections
for year-based content, maintain .html backward compatibility
Create Astro content collections for structured content:
- news/ - Release announcements with date/version metadata
- gsoc/ - Google Summer of Code project years (2015-2022)
- gsod/ - Season of Docs years (2019-2021)
- conference/ - Conference pages (2018-2019)

Each collection has type-safe Zod schema validation in config.ts.
Sample entries added to verify build succeeds.

Build tested: All content collections validate successfully.
Convert documentation.haml to cockpit-style layout:
- Hero with Installation + Quick Reference CTAs
- Two-column resource grid (main docs + short guides)
- Blog section with 7 Red Hat blog post links
- Videos section with 7 YouTube tutorials and thumbnails

Reuses Button and Card components. All external links open in new tabs.
Convert community.haml with clean content-focused layout:
- Hero heading
- Welcome section with contribution guidelines
- Mailing Lists section (general + announcements)
- Chat section (IRC + Slack)
- Funding section (Swag + OpenCollective)

Alternating backgrounds (panel/space) for visual rhythm.
All links styled with cyan hover.
Convert faq.haml with anchor-link Q&A pattern:
- 4-column question index (General, Philosophical, Technical, Troubleshooting)
- Answers section with smooth scroll-to-anchor navigation
- Sample Q&A entries demonstrate the pattern

NOTE: Full FAQ has 1000+ lines. Structural migration complete,
remaining ~20 Q&A entries to be bulk-migrated following this pattern.

Skipped Accordion component - anchor links work fine for FAQ use case
and keeps zero-JS philosophy.
Mark completed tasks:
- Content collections infrastructure (all 4 collections)
- Documentation page (with blog + videos sections)
- Community page (mailing lists, chat, funding)
- FAQ page (structural migration, anchor-link navigation)

Current status: 6 pages migrated, build passing.
Next: Phase 3.3 - Supporting pages.
Mark FAQ as PARTIAL migration with explicit call-out:
- Structure and 4 sample Q&As complete
- Remaining ~20 Q&A entries to be bulk-migrated in Phase 3.5

Added explicit task in Phase 3.5 for FAQ content completion.
Migrate supporting pages from HAML to Astro with Cockpit Control aesthetic.

**Team page** (team.haml → team.astro):
- Grid of 8 maintainers with GitHub profile links
- Instrument panel cards with hover effects
- HUD-style scanline overlays on interaction
- Link to contributor graph

**Testimonials** (testimonials.haml → testimonials.astro):
- New Testimonial.astro component for quote cards
- 9 enterprise testimonials (Netflix, Red Hat, Aconex, Buffalo, etc.)
- Company logo integration where available
- Quote styling with opening/closing marks

**Gallery** (glider.haml + screenshots.haml → gallery.astro):
- Consolidated two separate pages into unified gallery
- PCP Glider section with Windows installation details
- 13 screenshot grid with lightbox functionality
- Client-side image viewer with keyboard navigation (Esc, arrows)
- HUD corner markers on image hover

**Presentations** (presentations.haml → presentations.astro):
- Chronological archive from 2020 back to 1999
- Two-column year-based layout
- Multi-format links (PDF, ODP, Video, HTML slides)
- Icon differentiation for video vs documents
- Sticky year headers for context

All pages build successfully with zero-JS base (except Gallery lightbox).
Aviation instrument aesthetic maintained across all components.
Community, Documentation, and FAQ pages were missing Header and Footer
components, making them navigation dead-ends. Added imports and components
to all three pages so users can actually navigate back to the homepage.

Good catch on the nav issue.
Add critical documentation for the new-site/ Astro rebuild to prevent
Header/Footer omissions and clarify build commands, styling constraints,
and component locations for future development sessions.
Bring Google Season of Docs pages into the modern redesign to maintain
consistency across the site. 2019/2020 use dynamic routes with TypeScript
data, while 2021's narrative structure (proposal/case study) uses static
pages. Navigation updated to point to /gsoc.html index.
Bring Google Summer of Code pages (2015-2022) into the modern redesign
for consistency. Includes reusable Breadcrumb, YearNavigation, and
NewsItem components shared across GSoC/GSoD pages. Build artifacts
(collection schemas, data store) support Astro's content layer.
@tallpsmith tallpsmith marked this pull request as draft February 2, 2026 00:38
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