Hetzner-ready site shell

Forum, gallery, and member areas from one clean front door.

This build is structured like a modern community hub: discussion tracks, curated media, verified profiles, and a staged launch path that can grow into a full member product later.

Explore Structure Review Launch Plan

Active host: this domain Served with automatic TLS on Hetzner

Phase 1

Landing Experience Fast static delivery across every domain

Phase 2

Community Engine Forums, profiles, moderation, and role-based access

Infrastructure

1 Hetzner node Static delivery with managed TLS and domain routing

Routing

4 mapped domains Same site served from every supplied hostname

Structure

Organized like a member community, not a one-page brochure.

The layout mirrors a category-based platform so the static launch already suggests where the full product can expand next.

Forum Tracks

Clear lanes for introductions, discussion threads, long-form posts, and event chatter.

Media Library

A place for featured galleries, editorial drops, interviews, and curated member submissions.

Member Profiles

Verification, profile cards, and access tiers are framed as a future layer rather than baked into the initial launch.

Safety Controls

Space for moderation rules, reporting flows, and gated content policies once the platform becomes interactive.

Forum

Conversation areas with enough shape to feel real on day one.

The front page can preview category depth now, then hand off to a forum engine later without forcing a full redesign.

Introductions and announcements
Topic-based rooms and editorial threads
Events, news, and member updates

Members

Profiles and trust systems are accounted for before they exist.

This is where verification, role-gated access, and moderation workflows can plug in once the static launch proves the traffic path and domain setup.

Display names and profile badges
Moderation queue and reporting hooks
Tiered access for premium areas

Launch Plan

Start with a fast static front end, then add the heavier system.

Step 1

Ship the landing experience

Serve the same branded site across every domain with fast static delivery, automatic TLS, and zero app runtime complexity.

Step 2

Confirm Hetzner ingress

Point DNS, open ports 80 and 443, and verify each hostname resolves to the same node before layering in application logic.

Step 3

Swap in the platform backend

Replace the static page with the chosen forum or membership stack once the infrastructure, routing, and moderation model are ready.