Specus
brand/bell-ross-structural-reference.md
Bell & Ross as the structural reference for Specus
Скачать .mdСкачать папку .zip

Bell & Ross as the structural reference for Specus

Status: primary reference for product-page structure and conceptual communication.

This reference is abstract. It does not prescribe Bell & Ross typography, colours, grids, animation, or visual styling. Specus keeps its own visual language.

What the reference means

Bell & Ross separates three jobs that are often mixed together:

  1. The product page identifies the object, gives the essential facts, and offers the next action.
  2. Short feature sections explain one visible or technical decision at a time.
  3. Brand and universe pages carry the larger story, history, and philosophy.

The product is therefore understandable without reading a manifesto. The concept remains present because every claim is attached to a feature, material, dimension, function, or use case.

Product-page sequence

Use this order unless the product requires a clear exception:

  1. Product identity. Model name, product type, primary image, and one concise distinguishing sentence.
  2. Technical specifications. Place verified facts near the top. Use a stable order: movement, functions, case, dial, crystal, water resistance, crown, strap, buckle.
  3. Primary action. Purchase, pre-order, enquiry, or registration follows the essential facts. A visitor should not need to pass through conceptual copy before acting.
  4. Feature sections. Each section explains one feature with one image and a short text. Prefer two or three strong sections to a long report.
  5. Service or related objects. Add only when it helps the purchase or use decision.

Do not repeat the same specification in the hero, a table, a second specification block, and feature copy. A fact appears once in the full specification; later sections may explain its consequence without restating the whole list.

Conceptual communication

Build every product claim in this order:

Claim → physical reason → visible or practical result.

Example:

  • Claim: the dial remains legible in low light.
  • Physical reason: a sandwich construction exposes a luminous layer beneath the upper plate.
  • Result: the hour markers remain readable after illumination.

Use a small, repeated vocabulary for each product. For SA-1 the current vocabulary is: hand-wound mechanical watch, sandwich dial, pins, external modules, service boundary. Avoid introducing a new metaphysical term where a component name is enough.

Claims must match the maturity of the object. Distinguish current sample features from future modules. Do not imply owner-serviceable modularity, certified performance, or compatibility until it has been tested and documented.

Brand and world pages

Put the broader Specus position on World of Specus, project indexes, essays, and dedicated universe pages. These pages may explain recurring forms, origin stories, cultural references, and connections between scales.

Keep the bridge back to products concrete: name the object, feature, dimension, or documented project in which an idea appears.

Writing rules

  • Lead with the object and verified facts.
  • Keep paragraphs short and specific.
  • Give one section one job.
  • Prefer component names and measurements to promotional adjectives.
  • Explain why a feature matters once.
  • Keep speculative future work clearly labelled as future work.
  • Put calls to action immediately after the information needed to make that action meaningful.
  • Keep translations structurally equivalent across supported languages.

Required post-layout audit

After every product-page layout change:

  1. Read the rendered page from top to bottom and list the job of every section.
  2. Remove any section whose job duplicates another section.
  3. Check that specifications appear before conceptual explanation.
  4. Check that the main action follows the essential product facts.
  5. Verify that each feature section contains one feature, one supporting image, and one concise explanation.
  6. Check every technical claim against the approved specification and the current development stage.
  7. Compare all language versions for the same order, facts, and action.
  8. Run the production build.
  9. Inspect the rendered desktop page and confirm reading order, image fit, and absence of raw markup.
  10. After deployment, verify the public URL and the submitted form path.

Reference pages

Observed pattern as of 23 September 2026: product identity and commerce first; technical specifications near the top; concise image-led feature explanations afterwards; the larger brand thesis lives on history and universe pages.