landing-page-products

byKing Ff

http://electric-jack.mayatek.ng/ I want to build alike this landing page and also showcase other products maybe after purchase or a client clicking the link. Give me more ideas on how to go about it. Thanks

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Electric Jack

1. Introduction

Electric Jack is a product showcase site for a premium goods seller. A prospective client opens a link the product owner has shared, lands on a dark, curated catalogue page, and can browse the showcased products — each with its catalogue code and price — and complete a purchase. The product owner keeps the landing page and the product showcase current and shares the link with clients.

The site is built to look and feel like the referenced landing page at http://electric-jack.mayatek.ng/, used strictly as a visual and structural reference. The reference could not be fetched during analysis, so no content, copy, product names, or facts are taken from it; only the user's stated intent to build "alike this landing page" and to showcase other products after purchase or when a client clicks the link is carried forward.

The audience is buyers of premium goods who arrive from a shared link and want calm confidence rather than noise: one exact artefact, one spot colour, products as the only bright objects on a graphite ground.

2. System Overview

Page 1 of 18

2a. Product Interpretation and Delivery Boundary

Electric Jack is a first-party web application with three custom pages: Landing, Products, and Checkout. All three are publicly reachable without an account — the source establishes no login, no account creation, and no protected area. A prospective client opens the shared link, reads the landing page, moves into the catalogue, and can complete a purchase at Checkout. The product owner uses the same public surfaces to keep the showcase current and to share the link; no separate owner console, admin area, or authentication boundary is accepted by the source, so none is added.

The showcase is the product. The landing page is the anonymous first impression; the Products page is the catalogue the shared link opens into and the page a client returns to after a purchase; Checkout is where a showcased product is bought. Purchase completion is the observable outcome that closes the client's journey, and the catalogue remains open for continuation.

Delivery is a React frontend, a shared FastAPI backend, and a MariaDB database, run via docker-compose. The backend owns the product catalogue data and the checkout/purchase records. No payment-provider integration, no accounts, no email, and no analytics dashboard are accepted by the source; the checkout records the purchase intent and its outcome within the application.

2b. Source Content Inventory

Not applicable — the reference directive declares visual_inspiration and structure_reference only, with no content_source. The reference page could not be fetched, so no factual entities, products, prices, or copy are available to inventory.

2c. Page Content and Component Coverage

Page 2 of 18

Landing

  • Information and state: The public entry. Anonymous, no account. Presents the product name, the entry headline, the subline, and the primary call to action. A hero product plate (one monochrome product image on a plain graphite ground) sits left of centre at roughly 60 percent width. A stacked display line in Archivo runs at the top left; a thin orange rule and the catalogue code sit under it. A full-width orange rule divides the header from the hero plate. A slow timed crossfade cycles the hero plate through showcased products.
  • Primary action: "View the catalogue" — a flat orange rectangle at the lower left — navigates to Products.
  • Supporting actions: Header wordmark returns to Landing; a header link to Products.
  • Domain entities: Product (name, catalogue code, price, plate image) surfaced in the hero crossfade.
  • Component responsibilities: Header (wordmark, orange rule); Hero (display line, subline, CTA, hero plate with crossfade); Section openers with one centred diagram and sparse metadata blocks; footer with hairline rules.
  • States: Loading — hero plate placeholder on graphite with the display line already rendered. Empty — if no products exist, the hero shows the display line and CTA only, with no plate. Success — plate crossfades through available products. Error — if the product feed fails, the hero renders without a plate and the CTA still works. Recovery — a retry control reloads the hero feed.
Page 3 of 18

Products

  • Information and state: The catalogue. Anonymous, no account. Product rows read as ruled catalogue entries with aligned code, name, and price columns, separated by hairline rules. Each product carries a small catalogue code in acid-yellow caps. A colour-code strip supplies the graphic accent. This is the page the shared link opens into and the page a client returns to after a purchase.
  • Primary action: Select a product row to proceed to Checkout for that product.
  • Supporting actions: Return to Landing; re-open the catalogue after a purchase.
  • Domain entities: Product (catalogue code, name, price, plate image, short description).
  • Component responsibilities: Catalogue header with the acid-yellow code strip; ruled product rows (code / name / price columns); product plate on selection; section opener with centred diagram and metadata blocks.
  • States: Loading — hairline skeleton rows. Empty — a single ruled line stating the catalogue is being prepared, with no invented products. Success — ruled rows with aligned columns. Error — a ruled error line with a retry control. Recovery — retry reloads the catalogue.
Page 4 of 18

