agile-bronze

byFill

привет

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Привет

1. Introduction

Привет is a test website built to demonstrate the builder's capabilities and skills. The requester asked for a test site explicitly to check what the builder can do — its craft, its range, and its execution quality. The product is therefore a single public showcase page whose content, typography, colour, and motion are themselves the demonstration.

The audience is an anonymous Visitor who opens the site to see the builder's result, reads its content, and checks that the site works. There is no account, no data entry, and no transactional workflow: the site's value is the visible quality of the page itself.

This document is the System Requirements Document for the product. It specifies the one accepted page, the single accepted persona, the visual and motion direction, and the delivery boundary.

2. System Overview

Page 1 of 17

2a. Product Interpretation and Delivery Boundary

The product is a public, anonymous, single-page test site. A Visitor arrives with no identity, no prior state, and no credentials, and immediately sees the full showcase. Nothing on the site requires sign-in, registration, or stored personal data.

Delivery is first-party: the React frontend renders the Landing page, and the shared FastAPI backend serves the application API that supplies the page's content. MariaDB is provisioned as application-owned storage and holds the showcase content the backend serves. No provider-owned surface, external destination, or headless delivery model is involved.

The current horizon contains exactly one page — Landing — and one capability: showing the builder's capabilities and skills. There is no future-horizon functionality accepted for this product; anything beyond the Landing showcase is out of scope.

2b. Source Content Inventory

Not applicable — no reference directive declares content_source.

2c. Page Content and Component Coverage

Page 2 of 17

Landing

Information and state

  • Hero headline: "Привет. Смотрите, что я умею." rendered in Anton, uppercase, tight leading, at 128px desktop / 56px mobile, filling the left 8 columns on the paper ground #F2EDE4.
  • Hero subline: "Это тестовый сайт. Он показывает типографику, цвет и движение." in Archivo body type.
  • Hero call to action: "Смотреть", left-aligned beneath the headline.
  • A red #D8262C block filling the right 4 columns, holding at most one high-contrast black-and-white photo cutout.
  • A yellow #F5C400 label strip with black caps crossing the hero base.
  • Section content presenting the builder's capabilities and skills, each section headed in a left column with body text in a right column, separated by a black rule, with one flat colour block per section.
  • A slow marquee of Russian words crossing the section break.
  • Page state: loading (content being fetched from the backend), success (full showcase rendered), empty (no showcase content available), error (content fetch failed).

Primary actions

  • Read the hero headline, subline, and label strip.
  • Activate the "Смотреть" call to action to move to the showcase sections below the hero.

Supporting actions

  • Scroll through the showcase sections.
  • Read the marquee words as they pass.
Page 3 of 17

Domain entities

  • Showcase section: a titled block of the builder's demonstrated capability or skill, with heading and body text.
  • Hero content: headline, subline, call-to-action label, label-strip text, and the optional cutout image reference.

Component responsibilities

  • Hero block — renders the headline, subline, CTA, red block, cutout, and yellow label strip; keeps all readable text and the CTA fully inside the viewport and their containers at 375px, 768px, and 1280px, scaling with clamp(...) where needed.
  • Section list — renders each showcase section as a left heading column plus right body column with a black rule between, one flat colour block per section.
  • Word marquee — runs the slow Russian-word marquee across the section break; under prefers-reduced-motion it becomes a static arrangement (wrapped rows or a horizontally scrollable row) in which every item can be brought fully into view.
  • Content loader — fetches showcase content from the backend and drives loading, empty, success, and error states.
Page 4 of 17

States

  • Loading: hero renders immediately from static copy; showcase sections show a placeholder in the section area.
  • Empty: showcase area shows a short plain statement that no showcase content is available, in the same typographic system.
  • Success: all sections render with their headings, body text, and colour blocks.
  • Error: showcase area shows a plain error statement and a retry control that re-requests the content; the hero remains fully usable.
  • Recovery: retry re-fetches and replaces the error state with the success or empty state.
  • Reduced motion: marquee and entrance stagger are replaced by a static, fully readable layout.
Page 5 of 17

3. Functional Requirements

