feat: create comprehensive content pages and update navigation (#116)

* feat: create comprehensive content pages and update navigation

Create complete content strategy with 6 new pages:
- Home page with hero section, live demo, features, trust signals
- Help/FAQ with quick start, troubleshooting, security best practices
- Security page with technical deep-dive into encryption architecture
- Examples page showcasing 8 real-world use cases with code samples
- About page highlighting human-AI collaboration and zero-knowledge promise
- Privacy and Terms pages with clear, friendly language

Update navigation structure:
- Header: focused on primary actions (Create, Examples, Help, GitHub)
- Footer: comprehensive sitemap with playful section headers
- ✨ Make Magic, 🤝 Behind the Sheets, ⚖️ Boring (but Important)

Technical improvements:
- Responsive design with mobile-first approach
- Consistent component patterns using shadcn/ui
- Proper SEO with metadata for all pages
- Accessibility with semantic HTML and ARIA labels
- ESLint compliant with proper quote escaping

Logo size increased from "xl" to "2xl" for better visual impact.
All content emphasizes zero-knowledge encryption and user privacy.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

* fix: replace dynamic dates with static dates to prevent hydration issues

Replace new Date().toLocaleDateString() with static date strings in Privacy and Terms pages
to avoid hydration mismatches between server and client rendering.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

* fix: implement dynamic year in footer without hydration issues

- Create DynamicYear client component that gets current year directly
- Keep Footer as server component for better performance
- Avoid hydration mismatch by using client component only for dynamic content
- No useState/useEffect needed - just get year on render

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

* fix: remove edge runtime from gists API to resolve OpenNext build error

OpenNext requires edge runtime functions to be in separate files.
Removing explicit edge runtime declaration allows the API to run
in Node.js runtime while maintaining compatibility with Cloudflare.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

---------

Co-authored-by: Claude <[email protected]>

Author: nullcoder

app/about/page.tsx

@@ -8,8 +8,6 @@ import { errorResponse, ApiErrors, validationError } from "@/lib/api-errors";
 import type { CreateGistResponse } from "@/types/api";
 import type { GistMetadata } from "@/types/models";
 
-export const runtime = "edge";
-
 // Validation schema for gist metadata
 const metadataSchema = z.object({
   expires_at: z.string().datetime().nullable().optional(),