Checkout

  • Information and state: The purchase surface for one selected product. Anonymous, no account. Shows the selected product's catalogue code, name, and price, plus the fields needed to record the purchase (buyer name, contact, and delivery note). No payment-provider surface is accepted by the source; the checkout records the purchase and its outcome in the application.
  • Primary action: Confirm purchase — a flat orange rectangle.
  • Supporting actions: Return to Products; change the selected product.
  • Domain entities: Product (code, name, price); Purchase (selected product, buyer name, contact, delivery note, status, timestamp).
  • Component responsibilities: Order summary block (code / name / price in aligned columns); purchase form; confirmation block.
  • States: Loading — summary block placeholder. Empty — no product selected: a ruled line directing the client back to Products. Success — confirmation block with the purchase reference and the product code. Error — validation errors on required fields, or a submission failure line with a retry control. Recovery — retry resubmits; the client can return to Products and reselect.
Page 5 of 18

3. Functional Requirements

FR-1 — Landing page in the reference style. As a prospective client, I should open the shared link and see a landing page built in the style and structure of the referenced landing page, so that the first impression is calm, curated, and costly. (explicit)

  • Trigger: the client opens the shared link.
  • Observable result: the Landing page renders with the graphite ground, the display headline, the subline, the hero plate, the orange rule, and the "View the catalogue" CTA.
  • Access: anonymous, no account.
  • Failure/recovery: if the hero feed fails, the page still renders the headline and CTA; a retry control reloads the hero.
  • Continuation: the client selects "View the catalogue".

FR-2 — Showcase other products. As a prospective client, I should see the other products showcased on the site, so that I can review the full catalogue rather than a single item. (explicit)

  • Trigger: the client opens Products, or the hero crossfade cycles on Landing.
  • Observable result: ruled catalogue rows with aligned code, name, and price columns, each product carrying an acid-yellow catalogue code.
  • Access: anonymous, no account.
  • Failure/recovery: a ruled error line with a retry control; retry reloads the catalogue.
  • Continuation: the client selects a product row.
Page 6 of 18

FR-3 — Showcase after purchase or on link open. As a prospective client, I should see the product showcase after a purchase or when I open the shared link, so that the catalogue is the destination of the shared link and remains available after buying. (explicit)

  • Trigger: the client opens the shared link, or completes a purchase at Checkout.
  • Observable result: the Products page is reachable from the shared link and from the post-purchase confirmation.
  • Access: anonymous, no account.
  • Failure/recovery: if the catalogue fails to load, the confirmation still shows the purchase reference and a retry control.
  • Continuation: the client browses further products.

FR-4 — Product owner shares the landing page link. As the product owner, I should share the landing page link with the client, so that the client can open the showcase. (required_inference)

  • Trigger: the owner copies the public Landing URL.
  • Observable result: the client opens the link and lands on Landing.
  • Access: anonymous, no account.
  • Failure/recovery: if the link is mistyped, the client reaches Landing's not-found state with a link back to Landing.
  • Continuation: the client selects "View the catalogue".
Page 7 of 18

FR-5 — Product owner keeps the showcase current. As the product owner, I should keep the product showcase current, so that the catalogue the client opens reflects the products on offer. (required_inference)

  • Trigger: the owner updates the catalogue data held by the backend.
  • Observable result: Landing's hero crossfade and Products' ruled rows reflect the current catalogue.
  • Access: the owner uses the same public surfaces; no separate owner console is accepted by the source.
  • Failure/recovery: if an update is malformed, the catalogue retains its last valid state and the error is surfaced on the next load.
  • Continuation: the client sees the updated catalogue on the next open.

FR-6 — Complete a purchase. As a prospective client, I should complete a purchase of a showcased product at Checkout, so that I can buy what I have reviewed. (required_inference)

  • Trigger: the client selects a product row on Products and confirms at Checkout.
  • Observable result: a confirmation block with the purchase reference and the product code.
  • Access: anonymous, no account.
  • Failure/recovery: validation errors on required fields; a submission failure line with a retry control; the client can return to Products and reselect.
  • Continuation: the client returns to Products to browse further.

4. User Personas

Page 8 of 18

Prospective client

  • Product context: Arrives from a link the product owner shared, on a dark, curated catalogue page. Buys premium goods and expects calm confidence, not noise.
  • Primary goal: Review the showcased products — each with its catalogue code and price — and complete a purchase of the one they want.
  • Distinct accepted responsibilities: Opens the shared link; reads the landing page; moves into the catalogue; reviews ruled product rows; selects a product; completes a purchase at Checkout; returns to the catalogue after buying.
  • Relevant inputs or decisions: Which product to select; whether to confirm the purchase; the buyer name, contact, and delivery note at Checkout.
  • Interactions with other accepted participants: Receives the shared link from the product owner; sees the catalogue the owner keeps current.
  • Observable success: A confirmation block with the purchase reference and the product code, and the catalogue still open for further browsing.
