Join the Webstudio community

Updated 4 weeks ago

Terminology Question: The Use of "Instance" in Web-Builder Contexts

Terminology question. In your App / Docs / Videos you always speak of instances if you refer to elements on the page. I understand an instance as a non-unique copy of something, often driven by some common parent. Elements on the canvas may be an instance – but often enough, they are unique – such as images.

Of course, one from the perspective of the app-creator may see elements on screen as instances of components you make available – in that sense, bitmaps indeed live in an instance of your image component

Then again – users will likely find their creations unique and think of the "About"-Card and the "Contact" card as different items, even the underlying HTML-element has the same structure.

This just struck me as odd and unprecise – but I'm neither a native English speaker, nor a code-wizard.

Is this usage for the term instance common in visual Web-Builders?
Attachment
image.png
O
H
10 comments
Instance is correct, what you see and interact with on canvas is a component instance, it renders an html element
Component > Instance > Element
Ok, I understood this derivation – and it undoubtedly is technically correct. But should one use this term?

Designers who build unique websites with Webstudio will certainly not imagine their website as a bunch of instances (i.e. a trivial collection of essentially the same things. Of course, they will continue talking of elements…

One creates a mismatch between what people have in their head and the official term. It appears quite clever to me, that Webflow chose the "dirty" term elements in their GUI.
precise language is important and instances isn't that bad or far fetched from how most people think
unless I find out people struggle with that name, I see no reason to change
One creates a mismatch between what people have in their head and the official term.

That's an assumption I would need to validate
It appears quite clever to me, that Webflow chose the "dirty" term elements in their GUI.

No they just didn't know better at the time, its historical
I also love precise language. But terms change semantics when work contexts change. I'm sure you can see my perspective too.
All I hear is a preference based on past experience.
If I hear a lot of this feedback, we can think about it, so far you are the first one 🙂
Add a reply
Sign up and join the conversation on Discord