# Lidar drone scanning

> A pale technical product site featuring a rendered drone, an oversized translucent wordmark, precision measurements, and a capabilities section combining navigation, point-cloud imagery, and scanning specifications.

- Kind: Website
- Live website: https://drone.riotters.com/
- Page: https://meetreference.com/v/ref-lidar-drone-scanning-a278/
- Ready-to-use agent handoff: https://meetreference.com/v/ref-lidar-drone-scanning-a278/agent.txt
- Authorship: Not stated
- Made with: Not stated
- Model: not stated
- Built with: not stated
- Style: 3D sites; technical minimalism, 3d product, oversized typography, monochrome, point cloud, hairline grid
- Preview: a flip-through of inspected screenshots; open the live work to experience its motion and interactions.
- Shared by Riotters in Website: https://www.awwwards.com/sites/lidar-drone-scanning
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

## Recreating this website

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Place a detailed product render in a nearly white field, using oversized low-contrast lettering behind it to add depth without competing with the object. Connect the render to specifications through fine circular guides, hairline dividers, and compact bracketed captions. Follow with a monumental section heading and a three-column layout separating navigation, visualization, and explanation. For a new subject, replace the drone, scanning particles, and measurements with subject-specific imagery and data, while increasing contrast on secondary labels.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the captured walkthrough frames, not by the creator.

Minimal, polished landing page presenting an autonomous LiDAR inspection drone and its capabilities.

- Color: White and very pale gray backgrounds, dark navy text, and muted gray-blue product imagery.
- Type: Clean sans-serif text, with a very large, lightweight “Capabilities” heading and smaller understated labels.
- Framing: Wide, spacious layouts with the drone render centered in product panels; later sections pair imagery with concise feature copy and metrics.
- Structure: A slim top navigation sits above product hero panels, followed by a large capabilities section with a central drone image, feature labels, and specification blocks.

Storyboard, nine frames spread across the captured walkthrough: https://meetreference.com/media/ref-lidar-drone-scanning-a278/storyboard.webp

- Frame 1 at 0.7s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f1.webp
- Frame 2 at 2.1s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f2.webp
- Frame 3 at 3.5s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f3.webp
- Frame 4 at 4.8s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f4.webp
- Frame 5 at 6.2s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f5.webp
- Frame 6 at 7.6s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f6.webp
- Frame 7 at 9.0s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f7.webp
- Frame 8 at 10.4s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f8.webp
- Frame 9 at 11.8s: https://meetreference.com/media/ref-lidar-drone-scanning-a278/f9.webp

## Links

- Visit site: https://drone.riotters.com/
- Original post: https://www.awwwards.com/sites/lidar-drone-scanning
- Source and design credit: https://www.awwwards.com/sites/lidar-drone-scanning