Sign in
Open the team URL and use the credentials provided by the project administrator.
Practical team handbook
Design together.
Decide clearly.
A shared way of working for planners, landscape designers, visualization teams, and reviewers developing park concepts remotely in the Collaborative Design Configurator.
Landscape designer
Visualization lead
Design reviewer
1
2
3
01 · Quick start
From sign-in to a saved option.
Use this four-step sequence for a first working session. It establishes the correct plan, captures an edit, and leaves the shared project in a known state.
Confirm the layout
Select the intended concept plan. Choose Use layout in project so it becomes part of the active configuration.
Make one focused edit
Choose a layer, double-click the plan to add an item, then use the Properties panel to name and refine it.
Save the milestone
Select Save project. Download JSON as a portable snapshot when the option is ready for review.
Important: saving is intentional.
Canvas edits update your active browser session immediately, but Save project writes that state to the authoritative project configuration. Agree who saves during a live team session.
02 · Workspace map
Four areas, one design state.
The interface separates navigation, spatial editing, detailed properties, and project-level actions so the team can move from broad composition to precise review.
1
Top action barUpload inputs, import or download JSON, save the project, and generate Blender output.
2
Left panelChoose layers and layouts, search the GLB library, and control reference visibility.
3
Plan canvasPlace, select, and drag spatial elements while reading live pointer coordinates.
4
Right panelFine-tune selected items, configure render settings, and inspect generated views.
03 · Team roles
Clear ownership keeps remote work fluid.
CDC does not force formal permissions for every discipline. Use lightweight team roles to prevent conflicting edits and make review responsibilities explicit.
Design editor
Maintains the active layout, places program elements, develops paths, and coordinates protected trees and site constraints.
Visualization lead
Registers GLB assets, verifies dimensions, defines render cameras and lights, and generates day/night review images.
Review lead
Names the option under review, checks discipline inputs, records decisions, and authorizes the shared save or output milestone.
04 · Shared workflow
A repeatable review loop.
Treat each design alternative as a short, traceable cycle. The objective is not simply to move objects; it is to turn design intent into a state the whole team can inspect.
Frame the question
State the decision before editing: for example, “increase shaded family seating without narrowing the jogging loop.”
Good review questions are spatial and testable.Load the correct context
Confirm the selected plan, show the relevant layers, and set reference transparency so existing and proposed information are easy to distinguish.
Develop the alternative
Add or reposition assets, edit dimensions and properties, and keep names meaningful enough for another team member to understand.
Review from evidence
Use visibility toggles, security coverage, tree protection radii, camera views, and lighting modes to test the option against the original question.
Record the milestone
Apply pending property changes, save the shared project, download JSON for a named snapshot, and generate renders or Blender output when required.
Communicate immediately after the shared save.05 · Design layers
Use the right layer for the question.
Selecting a layer changes what a double-click adds and which properties become available. Turn on Show all layers for coordination; isolate a layer for precise editing.
ObjectsGLB assets such as shade structures, play elements, furniture, courts, and landscape features. Supports rotation, scale, duplication, and enable/disable.
Jogging trackA closed route defined by editable vertices and a shared width. Double-click near a segment to insert a new vertex.
Protected treesExisting or retained trees with a visible protection radius for site coordination.
Path lightsLighting positions sharing the configured luminous flux and pole height.
Accent lightsFeature-lighting positions for focal elements, landscape, or architectural emphasis.
Security camerasCamera locations with directional or 360-degree coverage, range, height, and orientation.
Blender lightsPoint, area, spot, or sun lights with height, power, size, color, and render enable controls.
Render camerasPresentation viewpoints with position, height, target, target height, and lens settings.
06 · Editing actions
Work quickly, then fine-tune precisely.
Use direct manipulation for early composition and the Properties panel for controlled adjustments. Expand a topic below for the exact sequence.
Place and move an object
- Select an item in the Asset library.
- Choose Place selected asset or double-click the plan.
- Drag the placed object to move it.
- Edit X/Y, rotation, and scale in Properties; then choose Apply changes.
Add a point to another layer
- Select the required layer.
- Double-click the target location on the plan.
- Select the new marker and complete its available properties.
- For a track, double-click near the segment where a vertex should be inserted.
Copy or duplicate an item
Choose Duplicate for a nearby copy. Alternatively, copy and paste from the Properties panel or use Ctrl + C and Ctrl + V. Paste only works while the matching layer is active.
Register a new GLB asset
- Upload the GLB from the top bar.
- Select + Register asset.
- Choose the uploaded model and verify extracted width, depth, and height.
- Give it a stable asset key, set import rotation if needed, and save.
Change the concept plan
Upload a PNG, JPG, JPEG, or WebP if needed. Select it under Design layouts, visually confirm it, then choose Use layout in project. Adjust reference transparency to compare information.
Remove an item safely
Select the marker, vertex, light, camera, or object; verify its name and layer in Properties; then choose Delete. Save only after confirming that the resulting plan is correct.
Ctrl + C Copy selectedCtrl + V Paste on active layerDouble-click Add to active layerDrag Reposition selected item
07 · Review & output
Check the design before you generate.
A clean output begins with a deliberate review state. Use these two checklists before rendering cameras or producing the coordinated Blender model.
Design review
- The intended layout is active.
- Object names and positions are understandable.
- Track width and geometry are coherent.
- Tree protection and camera coverage are checked.
- Required layers are visible and unexpected items are removed.
- Pending property edits have been applied.
Output review
- Render cameras have meaningful names.
- Targets, heights, and lenses frame the intended view.
- Day, night, or both is selected deliberately.
- Render lights are enabled as required.
- Sun power and angle suit the review purpose.
- The shared project is saved before generation.
Choose the lightest useful output.
Use camera renders for focused design conversations, JSON for a portable configuration snapshot, and the generated .blend file when the selected option needs visualization or further 3D development.
08 · Team conventions
Four rules for remote clarity.
The configurator stores one authoritative design state. Simple working agreements reduce collisions and preserve the reasoning behind each milestone.
Name before sharing
Use descriptive asset and camera names such as family_shade_north_option_b or arrival_evening_review.
One active editor per review
Others can direct, observe, or record decisions, but nominate one person to make and save edits during a live session.
Snapshot meaningful milestones
Download JSON after an agreed option—not after every movement—and include the option name and date when storing it externally.
State what changed
After saving, tell the team which layers changed, which review question was addressed, and which output should be inspected.
09 · Administration
Keep access and project data controlled.
The current login is intentionally simple and suitable for a managed design team. Internet-facing deployment needs the usual production safeguards.
Team access
Usernames and shared passwords are managed in users.json. Use team-specific credentials and update them before sharing the deployment.
Authoritative data
The server writes the saved configuration to scripts/park/config.json. Include it in the project backup routine.
Uploaded inputs
GLB files are stored under Inputs/3Dobjects; layouts are stored under Inputs/design_layouts.
Generated outputs
Previews, generated Blender models, JSON reports, and rendered images are stored under storage. Manage storage and retention as the project grows.
For internet-facing use
Put HTTPS through Nginx or Caddy in front of the service and configure firewall rules, request-size limits, backups, and access logging. Because CDC accepts uploads and can run Blender, do not expose it with default or broadly shared credentials.
Ready for the next review?
Open the shared plan and make the decision visible.
Start with a clear question, nominate the active editor, and leave the project in a saved, reviewable state.