property-sale-delhi

byJunglee Web

i have business related to property sale in delhi and i want to create website for my business with best UI and 3d effect

LandingProperty DetailsPropertiesContact
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Delhi Property Sale

1. Introduction

Delhi Property Sale is the public website for a Delhi-based property sale business. The business sells homes in Delhi, and the site exists to present that business and the properties it sells to prospective buyers in a way that feels premium, architectural, and trustworthy — a "best UI" with real 3D effects, per the owner's explicit request.

The audience is twofold: property buyers who want to see what is for sale in Delhi and reach the business about a home they like, and the business owner, who needs the business and its listings to be shown well enough that buyers make contact.

The site is a public, no-account marketing and listing surface. It is not a transaction system, not a CRM, and not a portal with logins. Its job is to show the business, show the properties, and open a conversation.

Page 1 of 19

2. System Overview

Delhi Property Sale is delivered as a public React front end served alongside a shared FastAPI backend and a MariaDB database. The front end carries the full visual and 3D experience; the backend serves the property listing data and receives contact requests; the database holds the listing records and the contact requests the business receives.

The active human actors are the Property buyer and the Business owner. The buyer browses the Landing page, the Properties page, and individual Property Details pages, and can send a contact request from the Contact page. The owner is represented on the site through the business presentation and the listings themselves, and receives the contact requests buyers send.

Current delivery covers four public pages — Landing, Properties, Property Details, and Contact — all reachable without any account or sign-in. There is no authentication, no buyer account, no owner dashboard, and no online payment or booking in the current scope.

Removed from scope

  • Buyer accounts and sign-in (also: login, registration, user profiles)
  • Owner admin dashboard or listing management UI
  • Online payments, booking, or token/advance collection
  • Saved favourites, shortlists, or comparison tools
  • Search filters, map search, or saved searches
  • Mortgage/EMI calculators or legal-document workflows
Page 2 of 19

2a. Product Interpretation and Delivery Boundary

Everything the buyer needs is public and anonymous. A visitor lands on the root Landing page, moves into the Properties listing, opens a single Property Details page, and — when a home interests them — goes to the Contact page and sends a message to the business. No step requires an account, and no step stores durable buyer-specific state that must be resumed later. The contact request is the one durable artifact a buyer creates, and it is bound to the buyer's own name and contact details as entered, not to a login.

The business owner's side of the site is the published presentation itself: the business story on the Landing page and the listings on the Properties and Property Details pages. The owner's observable outcome is that buyers see the listings and make contact; the contact requests arrive at the business through the backend. The owner does not operate a separate first-party management surface in this scope.

The 3D and motion experience is a first-class delivery requirement, not decoration layered on afterwards: the hero's CSS 3D building form, the tilted listing plane, and the diagonal section cuts are part of how the business is presented. All of it degrades to a usable static arrangement under reduced-motion preferences.

2b. Source Content Inventory

Not applicable — no reference directive supplies a content_source for this project.

2c. Page Content and Component Coverage

Page 3 of 19

Landing

  • Information and state: the business identity (Delhi property sale), the hero headline "Homes in Delhi, Shaped for Living", the subline "See premium properties for sale in Delhi. Speak to our team about the home you want.", and the primary call to action "View Properties". A preview of the property offering and a route into Contact.
  • Primary action: "View Properties" — gold outline button beneath the hero headline, leading to the Properties page.
  • Supporting actions: navigate to Contact; navigate to Properties from any listing preview.
  • Domain entities: business presentation content; a preview set of property listings.
  • Component responsibilities:
    • Hero stage
      Full-bleed dark stage; pearl headline spanning 9 of 12 columns at left; gold outline CTA beneath it; one rotating CSS 3D curved building form at right that tilts with the pointer.
    • Curved section bands
      Full-bleed curved bands with long diagonal section boundaries separating the hero from the business introduction and the listing preview.
    • Business introduction
      Wide-margin single column describing the Delhi property sale business.
    • Listing preview
      A small set of property cards on the shared tilted plane with pearl hairline edges, each routing to its Property Details page.
    • Contact prompt
      A closing band pointing to the Contact page.
  • States:
    • Loading: hero renders immediately from static content; listing preview shows a restrained placeholder band while listings load.