FR-1 — Show the builder's capabilities and skills

  • As a Visitor I should see a page that presents the builder's capabilities and skills so that I can judge the builder's result.
  • Provenance: explicit.
  • Lifecycle: The Visitor opens the Landing page anonymously; the page loads hero copy and showcase sections from the backend; the Visitor reads the sections; the observable result is a fully rendered showcase. If content fails to load, the Visitor sees an error statement with a retry control and can recover without losing the hero. Continuation: the Visitor scrolls through all sections.
  • Acceptance: The Landing page renders at least one showcase section with a heading and body text, and the hero headline, subline, and CTA are visible on first paint.

FR-2 — Read the hero entry content

  • As a Visitor I should see the headline "Привет. Смотрите, что я умею.", the subline "Это тестовый сайт. Он показывает типографику, цвет и движение.", and the call to action "Смотреть" so that I immediately understand what the site is.
  • Provenance: explicit (entry hero copy supplied by the creative direction).
  • Lifecycle: On page open the hero renders with the exact copy; the CTA sits left-aligned under the headline; activating "Смотреть" moves the Visitor to the showcase sections. Observable result: the hero is fully visible and the CTA is operable.
  • Acceptance: All three strings appear verbatim; the CTA is reachable and moves focus/scroll to the showcase area.
Page 6 of 17

FR-3 — Read showcase sections in the poster layout

  • As a Visitor I should read each showcase section as a left-column heading with right-column body text separated by a black rule, with one flat colour block per section so that the content is legible and visually structured.
  • Provenance: explicit (creative direction layout and signature moves).
  • Lifecycle: As the Visitor scrolls, each section enters with a short stagger and its colour block wipes in on scroll; the observable result is each section fully readable. Under reduced motion the sections appear statically without stagger or wipe.
  • Acceptance: Every section heading and body text stays entirely inside the viewport and its container at 375px, 768px, and 1280px; no element covers any part of them.

FR-4 — See the word marquee

  • As a Visitor I should see a slow marquee of Russian words crossing the section break so that the site demonstrates motion as part of its craft.
  • Provenance: explicit (creative direction signature move and motion).
  • Lifecycle: The marquee runs continuously at a slow tempo; each word becomes fully readable as it passes. With prefers-reduced-motion, the marquee becomes a static arrangement (wrapped rows or a horizontally scrollable row) where every item can be brought fully into view.
  • Acceptance: The marquee moves; no readable text or control is permanently covered; the reduced-motion arrangement exposes every word.
Page 7 of 17

