LUXSER is a Minecraft Java client. This document specifies the marketing website for LUXSER: a professional, polished, responsive site that presents the client to Minecraft players with a premium, modern gaming aesthetic built on a purple-and-black theme.
The website's audience is Minecraft players who want to understand what LUXSER is, what it offers, and how to get it. Because the client is not yet released, the site communicates availability honestly: the Download and Use Now actions both display "Coming Soon", and no fake download links exist anywhere on the site.
The scope of this document is the website only. Building the Minecraft application itself is explicitly out of scope for now.
LUXSER's website is a public, no-account marketing site. It has four sections — Home, Features, About, and Download — reachable by any visitor without sign-in. The Home section is the public entry: it carries the hero title "LUXSER – Beyond Vanilla. Built for You.", the Use Now button showing "Coming Soon", and the Download button showing "Coming Soon". Features presents the client's features, About gives more information about LUXSER, and Download presents the Download button showing "Coming Soon" with no fake download link.
The site is delivered as a React frontend served alongside a shared FastAPI backend process and a MariaDB database provisioned in the initial scaffold. The backend and database are infrastructure only: the current website is static marketing content, so no application-owned user identity, accounts, or persistent domain data are required by any accepted workflow. The backend exists as the shared application process for any future server-side needs and does not add product behavior.
The only active human persona is the Minecraft player visiting the site. There are no other human participants, no provider-owned surfaces, and no external destinations in the accepted journeys.
Removed from scope
The website is a first-party, publicly accessible marketing surface owned by the application. Every visitor reaches all four sections anonymously; no sign-in, account, or identity establishment is required or offered, because no accepted workflow creates durable visitor-specific state, commitments, or entitlements.
The Download and Use Now buttons are present and visible but intentionally inert in the sense that they communicate "Coming Soon" rather than initiating a download or launching the client. This is a deliberate honesty boundary: the site must never present a link that appears to download LUXSER when no build exists. When a real build becomes available, that is a future change outside this document's current scope.
The Minecraft application itself — its gameplay, launcher, account integration, and distribution — is a future horizon. Nothing in this document specifies or implies application behavior.
Not applicable — no reference directive with content_source was supplied.
prefers-reduced-motion.href to any file and no download attribute pointing at a real or fake asset.FR-1 — Present the LUXSER client. As a Minecraft player, I should see a website that presents the LUXSER Minecraft Java client, so that I understand what LUXSER is. Provenance: explicit. Lifecycle: visitor lands on Home → reads hero title and subline → sees LUXSER named as a Minecraft Java client. Observable acceptance: the LUXSER name and its identity as a Minecraft Java client are visible on the site. Failure/recovery: not applicable (static content). Continuation: visitor navigates to Features, About, or Download.
FR-2 — Purple and black theme. As a Minecraft player, I should see the site rendered in a purple and black theme, so that it matches LUXSER's identity. Provenance: explicit. Observable acceptance: background is black-violet (#0B0610), primary colour is purple (#A855F7), and no blue or indigo accents appear on a white ground. Failure/recovery: not applicable. Continuation: theme applies across all four sections.
FR-3 — Premium, modern gaming aesthetic. As a Minecraft player, I should experience a premium, modern gaming aesthetic, so that LUXSER feels like a confident, high-quality client rather than a neutral tool. Provenance: explicit. Observable acceptance: bold colour fields, chunky Unbounded display type, sticker-like badges, overlapping panels, thick black outlines, and expressive motion are present; no gradient-blob hero and no grid of identical hover-lift cards. Failure/recovery: not applicable. Continuation: aesthetic is consistent across all sections.
FR-4 — Responsive for mobile, iPad, and PC. As a Minecraft player, I should be able to read and use the site on mobile, iPad, and PC, so that the site works on whatever device I use. Provenance: explicit. Observable acceptance: at 375px, 768px, and 1280px, headlines, wordmarks, labels, numbers, card text, and controls stay entirely inside the viewport and their container, wrapping or scaling (e.g. font-size: clamp(...)) to fit, and no other element covers any part of them. Failure/recovery: not applicable. Continuation: layout reflows per breakpoint.
FR-5 — Home, Features, About, and Download sections. As a Minecraft player, I should find Home, Features, About, and Download sections, so that I can explore the site by section. Provenance: explicit. Observable acceptance: all four sections are reachable from site navigation; each renders its own content. Failure/recovery: not applicable. Continuation: visitor moves between sections freely.
FR-6 — Smooth animations and glowing purple effects. As a Minecraft player, I should see smooth animations and glowing purple effects, so that the site feels alive and premium. Provenance: explicit. Observable acceptance: words slide in on load, purple blocks wipe across sections, buttons flip colour on hover, section titles slide in from the left as a colour block wipes behind them, and a slow purple glow ring pulses behind the hero crystal shape. Under prefers-reduced-motion, all motion stops and a usable static arrangement is provided. Failure/recovery: reduced-motion preference is honored as the recovery path. Continuation: motion is consistent across sections.
FR-7 — Hero title. As a Minecraft player, I should see the hero title "LUXSER – Beyond Vanilla. Built for You." on the Home section, so that I immediately grasp LUXSER's positioning. Provenance: explicit. Observable acceptance: the exact string "LUXSER – Beyond Vanilla. Built for You." renders as the hero headline, crossing the edge of the violet block, scaling from 44px on mobile to 128px on desktop, and staying fully inside the viewport at 375px, 768px, and 1280px. Failure/recovery: not applicable. Continuation: visitor reads the subline and sees the two buttons.
FR-8 — Download button shows "Coming Soon". As a Minecraft player, I should see a Download button that shows "Coming Soon", so that I know a download is not yet available. Provenance: explicit. Observable acceptance: the Download button is visible on Home and on Download, displays "Coming Soon", and does not initiate a download. Failure/recovery: not applicable. Continuation: visitor understands the client is unreleased.
FR-9 — Use Now button shows "Coming Soon". As a Minecraft player, I should see a Use Now button that shows "Coming Soon", so that I know the client cannot be launched yet. Provenance: explicit. Observable acceptance: the Use Now button is visible on Home, displays "Coming Soon", and does not launch or navigate to any client. Failure/recovery: not applicable. Continuation: visitor understands the client is unreleased.
FR-10 — No fake download links. As a Minecraft player, I should never encounter a fake download link, so that I am not misled into expecting a file that does not exist. Provenance: explicit (hard constraint). Observable acceptance: no anchor, button, or asset on any section points to a real or fabricated download file; no version number is presented as a downloadable artifact. Failure/recovery: not applicable. Continuation: the Download and Use Now buttons remain honest "Coming Soon" states.
FR-11 — Polished and professional. As a Minecraft player, I should find the website polished and professional, so that it reflects well on LUXSER. Provenance: explicit. Observable acceptance: consistent typography (Unbounded headings, Space Grotesk body), consistent spacing rhythm, sharp-cornered blocks with pill-round buttons, and no broken layouts at any breakpoint. Failure/recovery: not applicable. Continuation: quality is consistent across all sections.
FR-12 — Website only; no Minecraft application. As the product owner, I should have only the website built in this phase, so that the Minecraft application is not started prematurely. Provenance: explicit (hard constraint). Observable acceptance: the delivered system contains the marketing website only; no client, launcher, or gameplay code is produced. Failure/recovery: not applicable. Continuation: application build is a future horizon.
Product context. A Minecraft Java player who has heard of or is curious about LUXSER. They arrive at the website to judge whether LUXSER is worth their attention. They are evaluating a client they cannot yet download, so their decision is about interest and anticipation, not immediate acquisition.
Primary goal. Understand what LUXSER is, what it offers, and whether it is available — and leave with a clear, honest picture of its status.
Distinct accepted responsibilities.
Relevant inputs or decisions. Decides whether LUXSER interests them based on the features and about content; recognizes that both Download and Use Now are "Coming Soon" and therefore that no build is available yet.
Interactions with other accepted participants. None. The Minecraft player is the only active human persona; there are no other human participants, providers, or external destinations in the accepted journeys.
Observable success. The player can read the hero title, browse Features and About, and see both buttons in their "Coming Soon" state without encountering any fake download link, on mobile, iPad, or PC.
prefers-reduced-motion enabled.Muse and headline. Saturated play after Jessica Walsh, on a purple and black ground. Bold colour fields, chunky type, and playful motion — energy and confidence, not a neutral tool.
Mode. Dark mode only.
Colour tokens (exact hex by role).
#0B0610 (black-violet ground, covers most of the page)#1A0E24 (plum panels)#F4ECFF#A855F7 (violet — main colour block and glow)#D7FF3E (acid lime — the one hot accent for labels and focus rings)#9A86B8Typography.
Shape language. Hard colour blocks, sticker-like badges, overlapping panels, thick black outlines. Sharp corners on blocks; pill-round on buttons.
Layout. Asymmetric full-bleed sections. The hero stacks a giant headline over a purple block. Features use a staggered two-column poster grid, not equal cards.
Imagery style. Flat purple and plum vector blocks, a pixel-motif pattern, and one glowing crystal shape. No stock photography.
Motion. Expressive: words slide in on load, purple blocks wipe across sections, buttons flip colour on hover. All motion stops under prefers-reduced-motion.
Readability rule. Headlines, wordmarks, labels, numbers, card text, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (e.g. font-size: clamp(...) with its mobile size) to fit. No other element covers any part of them. Imagery, decoration, and motion may be cropped, bled off an edge, rotated, overlapped, or cut as the direction asks, as long as they cover no readable text or control.
Avoid. No gradient-blob hero; no grid of identical hover-lift cards; no blue or indigo accents on a white ground; no fake download links or version numbers; no Inter, Roboto, or Poppins; no centred headline with a small subtext and one plain button.
The public entry (Home) is a full-viewport black ground. A violet #A855F7 block fills the lower 40% and bleeds off both edges. The Unbounded headline "LUXSER – Beyond Vanilla. Built for You." sits across the block edge, scaling from 44px on mobile to 128px on desktop. Under the headline sit the lime Download button and the purple Use Now button, each carrying a lime "Coming Soon" tag that flips to the front on hover. A slow purple glow ring pulses behind the hero crystal shape.
The signature gesture is the headline crossing the block edge: the oversized type is not centred over a small subtext with one plain button; it straddles the boundary between black ground and violet field, carrying the Walsh energy while keeping every glyph fully inside the viewport at every breakpoint. The gesture is carried by the block and the type together — the block bleeds, the type stays whole.
Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d
Landing Hero Motion Brief
prefers-reduced-motion, and a usable static arrangement is provided. Rationale: accessibility and the direction's explicit motion rule.Source-specified technology choices are preserved; no substitutions are made.
No comments yet. Be the first!