Page 4 of 19
  • Empty: if no listings are available, the preview band is omitted and the hero and Contact prompt remain.
  • Success: hero, introduction, preview, and contact prompt all present.
  • Error: if listings fail to load, the preview band shows a quiet message and a link to the Properties page; the hero is unaffected.
  • Recovery: retry the listing preview load without leaving the page.
  • Reduced motion: static hero with the building form held in a fixed pose; no pointer tilt.
Page 5 of 19

Properties

  • Information and state: the set of properties the business sells in Delhi, each shown as a card with its identifying details and a route into its details.
  • Primary action: open a property listing.
  • Supporting actions: return to Landing; go to Contact.
  • Domain entities: property listing (title, location in Delhi, price, key attributes, primary image).
  • Component responsibilities:
    • Listing plane
      Tilted 3-column plane at 1280px, stacking to a single column at 375px; cards carry pearl hairline edges and chamfered corners — no square cards.
    • Listing card
      Property image, title, Delhi location, price, key attributes, and an open action routing to Property Details.
    • Page heading band
      Oversized single-line heading in Jost Light with wide tracking.
  • States:
    • Loading: cards render as chamfered placeholder panels on the tilted plane.
    • Empty: a message that no properties are currently listed, with a route to Contact.
    • Success: all listings rendered on the plane.
    • Error: an inline message with a retry action; the page heading and navigation remain usable.
    • Recovery: retry reloads the listing set in place.
Page 6 of 19

Property Details

  • Information and state: the full details of one property listing — title, Delhi location, price, description, key attributes, and imagery — plus the route to contact the business about this property.
  • Primary action: contact the business about this property, routing to Contact with the property identified.
  • Supporting actions: return to Properties; open another listing.
  • Domain entities: property listing (full record).
  • Component responsibilities:
    • Detail header
      Oversized property title and Delhi location in the heading treatment.
    • Imagery band
      Architectural imagery of the property on charcoal grounds with curved framing.
    • Detail column
      Price, description, and key attributes in a wide-margin single column.
    • Contact action
      The single gold action on the page, routing to Contact with the property identified.
  • States:
    • Loading: header and detail column show restrained placeholders.
    • Empty: not applicable — a details page always resolves to one listing or to the not-found state.
    • Success: full listing rendered.
    • Error: if the listing cannot be found or loaded, a clear message with a route back to Properties.
    • Recovery: return to Properties and reopen a listing.
Page 7 of 19

Contact

  • Information and state: a form for the buyer to send a contact request to the business, carrying the buyer's name, contact details, and message, and identifying the property when the buyer arrived from a Property Details page.
  • Primary action: send the contact request.
  • Supporting actions: return to Properties; return to Landing.
  • Domain entities: contact request (buyer name, contact details, message, referenced property, submission time).
  • Component responsibilities:
    • Contact form
      Fields for name, contact details, and message; the referenced property shown when present; a single gold submit action.
    • Validation feedback
      Inline messages for missing or malformed fields, kept whole and readable at every viewport.
    • Confirmation state
      A clear acknowledgement that the request was sent, with a route back to Properties.
  • States:
    • Loading: submit action shows a pending state and is not double-submitted.
    • Empty: form fields blank; referenced property shown only when the buyer arrived from a listing.
    • Success: confirmation replaces the form.
    • Error: validation errors inline per field; a submission failure shows a message and preserves the entered values.
    • Recovery: correct fields and resubmit, or retry after a submission failure without re-entering data.
Page 8 of 19

3. Functional Requirements

FR-1 — Present the Delhi property sale business (explicit) As a Property buyer, I should see the Delhi property sale business presented on the Landing page, so that I understand who the business is and what it sells.

  • Trigger: the visitor reaches the root Landing page.
  • Observable result: the hero headline "Homes in Delhi, Shaped for Living", the subline "See premium properties for sale in Delhi. Speak to our team about the home you want.", and the business introduction are visible.
  • Access: public, no account.
  • Failure/recovery: static content renders independently of listing data; a listing failure does not blank the hero.
  • Continuation: the "View Properties" action leads to the Properties page.

