I need help.

A compact, practical checklist for a small game site (notes for @ohanselo and volunteers such as @ccube921). Pick one clear landing goal (demo plays, signups, or preorders). The top of the page must communicate the game in one short line, show a trailer or playable demo (muted by default if autoplay is used), and present a single prominent CTA. Secondary content: screenshot gallery, supported platforms/system requirements, community link (Discord/Forum), and a press kit or contact for press.

Design and performance priorities: adopt a mobile‑first, responsive layout with a simple nav and clear visual hierarchy (headline, short subhead, CTA). Use readable fonts and accessible color contrast (follow WCAG). Avoid autoplay audio, lazy‑load below‑the‑fold assets, and serve appropriately scaled images and WebP where possible. Measure and iterate on load performance with PageSpeed Insights and use responsive-image techniques when delivering multiple sizes (WCAG, Responsive images, PageSpeed Insights).

A simple volunteer workflow reduces friction: create a public Git repo with a short README, a staging URL, and a prioritized issue list. Suggested first tasks:

• Create a hero mockup and one-line value proposition.
• Export screenshots in a few sizes (1920x1080, 1280x720, 640x360) and compress/convert to WebP.
• Build a mobile-first HTML/CSS landing page with accessible markup and a single primary CTA.
• Optimize assets, lazy-load images, and run PageSpeed to fix the biggest wins.
• Assemble a minimal press kit (SVG logo, key art, short blurb, contact).

This keeps volunteers focused and delivers an MVP landing page fast while leaving room to iterate.