Page 9 of 18

Product owner

  • Product context: Runs the premium goods showcase. Shares the link with clients and keeps the catalogue current. Uses the same public surfaces; no separate owner console is accepted by the source.
  • Primary goal: Put a curated, current catalogue in front of clients through a single shared link.
  • Distinct accepted responsibilities: Shares the Landing link; keeps the product showcase current so that Landing's hero crossfade and Products' ruled rows reflect the products on offer.
  • Relevant inputs or decisions: Which products to include; each product's catalogue code, name, and price; when to share the link.
  • Interactions with other accepted participants: Shares the link with the prospective client; the client's purchase is the observable interest in the catalogue.
  • Observable success: The client opens the link, sees the current catalogue, and completes a purchase.

5. Core User Flows

Page 10 of 18

Flow A — Prospective client opens the shared link and reviews the catalogue

  1. The product owner shares the Landing URL with the client.
  2. The client opens the link and lands on Landing (anonymous, no account).
  3. Landing renders the graphite ground, the display headline "Electric Jack. A catalogue you can open.", the subline "Open the shared link to see each product, its code and its price.", the hero plate, the orange rule, and the "View the catalogue" CTA.
  4. The hero plate slowly crossfades through showcased products.
  5. The client selects "View the catalogue" and arrives at Products.
  6. Products renders ruled catalogue rows with aligned code, name, and price columns, each product carrying an acid-yellow catalogue code.
  7. The client reviews the rows and selects a product.
  8. Failure/recovery: if the catalogue fails to load, a ruled error line with a retry control appears; retry reloads the catalogue.
  9. Continuation: the client proceeds to Checkout for the selected product, or returns to Landing.
Page 11 of 18

Flow B — Prospective client completes a purchase

  1. From Products, the client selects a product row and arrives at Checkout.
  2. Checkout shows the order summary block with the selected product's catalogue code, name, and price in aligned columns.
  3. The client enters the buyer name, contact, and delivery note.
  4. The client selects "Confirm purchase".
  5. Failure/recovery: if a required field is missing, a validation error appears on that field; if submission fails, a failure line with a retry control appears and the client can retry or return to Products to reselect.
  6. On success, Checkout shows a confirmation block with the purchase reference and the product code.
  7. Continuation: the client returns to Products to browse further products.

Flow C — Prospective client returns to the showcase after a purchase

  1. From the Checkout confirmation, the client selects the link back to Products.
  2. Products renders the current catalogue.
  3. The client reviews further products or returns to Landing.
  4. Failure/recovery: if the catalogue fails to load, the retry control reloads it.
Page 12 of 18

Flow D — Product owner keeps the showcase current and shares the link

  1. The product owner updates the catalogue data held by the backend (product code, name, price, plate image).
  2. Landing's hero crossfade and Products' ruled rows reflect the current catalogue on the next load.
  3. Failure/recovery: if an update is malformed, the catalogue retains its last valid state and the error is surfaced on the next load.
  4. The product owner copies the Landing URL and shares it with the client.
  5. Continuation: the client opens the link and Flow A begins.
Page 13 of 18

6. Visuals Colors and Theme

Muse: Peter Saville. Headline: "Electric Jack. A catalogue you can open."

The direction is austere: one exact artefact, one spot colour, products as the only bright objects on a graphite ground.

Palette (dark mode):

RoleHexUsage
Background#101014Graphite ground, ~70% of the surface
Surface#1A1A20Plates, summary blocks, form fields
Text#EDEAE3Bone text and hairline rules, ~20%
Primary#E8552BSignal orange — one action per screen
Accent#C8D94AAcid yellow — catalogue code strip only
Muted#8C8C96Metadata, secondary labels

Typography: Headings and body in Archivo. Headings at Medium weight, wide tracking in caps for labels; display lines use tight leading and large sizes. Modular scale 1.25: 44 / 34 / 26 / 18 / 15, with display clamp(44px, 9vw, 132px).

Shape language: Square corners and one-pixel rules. One centred diagram or product plate carries each section. Metadata sits in small blocks.

Layout: A strict 12-column grid with wide outer margins. The hero holds one large code plate. Product rows read as ruled catalogue entries with aligned code, name, and price columns.

Page 14 of 18

Imagery: One monochrome product plate per section on a plain graphite ground. A thin scientific diagram and a colour-code strip supply the graphic accent. No stock people.

Readable text and controls stay whole at 375px, 768px, and 1280px, wrapping or scaling to fit; imagery and decoration may be cropped or bled off an edge, but never over readable text or controls.

7. Signature Design Concept