FR-2 — Show the properties the business sells (explicit) As a Property buyer, I should see the properties the business sells, so that I can compare what is available in Delhi.

  • Trigger: the visitor opens the Properties page or the Landing listing preview.
  • Observable result: property cards with title, Delhi location, price, key attributes, and imagery, rendered on the tilted listing plane.
  • Access: public, no account.
  • Failure/recovery: a load failure shows an inline message with retry; an empty set shows a no-listings message with a route to Contact.
  • Continuation: each card opens its Property Details page.
Page 9 of 19

FR-3 — Open a property listing (required_inference) As a Property buyer, I should open a single property listing, so that I can judge whether the home suits me before contacting the business.

  • Trigger: the buyer selects a property card on the Properties page or the Landing preview.
  • Observable result: the Property Details page shows that listing's title, Delhi location, price, description, key attributes, and imagery.
  • Access: public, no account.
  • Failure/recovery: an unresolvable listing shows a clear message with a route back to Properties.
  • Continuation: the contact action routes to Contact with the property identified.

FR-4 — Send a contact request (required_inference) As a Property buyer, I should send a contact request to the business about a property, so that the business can respond to me.

  • Trigger: the buyer submits the Contact form with name, contact details, and message.
  • Observable result: the request is recorded with the buyer's details, message, referenced property (when present), and submission time; the buyer sees a confirmation.
  • Access: public, no account; the request is bound to the details the buyer enters.
  • Failure/recovery: missing or malformed fields show inline validation and block submission; a submission failure preserves entered values and offers retry.
  • Continuation: the buyer returns to Properties or Landing from the confirmation.
Page 10 of 19

FR-5 — Receive buyer contact requests (required_inference) As a Business owner, I should receive the contact requests buyers send, so that I can follow up on the properties they asked about.

  • Trigger: a buyer successfully submits the Contact form.
  • Observable result: the contact request is stored with the buyer's name, contact details, message, referenced property, and submission time, available to the business.
  • Access: business-side receipt through the backend; no first-party owner management surface in this scope.
  • Failure/recovery: a failed submission is reported to the buyer and is not silently lost; the buyer can retry.
  • Continuation: the business follows up outside the site.

FR-6 — Best-quality UI with 3D effects (explicit) As a Property buyer, I should experience a best-quality interface with 3D effects, so that the business feels premium and trustworthy.

  • Trigger: any page load.
  • Observable result: the CSS 3D curved building form in the hero tilting with the pointer, the tilted listing plane, long diagonal curved section boundaries, and the specified palette and typography.
  • Access: public.
  • Failure/recovery: under prefers-reduced-motion, a static hero and a usable static arrangement replace motion; readable text and controls stay whole at 375px, 768px, and 1280px.
  • Continuation: the experience never blocks navigation or the contact action.

4. User Personas

Page 11 of 19

Property buyer

The buyer is someone looking at homes for sale in Delhi and deciding which ones are worth pursuing. Their context is comparison: they arrive on the Landing page, want to know quickly whether this business has homes that fit, and move into the Properties listing to see the range. Their primary goal is to find a property worth contacting the business about.

Their distinct responsibilities are browsing the listing set, opening individual listings to judge fit, and — when a home interests them — sending a contact request with their own details and a message about that property. Their key decision is which listing, if any, merits a message. They interact with the business only through the contact request; they never see the business's side of the site. Their observable success is a confirmation that their request was sent, referencing the property they asked about.

Business owner

The owner runs a property sale business in Delhi and needs the website to represent that business well enough that buyers trust it and reach out. Their context is presentation and response: the site is the shopfront, and the listings are the inventory on display.

Their distinct responsibilities are having the business and its properties presented on the site, and receiving and following up on the contact requests buyers send. Their key input is the set of properties the business sells and the business story shown on the Landing page. They interact with buyers only through the contact requests those buyers submit. Their observable success is that buyers see the listings and make contact — measured by contact requests arriving with the property and buyer details intact.

