The official frontend for PyDay Chile – a community-driven Python conference showcasing Chile’s tech talent through talks, workshops, and networking events across multiple cities.

• Dynamic content routing for different conference locations
• Interactive map showing participating cities
• City-specific schedules and venue details

• Responsive image gallery with lazy loading
• Full-screen modal viewer with keyboard navigation
• Organized historical content by year and location
• Embedded video section with responsive players

• Next.js 13+ App Router implementation
• Optimized WebP image delivery
• Responsive UI built with Tailwind CSS
• Accessibility-first components (ARIA labels, keyboard navigation)

• Speaker profiles with social links
• Interactive schedule with filtering
• Sponsor showcase with tiered visibility
• Registration form with client-side validation

Core

Optimization

Interactive

pyday-frontend/
├── public/            # Optimized static assets
│   └── images/        # Organized media library
│       ├── gallery/   # Event photos by year/city
│       ├── speakers/  # Speaker headshots
│       └── sponsors/  # Partner logos
│
├── src/
│   ├── app/           # Next.js 13+ routing
│   ├── components/    # Reusable UI elements
│   ├── data/          # Content management
│   └── lib/           # Utilities & helpers
│
└── tailwind.config.js # Custom design system

• WCAG 2.1 AA-compliant components
• Semantic HTML structure
• Keyboard-navigable interfaces
• Reduced-motion preference support
• ARIA labels for interactive elements

• next@15.3.1: React framework for production
• tailwindcss@4.1: Utility-first CSS
• framer-motion@10.16.0: Smooth animations

Control feature visibility via environment variables:

# .env.local
NEXT_PUBLIC_FEATURE_REGISTRATION="false"   # Main registration form
NEXT_PUBLIC_FEATURE_SPONSORS="true"       # Full sponsors section
NEXT_PUBLIC_FEATURE_SPONSOR_FORM="false"  # Individual sponsor inquiry form

1. Set variables in .env.local using true/false.
2. Restart the server after any changes.
3. Alternate CTAs automatically display when:
   • A feature is disabled (false)
   • An external link is provided in cityData.js

// Example in src/data/cities.js
valparaiso: {
  talkProposalLink: "https://..." // Valid URL enables automatic CTA
}

Note: Alternate CTAs appear only when the related feature flag is false and a link is configured for that city.

Critical Server Configuration:
For production deployments, follow our Server Setup Guide covering:

• Node.js environment requirements
• PM2 process management
• GitHub Actions integration
• Mandatory environment variables
• Image optimization pipeline

Minimum Requirements:

• Node.js v20+
• 2GB RAM minimum
• HTTPS configuration

📌 Admin Note: The output: 'export' config is prohibited** - breaks dynamic routes and middleware. Always use standard Next.js build (npm run build+npm start`).

We welcome community contributions! Please see our Contribution Guidelines and review our Photography Style Guide for asset submissions.

License: Apache 2.0 (See LICENSE)
Maintainer: PyDay Chile Tech Committee
📧 pyday@pythonchile.cl