The public entry is a dark graphite screen. A large bone product plate sits left of centre at 60 percent width. A stacked display line in Archivo runs at the top left: "Electric Jack. A catalogue you can open." A thin orange rule and the catalogue code sit under it. The orange CTA "View the catalogue" is a flat rectangle at the lower left. A full-width orange rule divides the header from the hero plate. The hero plate fades to the next product on a slow timed crossfade. Section openers show one centred diagram with sparse metadata blocks. Each product carries a small catalogue code in acid-yellow caps. Product rows use hairline rules and aligned code, name, and price columns.

Avoid: no gradients, blobs, or glass panels; no rounded cards or hover-lift tiles; no blue or indigo accent; no stock people; no centred headline with a button under it.

8. Interaction Model & Motion Direction

Interaction Model: Static Motion Tempo: still Hero Dimensionality: flat

Page 15 of 18

Landing Hero Motion Brief

  • Focal subject: the large bone product plate, left of centre at 60 percent width, on a plain graphite ground.
  • Input → transformation → outcome thesis: the page loads → the hero plate fades to the next showcased product on a slow timed crossfade → the client sees the catalogue's range before selecting "View the catalogue".
  • Motion vocabulary: precise 200ms fades; a slow crossfade between product plates; no bounce, no parallax.
  • Composed first frame: graphite ground; stacked Archivo display line at top left; thin orange rule and catalogue code beneath it; bone product plate left of centre; flat orange CTA at lower left; full-width orange rule dividing header from hero.
  • Reduced-motion state: the crossfade is disabled; the hero plate shows a single product statically, and the CTA remains fully usable.
Page 16 of 18

9. Non-Functional Requirements

  • NFR-1 — Reference fidelity. The Landing page must be built in the style and structure of the referenced landing page, using the creative direction's palette, typography, shape language, layout, and motion. (explicit)
  • NFR-2 — Readable text and controls. Headlines, wordmarks, labels, numbers, cards' text, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit; no other element covers any part of them. (explicit)
  • NFR-3 — Reduced motion. With prefers-reduced-motion, the hero crossfade is disabled and a usable static arrangement is provided. (explicit)
  • NFR-4 — Anonymous access. Landing, Products, and Checkout are publicly reachable without an account; no login, account creation, or protected area is accepted by the source. (explicit)
  • NFR-5 — Persistent catalogue and purchases. The backend persists the product catalogue and purchase records in MariaDB so that the showcase stays current and purchases are recorded. (required_inference)
  • NFR-6 — Failure recovery. Each page provides a retry control when its data feed fails, and the client can always return to Products or Landing. (required_inference)

10. Tech Stack

  • Frontend: React application UI.
  • Backend: shared FastAPI process for application APIs and domain modules (catalogue, purchases).
  • Database: MariaDB for application-owned persistent data (products, purchases).
  • Orchestration: docker-compose with the frontend, backend, and database services.
Page 17 of 18

11. Assumptions and Constraints

  • A-1: The referenced landing page could not be fetched during analysis; only the user's stated intent to build "alike this landing page" is carried forward, with no content, copy, or facts taken from it. (explicit)
  • A-2: The product owner keeps the showcase current through the same public surfaces; no separate owner console or authentication boundary is accepted by the source. (required_inference)
  • A-3: No payment-provider integration is accepted by the source; Checkout records the purchase and its outcome within the application. (required_inference)
  • A-4: No email, analytics dashboard, or account management is accepted by the source. (explicit)
  • A-5: The creative direction's palette, typography, shape language, layout, and motion are authoritative for the visual design. (explicit)

12. Glossary

  • Catalogue code: the small acid-yellow caps identifier carried by each product.
  • Hero plate: the large monochrome product image on the Landing page.
  • Product plate: the monochrome product image shown per section.
  • Ruled catalogue entry: a product row with hairline rules and aligned code, name, and price columns.
  • Shared link: the Landing URL the product owner shares with the client.
  • Signal orange: the primary colour #E8552B, marking one action per screen.
  • Acid yellow: the accent colour #C8D94A, marking only the catalogue code strip.
Page 18 of 18

No completed page designs yet.

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

Landing: Open public landing URL
Landing: 1. Verify hero crossfade
Landing: 2. Retry hero feed
Products: 1. Verify ruled catalogue rows
Products: 2. Retry catalogue load
Landing: Copy landing URL
Landing: Share link with client

No completed page designs yet.

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

Landing: Open public landing URL
Landing: 1. Verify hero crossfade
Landing: 2. Retry hero feed
Products: 1. Verify ruled catalogue rows
Products: 2. Retry catalogue load
Landing: Copy landing URL
Landing: Share link with client