5. Core User Flows

Page 12 of 19

Flow A — Buyer discovers the business and browses listings

  1. The buyer reaches the root Landing page. The hero stage shows the pearl headline "Homes in Delhi, Shaped for Living", the subline, and the gold outline "View Properties" button; the CSS 3D curved building form sits at right and tilts as the pointer moves.
  2. The buyer reads the business introduction in the curved band below the hero.
  3. The buyer selects "View Properties" and arrives on the Properties page.
  4. The Properties page renders the listing plane — three tilted columns at 1280px, stacked at 375px — with each card showing title, Delhi location, price, key attributes, and imagery.
  5. If no listings are available, the buyer sees the no-listings message and a route to Contact instead.
  6. The buyer continues to Flow B with a listing in mind.

Flow B — Buyer opens a property and judges fit

  1. From the Properties page (or the Landing preview), the buyer selects a property card.
  2. The Property Details page loads that listing: oversized title, Delhi location, imagery band, price, description, and key attributes.
  3. The buyer reads the details and decides whether the home is worth pursuing.
  4. If the listing cannot be resolved, the buyer sees a clear message and returns to Properties to choose another.
  5. When the home interests them, the buyer selects the gold contact action, which routes to Contact with the property identified.
Page 13 of 19

Flow C — Buyer sends a contact request

  1. The buyer arrives on the Contact page, with the referenced property shown when they came from a listing.
  2. The buyer enters their name, contact details, and message.
  3. The buyer submits. If a field is missing or malformed, inline validation marks it and submission is blocked; the buyer corrects it and resubmits.
  4. On success, the confirmation state replaces the form and the buyer sees that the request was sent.
  5. If submission fails, the entered values are preserved and the buyer retries without re-entering data.
  6. The buyer returns to Properties or Landing from the confirmation.

Flow D — Business owner receives and follows up on a request

  1. A buyer completes Flow C successfully.
  2. The contact request is stored with the buyer's name, contact details, message, referenced property, and submission time.
  3. The business owner receives the request through the backend and sees which property the buyer asked about.
  4. The owner follows up with the buyer outside the site.
  5. If a buyer reports a failed submission, the owner knows no request was recorded and the buyer can retry from the preserved form.
Page 14 of 19

6. Visuals Colors and Theme

Muse and headline: Zaha Hadid — Fluid parametric grandeur for Delhi property. Sweeping curved forms and real 3D depth, architectural, calm, and costly.

Mode: dark.

Colour tokens (exact):

RoleHexUse
Background#111214Charcoal ground, ~70% of the page
Surface#1C1E21Panels, cards, form fields
Text#F4F1EABody text
Primary#D8D2C6Pearl — curves, large text, hairline card edges
Accent#C8A45CGold — one action only per page
Muted#8C8F94Secondary labels, metadata

Typography:

  • Headings: Jost, Light 300, wide tracking, sentence case, one oversized line per section.
  • Body: Josefin Sans.
  • Scale: 1.333 modular; display clamp(44px, 8vw, 128px); body steps 40 / 28 / 18 / 16.

Shape language: long sweeping curves, chamfered panel edges, diagonal section cuts. No square cards, no sharp 90-degree corners.

Page 15 of 19

Layout: full-bleed curved bands alternating with wide-margin single columns. Property listings on a tilted 3-column plane at 1280px, stacking at 375px.

Imagery: architectural renders of Delhi homes on charcoal grounds; soft pearl light sweeps across curved surfaces; no stock people.

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 to fit; no element covers any part of them. Imagery and decoration may bleed, crop, rotate, or overlap freely.

7. Signature Design Concept

The public entry is a full-bleed dark stage. At left, the pearl headline "Homes in Delhi, Shaped for Living" runs to 128px and spans 9 of 12 columns, with the subline beneath it and a single gold outline "View Properties" button under that. At right, one rotating CSS 3D curved building form — a parametric, sweeping mass in pearl and charcoal — tilts with the pointer, catching soft pearl light across its curved surfaces. The stage's lower edge is a long diagonal curve, not a rule, cutting into the business introduction band below.