FR-5 — Recover from a content load failure

  • As a Visitor I should see a plain error statement and a retry control when showcase content fails to load so that I can still judge the site and recover.
  • Provenance: required_inference (indispensable failure/recovery for FR-1's content fetch).
  • Lifecycle: The content request fails; the showcase area shows the error statement and retry control while the hero remains intact; the Visitor activates retry; the request repeats; the area shows the success or empty state. Observable result: the page is usable again.
  • Acceptance: The error state never removes the hero; retry issues a new request and updates the showcase area.

4. User Personas

Page 8 of 17

Visitor

  • Product context: An anonymous person who opens the test site with no account, no invitation, and no prior state. They arrive to see what the builder produced.
  • Primary goal: Judge the builder's capabilities and skills by reading the page and confirming that it works.
  • Distinct accepted responsibilities: Opening the Landing page, reading the hero copy, activating "Смотреть", scrolling the showcase sections, reading the marquee, and — if content fails — using the retry control.
  • Relevant inputs or decisions: Whether the page renders correctly and whether the content convincingly demonstrates craft; whether to continue scrolling or retry after an error.
  • Interactions with other accepted participants: None — the Visitor is the only accepted human participant; the backend and database serve content without a human counterpart.
  • Observable success: The hero, showcase sections, and marquee are fully readable at their viewport, the CTA works, and no readable text or control is cropped or covered.

5. Core User Flows

Page 9 of 17

Flow 1 — Visitor opens the test site and reads the showcase

  1. The Visitor navigates to the site's public URL with no identity.
  2. The Landing page renders the hero: "Привет. Смотрите, что я умею." in Anton filling the left 8 columns on the paper ground, the subline beneath it, and the "Смотреть" CTA left-aligned under the headline.
  3. The red #D8262C block fills the right 4 columns with the black-and-white cutout, and the yellow #F5C400 label strip crosses the hero base.
  4. The content loader requests showcase content from the backend; the showcase area shows a loading placeholder.
  5. On success, the showcase sections render: each with a left-column heading, right-column body text, a black rule between, and one flat colour block; sections enter with a short stagger and their colour blocks wipe in on scroll.
  6. The Visitor activates "Смотреть" and is moved to the showcase area, then scrolls through the sections.
  7. The slow marquee of Russian words crosses the section break; each word becomes fully readable as it passes.
  8. Result: The Visitor has read the full showcase and can judge the builder's capabilities and skills. Next step: the Visitor leaves the site or re-reads sections.
Page 10 of 17

Flow 2 — Visitor encounters a content load failure and recovers

  1. The Visitor opens the Landing page; the hero renders from static copy.
  2. The content loader's request fails; the showcase area shows a plain error statement and a retry control, while the hero remains fully usable.
  3. The Visitor activates retry.
  4. The content loader issues a new request; the showcase area shows the loading placeholder.
  5. On success the sections render as in Flow 1, step 5; if the backend returns no content, the area shows the empty statement instead.
  6. Result: The page is usable again and the Visitor can continue reading. Next step: continue with Flow 1 from step 6.

Flow 3 — Visitor with reduced motion reads the site

  1. The Visitor opens the Landing page with prefers-reduced-motion set.
  2. The hero renders statically with all readable text and the CTA whole and inside the viewport.
  3. Sections appear without stagger or colour-block wipes.
  4. The marquee is replaced by a static arrangement — wrapped rows or a horizontally scrollable row — in which every word can be brought fully into view.
  5. Result: The Visitor reads the entire showcase without motion. Next step: the Visitor leaves the site.
Page 11 of 17

6. Visuals Colors and Theme

Muse and headline: Typography as architecture after Paula Scher — "Words are the structure."

Mode: Light only.

Colour tokens (exact hex by role)

  • Background / paper ground: #F2EDE4
  • Surface (black block): #111111
  • Text: #111111
  • Primary (large red block): #D8262C
  • Accent (small labels only): #F5C400
  • Muted: #6E6A63

Typography

  • Headings: Anton, uppercase, leading 0.9, very large scale, stacked in hard columns.
  • Body: Archivo.
  • Modular scale 1.5: 120 / 80 / 48 / 28 / 18 / 16 px.
  • Headline size: 56px mobile, 128px desktop, implemented with clamp(...) so it stays whole at 375px, 768px, and 1280px.

Shape language: Hard edges only — no border radius anywhere. Flat colour blocks and diagonal bands. Black rules divide sections.

Layout: Full-bleed type columns on a 12-column grid; asymmetric poster blocks; one colour block per section; wide margins at 1280px, tight margins at 375px.

Page 12 of 17

Spacing rhythm: Section separation by black rules and generous vertical space; hero occupies the first viewport with the CTA left-aligned beneath the headline.

Imagery style: Type is the image. At most one high-contrast black-and-white photo cutout in the red hero block. No stock photos, no gradient blobs.

Forbidden: Rounded cards and soft shadows; gradient blobs and glass panels; centred headline with a blue button; small quiet body type with no display contrast; the generic indigo/blue-on-white SaaS template.

7. Signature Design Concept

The public entry is a full-viewport typographic poster. The word Привет fills the left 8 columns in Anton at 128px on desktop and 56px on mobile, sitting directly on the paper ground #F2EDE4. A solid red #D8262C block fills the right 4 columns and holds a single black-and-white cutout. A yellow #F5C400 label strip with black caps runs across the hero base. The headline "Привет. Смотрите, что я умею." stacks over the red block, the subline sits beneath it, and the "Смотреть" CTA is left-aligned under the headline.

The gesture is architectural: the type is the structure, the colour blocks are the walls, and the black rules are the joints. Every readable element stays whole and inside its container at 375px, 768px, and 1280px; where the direction asks for a bleed or crop, the gesture is carried by the red block, the cutout, and the label strip — never by the text or the CTA.

Page 13 of 17

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: flat

Landing Hero Motion Brief

  • Focal subject: the word Привет in Anton, stacked over the red #D8262C block, with the yellow label strip crossing the base.
  • Thesis: the Visitor opens the page → the headline words enter in a short stagger while the red block and label strip settle into place → the Visitor reads the full hero and the "Смотреть" CTA is ready.
  • Motion vocabulary: short stagger on words; slow type marquee across the section break; colour-block wipes on scroll; hard cuts, no easing bounce, no soft shadows.
  • Composed first frame: paper ground, headline occupying the left 8 columns, red block on the right 4 columns with the cutout, yellow label strip across the base, CTA left-aligned beneath the headline.
  • Reduced-motion state: all entrance stagger and colour-block wipes removed; the marquee becomes wrapped rows or a horizontally scrollable row where every word can be brought fully into view; the hero and sections render statically and completely readable.
Page 14 of 17

9. Non-Functional Requirements

  • Readability at every viewport (explicit): headlines, wordmarks, labels, numbers, and controls stay entirely inside the viewport and their containers at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit; no other element covers any part of them. Imagery and decoration may be cropped, bled, rotated, or overlapped as the direction asks, provided they cover no readable text or control.
  • Moving content (explicit): marquees may cross the viewport or container edge by design; each item must become fully readable as it passes. With prefers-reduced-motion, a usable static arrangement (wrapped rows or horizontal scrolling) must expose every item.
  • Performance (required_inference): the Landing page's hero must paint without waiting on the backend content request, so the page is judgeable even when the API is slow or failing.
  • Accessibility (required_inference): the CTA and retry control are keyboard reachable and operable; colour contrast between #111111 text and #F2EDE4 ground, and between black caps and the #F5C400 label strip, remains legible.
  • No identity or personal data (explicit by access contract): the Landing page has access requirement none; no authentication, account, or personal data collection is part of the product.
Page 15 of 17

10. Tech Stack

  • Frontend: React application UI rendering the Landing page.
  • Backend: shared FastAPI process serving the application API and domain modules, including the showcase content endpoint.
  • Database: MariaDB for application-owned persistent storage of showcase content.
  • Infrastructure: docker-compose.yml with the backend, database, and frontend services; the frontend depends on the backend, and the backend depends on the database.

11. Assumptions and Constraints

  • A-1 (required_inference): The showcase content is served by the shared FastAPI backend from MariaDB, so the page can demonstrate a working full-stack delivery rather than a static file.
  • A-2 (required_inference): The hero copy is static in the frontend so the page remains judgeable when the content API is unavailable.
  • A-3 (explicit): The site is public and anonymous; there is no sign-in, registration, or account management.
  • A-4 (explicit): The product has exactly one page, Landing, and one persona, Visitor.
  • A-5 (explicit): The creative direction is authoritative for palette, typography, shape, layout, motion, and imagery; the forbidden list in section 6 is binding.
  • A-6 (explicit): No future-horizon functionality is accepted; anything beyond the Landing showcase is out of scope.
Page 16 of 17

12. Glossary

  • Landing — the single public page of the product; the anonymous entry surface showing the builder's capabilities and skills.
  • Visitor — the anonymous human who opens the Landing page to judge the builder's result.
  • Showcase section — a titled block on the Landing page presenting one demonstrated capability or skill, with a left heading column and right body column.
  • Hero — the first-viewport poster block containing the headline, subline, CTA, red block, cutout, and yellow label strip.
  • Marquee — the slow-moving row of Russian words crossing the section break.
  • Reduced motion — the prefers-reduced-motion state in which stagger, wipes, and marquee motion are replaced by a static, fully readable arrangement.
  • Paper ground — the #F2EDE4 background on which black type sits.
Page 17 of 17

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Landing: Open public site anonymously

Landing: Read hero headline and subline

Landing: Activate Смотреть call to action

Landing: Scroll showcase sections

Landing: Read marquee words

Landing: See content load error

Landing: Activate retry control

Landing: See empty content statement

Landing: Read static reduced-motion layout

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Landing: Open public site anonymously

Landing: Read hero headline and subline

Landing: Activate Смотреть call to action

Landing: Scroll showcase sections

Landing: Read marquee words

Landing: See content load error

Landing: Activate retry control

Landing: See empty content statement

Landing: Read static reduced-motion layout