epic(website): turn the Potato website from MVP into the proper public web presence

[slomin]

Summary

Turn the current Potato website from a quick MVP into the proper public-facing website for the project.

Right now the website is good enough to exist, but not yet good enough to carry Potato as a real public product and project surface. It should evolve from a minimal placeholder into a durable website that can explain Potato clearly, present releases and capabilities well, and support the growing split between:

• Potato OS / Core
• Inferno
• Apps
• future companion and ecosystem work

This should be treated as a big shaping epic, not a single design ticket.

Needs refinement

This epic is intentionally broad and should start in Needs Refinement state.

We know the direction, but the exact website structure still needs to be shaped, including:

• what lives on the main website vs GitHub docs vs product docs
• how Potato, Inferno, and Apps should be presented together without confusing the product boundary
• whether the first proper version should stay simple and mostly static, or grow into a richer site structure
• what release, install, docs, and download flows belong on the website itself
• what visual and design-system direction the public site should take

Goal

The goal is to make the website the proper public front door for Potato.

It should eventually help a visitor understand:

• what Potato is
• what runs where
• how to install or try it
• what Inferno is and how it relates
• what apps and ecosystem pieces exist
• where to find docs, releases, and project status

Scope

This epic should shape and later deliver a proper Potato website, including work such as:

• define the website information architecture
• define the public positioning and messaging for Potato
• improve the visual design so the site feels intentional and product-quality rather than MVP
• clarify navigation between:
  • Potato OS / Core
  • Inferno
  • Apps
  • docs
  • releases / install paths
• improve the install / get-started flow for new users
• improve release and changelog visibility where appropriate
• decide what content belongs on the website vs in repo docs
• create child tickets for design, content, implementation, navigation, release integration, and future ecosystem pages

Acceptance criteria

• the website direction is defined clearly enough to split this epic into concrete child tickets
• the intended information architecture is documented
• the public positioning for Potato is clearer than the current MVP site
• the epic is broken into concrete implementation tracks for design, content, and technical delivery
• this epic is marked as Needs Refinement until that shaping work is done

Non-goals

• shipping the full final website in this epic alone
• rebuilding every repo doc page into the website immediately
• solving all branding forever in one pass
• implementing Inferno or Apps product work in this ticket

Related

• Related to #264
• Related to #282
• Related to release and install documentation work already in potato-os/core