Implementing a dock configurator: water, modular geometry, interaction and labelling
Technical decisions for a dock or jetty configurator: water scene, geometry from tables, interaction, units, phones, value labelling and upkeep.
Short answer: a configurator for docks, pontoons and jetties is best built from dimension tables and rules. Sections, elements and booms are generated from parameters; fixed parts such as ladders or bollards are added as ready-made models. The real decisions are about the scene (how much water and shore?), interaction (drag, tap, snap), units and languages, phones, and how example values and released maker values are labelled.
How much water and shore does the scene need?
A dock without water and shore is hard to read: you see neither where it starts nor how high it sits. The scene needs three things: a water surface as the reference level, a shore with a connection point for the gangway or ramp and, depending on the product, a hint of the bottom so that depth becomes visible. It needs nothing more. Reflections, waves and particle effects cost processing time on a phone and pull attention away from the product. Our recommendation: water as a calm, slightly transparent surface, the shore as a simple bank, and boats only for scale, with a switch to hide them.
In the floating jetty configurator, boats, anchoring and dimensions can be shown or hidden [1]. That suits layouts: with boats you understand the berths, without them you see the piers.
Where does the geometry come from?
Docks are modular, which makes them a good fit for parametric geometry. A section, an element or a boom is described once as a part with dimensions; the configurator assembles length, width and position from the inputs. Every valid shape gets a model without each one having to exist as a file.
| Kind of part | Typical examples | Recommended approach |
|---|---|---|
| Grows with the size | walkway, head, decking, rails, booms, breakwater | generated from parameters in the browser |
| Fixed, repeated | floats, bollards, ladder, bench, fittings | modelled once, loaded as glTF and repeated |
| With its own movement | gangway, access ramp | parametric, with a pivot at the shore |
For fixed parts, glTF suits well: an open format from the Khronos Group for transmitting and loading 3D models [2]. If your parts exist as CAD, we check before the start whether they are suitable for the web; the route from STEP or native formats is covered in from CAD to a web 3D configurator. With docks, photos, drawings and dimension tables can be enough where the parts are geometrically simple.
Our four examples are example configurators with fictional products, built with our own geometry [1]. For your project, the geometry comes from your dimensions and documents. A side effect of building parametrically: model, checks and parts list read the same tables and so are less likely to drift apart.
How is a dock configurator operated?
The four examples show four interaction patterns that suit different products:
| Pattern | Example | Suits |
|---|---|---|
| Slide piers along the shore with a drag handle | floating jetty configurator | layouts with several piers and spacing |
| Add elements by tapping glowing slots on the water | floating dock planner | modular elements, use on a phone |
| Sections snap on in an animation | aluminium dock configurator | fixed-length sections, explaining the build |
| Ramp tilt checked per water level | floating dock kit configurator | kits with an access ramp |
The patterns come from the "Live in this demo" lists of the library pages [1]. One recommendation applies to all of them: direct interaction on the model should add to the input fields, not replace them. Anyone who prefers typing numbers, or cannot use the model, must reach the same configuration through fields and buttons.
Views are part of interaction too. For docks the plan view is often the most useful, because shape, spacing and berths are clearest from above; the side view shows deck height and ramp. The floating dock planner offers 3/4, plan and side views, and the aluminium dock configurator views with dimension labels [1].
Units, languages and vocabulary
Some dock makers sell across borders. Two rules keep that maintainable: store dimensions once in one unit and convert only for display, and keep every text, including notes and parts-list names, in translatable tables. Vocabulary needs the same care: "dock" means a structure for boats in American English but usually the water next to a quay in British English [3], so pontoon, jetty and dock are chosen per market. The aluminium dock configurator switches between ft-in and metric [1].
How are example values and maker values labelled?
Docks are structures in the water. Draft, freeboard, capacity, anchoring and permits have consequences if they are misread. For the build this means:
- Every value has a status. The data records whether a value is a released maker value, an assumption or an example rule, and the interface shows that status.
- Checks are worded carefully. "Fits the example rule" or "check on site", never "safe" or "suitable".
- The note travels with the value. What is labelled as an example value on screen is labelled the same way in the enquiry text and the PDF.
- Ratings only with release. Capacity or freeboard appears only if you stand behind it for that exact build.
Our examples are labelled this way on their library pages: site checks, draft, quantities and checks are simplified or fictional sample values, not a structural design and not a quote [1]. Responsibility for the real values lies with the manufacturer, with consulting engineers and authorities where required.
Phones and loading time
A dock may also be planned where it will go: at the shore, on a phone. Two requirements therefore apply from the start. First, the 3D model loads only when the visitor opens it; until then the page shows a poster image. Second, direct controls such as slots and drag handles must be large enough for fingers, and rotating and zooming must not block page scrolling. The library pages explain this for phones: turn and zoom inside the demo, swipe beside it to keep scrolling [1].
For loading time, what matters with docks is repetition. A layout with many booms, bollards and boats consists of many identical parts. Drawing them as instances of one model rather than as copies saves processing time, especially on a phone. A configurator should also redraw only when something changes.
Accessibility and privacy
Everything the 3D view shows should also be available as text: in the summary, the parts list and the enquiry text. Controls should be reachable by keyboard. The W3C Web Content Accessibility Guidelines (WCAG) 2.2 describe general requirements for web content [4]; which obligations apply to your offer is a question for your legal advisers. On privacy: once the enquiry sends contact and site details, you decide in the project where it goes and who stores it.
Who maintains models, rules and prices?
With docks, what changes most is tables: a new model, another section length, a different threshold, new prices for the season. These values belong in data tables separate from the code, so changes stay small and checkable. We do not offer a self-maintenance editor as standard; we make changes as part of maintenance.
The four examples
Example configurator · fictional product
Floating jetty configurator
Plan a floating jetty: presets for a guest jetty or small harbour, slide the piers, booms and berths, breakwater and fittings – with site checks and a PDF enquiry.
Example configurator · fictional product
Floating dock planner
Snap a floating dock together from elements: four models, straight, T or L shapes, gangway, ladder and fittings – with a water-depth check, sample price and PDF enquiry.
Example configurator · fictional product
Aluminium dock configurator
Put together an aluminium dock: floating or stationary, straight, L or T, sections, ladder and decking – with water-depth rules, a parts list and a PDF enquiry.
Example configurator · fictional product
Floating dock kit configurator
Put together a floating dock kit: straight, L or T shape, lengths, access ramp with a tilt check, swim island and timber deck – with a parts list and a PDF enquiry.
How enquiries from these configurators reach sales is covered in dock configurator enquiries, site visits and dealers. For the project process, see custom 3D configurator development.
Frequently asked questions
Can the dock be shown in AR at the shore?
An AR view is not offered as standard; we assess it case by case.
Can buyers recreate their own shore?
In simplified form, yes, through inputs such as shoreline length, depth or bank height. An exact terrain model does not belong in a sales configurator.
Do we need CAD data?
Not necessarily. For docks, drawings and dimension tables can be enough; we use CAD where it suits the web.
Sources
- Modelwright library: floating jetty configurator, floating dock planner, aluminium dock configurator and floating dock kit configurator pages, "Live in this demo" lists, sample-value notes and phone instructions; footer "All demo products are fictional and built with our own geometry", read 14 November 2026: modelwright.de/en/library/
- Khronos Group, glTF, read 14 November 2026: khronos.org/gltf
- Wikipedia, "Dock (maritime)", read 14 November 2026: en.wikipedia.org/wiki/Dock_(maritime))
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, read 14 November 2026: w3.org/TR/WCAG22