The signature is the tension between the flat, oversized typographic plane on the left and the dimensional, pointer-responsive architectural form on the right — the same gesture that carries into the tilted listing plane on the Properties page, where cards sit on a shared tilted surface with pearl hairline edges and chamfered corners.

Page 16 of 19

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: dimensional_css

Landing Hero Motion Brief

  • Focal subject: the CSS 3D curved building form at right of the hero stage.
  • Thesis: pointer movement over the hero → the building form tilts on its CSS 3D axes and the pearl light sweep shifts across its curved surfaces → the buyer perceives real architectural depth while the headline and CTA stay fixed and fully readable.
  • Motion vocabulary: slow camera-like sweeps on scroll; a CSS 3D tilt following the pointer on the hero model; long diagonal curved section boundaries that reveal as bands scroll into view.
  • Composed first frame: charcoal ground, pearl headline spanning 9 columns at left, gold outline button beneath, building form at right in a three-quarter pose with a pearl highlight along its leading curve, diagonal cut at the stage's lower edge.
  • Reduced-motion state: the static hero — building form held in a fixed three-quarter pose, no pointer tilt, no scroll sweep; all content and the CTA fully usable.
Page 17 of 19

9. Non-Functional Requirements

  • Best UI (explicit): the interface must meet the creative direction's palette, typography, shape language, and layout at 375px, 768px, and 1280px, with readable text and controls never cropped or covered.
  • 3D effects (explicit): the hero must render a CSS 3D curved building form with pointer tilt; the listing plane must be a shared tilted surface. No WebGL is required.
  • Reduced motion (required_inference): prefers-reduced-motion must yield a usable static arrangement with all content reachable.
  • Public access (required_inference): all four pages are reachable without an account; no authentication is introduced.
  • Contact durability (required_inference): a successfully submitted contact request must be persisted with buyer details, message, referenced property, and submission time; a failed submission must be reported to the buyer and must not silently discard entered values.
  • Performance (required_inference): the hero must render from static content without waiting on listing data, so a listing failure never blanks the entry page.

10. Tech Stack

  • Frontend: React application UI, carrying the CSS 3D hero, tilted listing plane, and the creative direction's tokens.
  • Backend: shared FastAPI process for application APIs and domain modules — property listing reads and contact request submission.
  • Database: MariaDB for application-owned persistent data — property listings and contact requests.
  • Infrastructure: docker-compose with the frontend, backend, and database services; the backend is reused for all feature APIs rather than adding new services.
Page 18 of 19

11. Assumptions and Constraints

  • Assumption (required_inference): the business's property listings are supplied to the site as data the backend serves; the owner does not manage them through a first-party UI in this scope.
  • Assumption (required_inference): contact requests are received by the business through the backend; follow-up happens outside the site.
  • Constraint (explicit): the website must have a best UI.
  • Constraint (explicit): the website must have 3D effects.
  • Constraint (explicit): the palette, fonts, surfaces, tone, and layout of the creative direction are preserved; the generic indigo/blue-on-white SaaS template is forbidden.
  • Constraint (required_inference): no buyer accounts, no owner dashboard, no payments, no saved favourites, no search filters, no calculators — none are in the accepted scope.

12. Glossary

  • Property listing — one home for sale in Delhi, with title, location, price, description, key attributes, and imagery.
  • Listing plane — the shared tilted 3D surface on which property cards sit on the Properties page.
  • Contact request — a message a buyer sends to the business, carrying name, contact details, message, referenced property, and submission time.
  • Hero stage — the full-bleed dark entry band on the Landing page holding the headline, subline, CTA, and CSS 3D building form.
  • Reduced motion — the prefers-reduced-motion state in which motion is replaced by a usable static arrangement.
Page 19 of 19
Live
Landing design preview
Landing: Present business story
Properties: Show property listings
Property Details: Present full listing
Contact: Receive contact request
Contact: Follow up outside site
Live
Landing design preview
Landing: Present business story
Properties: Show property listings
Property Details: Present full listing
Contact: Receive contact request
Contact: Follow up outside site