Docs · Exhibition

Public models
people can explore.

Exhibition is the public browsing space for Axle Keys models — where configurable objects can be shown, studied, shared, and eventually remixed. Private Studio models become public artifacts here.

LifecyclePublishingPage structureVisibilityOpen in Studiovs ShowroomBest practices
What Exhibition is for

Where private models
become public artifacts.

Exhibition stays focused on one job: make public models useful, understandable, and discoverable. Not a full social network — not a marketplace yet. The models come first.

What Exhibition is for

  • Browse and discover public configurable models
  • Study how objects are structured inside Systems
  • Open public models in Studio
  • Share useful models and create public reference pieces
  • Build toward future remix and community workflows

What Exhibition is not yet

  • Not a full marketplace
  • Not a social network or feed
  • Not a complex community structure before there are enough models to support it
  • Not automatic — projects stay private unless you publish

The Exhibition model lifecycle

Create in StudioConfigure & reviewPublish to ExhibitionBrowse publiclyOpen in StudioShare or remix later

The model remains connected to its System, parameters, description, and creator information throughout.

Publishing

Publish when the
model is ready.

Publishing should be intentional. A broken or confusing public model weakens Exhibition for everyone.

Before publishing, review

  • Title and description
  • Selected System
  • Public preview image or live viewer
  • Exposed parameters
  • Parts visibility
  • Model limitations
  • Creator or owner attribution
  • Whether any private files are hidden
  • Whether the model should be public at all

What a strong Exhibition model includes

  • Model title and short description
  • Live 3D preview
  • System label
  • Creator or owner
  • Configurable parameters
  • Visible parts or structure
  • Usage notes and limitations
  • "Open in Studio" action
  • Share link

Goal: help a visitor understand what the object is, how it works, and what can be changed.

Page structure

How Exhibition
is organised.

Exhibition index

The main browsing page. Useful sections: featured models, recent models, System filters, object categories, curated collections. The first version can be curated rather than algorithmic — do not over-engineer filtering before there is enough content.

Model detail pages

Individual public pages for each Exhibition model at /exhibition/:slug. Includes live 3D viewer, title, description, creator, System, parameters, related parts, public notes, limitations, "Open in Studio", and eventually duplicate or fork options.

The detail page is what turns Exhibition from a gallery into a platform.

Filters and categories

Organise by System, object type, material, creator, use case, or featured status. Recommended first filters: Open Design · Cabinet Systems · T-Slot Systems · Featured · Recent.

Model visibility

Private by default.
Public on purpose.

Studio projects remain private unless explicitly shared or published. A model becomes public only when you choose.

What public information may include

  • Model name and description
  • Creator or owner attribution
  • Preview image or live 3D viewer
  • Parameters and System label
  • Public metadata and published date
  • Public notes

Do not publish sensitive files, client information, private drawings, proprietary details, or third-party material without permission.


Updating a published model

Edit privately in Studio, save a version, preview changes, then update the Exhibition listing. A public model should not break silently when the private model changes. Older versions can be preserved if needed.


Unpublishing

A user can unpublish a model at any time. Unpublishing removes the public listing, but some data may remain in backups, logs, or shared links depending on platform policy. Read Legal →

Open in Studio

The most important
Exhibition action.

Opening a public model in Studio allows it to become a working project — not just something to look at.

What "Open in Studio" may mean

  • View only
  • Duplicate to your account
  • Fork a copy
  • Request access
  • Use as a starting example
  • Configure without editing the source

The exact behavior depends on model ownership, licensing, and platform settings.

Forking and remixing (future)

A fork creates a separate copy so the original remains intact. Remixing allows variations while preserving attribution to the original.

Future remix data may track: original model, forked model, creator attribution, change history, linked Exhibition pages, and configuration history.

Don't build a complex remix graph before basic publishing works well.

Exhibition vs Showroom

Same object.
Different intent.

Exhibition and Showroom are related but different. The distinction is what the surface is for.

Exhibition● Discovery

"What interesting configurable models are available?"

Public browsing, study, and sharing. A model in Exhibition is for discovery and education — anyone can find it, explore it, and open it in Studio. The audience is anyone curious about configurable physical objects.

View Exhibition →
Showroom● Commercial

"What does this person, shop, or business offer?"

Customer-facing product-line pages. A Showroom presents a maker's or business's configurable products to buyers. More controlled than Exhibition — focused on inquiry, quoting, and ordering workflows.

Read Showroom docs →

A model may begin as an Exhibition piece and later become part of a Showroom product line. Or a Showroom product may have an Exhibition-style page for discovery and sharing. The two surfaces can work together.

Best practices
and what's coming.

● Best practices

Publish well

  • Make the model understandable to a stranger — use a short title, direct description, visible parameters
  • Don't publish too early — a confusing public model weakens Exhibition
  • Expose useful controls, not internal technical values
  • Explain limitations — if experimental or not fabrication-ready, say so
  • Connect the model to the correct System so visitors have context
  • Don't accidentally publish private files or client information
○ Future roadmap

Planned features

  • Individual model detail pages
  • Better filters and categories
  • Creator pages and profiles
  • Model forks and remix history
  • Comments and requests
  • Collections and featured builds
  • Public configuration snapshots
  • Link to fabricators
  • "Built from this" posts

See what's
been built.

Browse the public Exhibition to discover configurable models across Systems. Or open Studio to create and publish your own.