DX & authoring experience: for SDC+code components, the example is treated as the default, may not be desirable

+++++++1 for default value being a placeholder. I've placed a paragraph component so many times and starting typing only to start adding letters after the example content.

However, that's really hard for non-text inputs. In that case I think it's fine to render the example as the default but leave the form empty.

wim leers → credited f.mazeikis → .

It is hard for non-textual prop shapes .

But even for some textual ones, like date and time. Let alone images.

For images, @lauriii has been saying that we need to make XBenhance what core’s image widget and media library widget do, precisely to show the default as a kind of placeholder.

No designs exist for it yet to my knowledge.

Given your +1, assigning to @lauriii.

wim leers → credited effulgentsia → .

Given a meeting last night surfaced this as a challenge/stable blocker for code components, and @effulgentsia’s firm +1 to label default value as “initial value” in the UI, to set clear expectations for content authors, bumping to Critical.

My experience is that most page builders treat default values exactly the way Experience Builder does now: if there’s text in a field, that’s what will be saved. This matches how forms typically behave: when you see prefilled text, you expect it to be submitted unless you overwrite it.

That said, we need to decide whether to rely on default or examples in JSON Schema for this. Personally, I don’t have a strong preference either way.

Additionally, we may want to consider supporting both a placeholder value which is purely a form display concern and a true fallback value which is a rendering concern (i.e. fallback value determined at render time). I don’t think these should block the stable release.

FWIW, this is called "Default value" in the Field UI module today and it behaves the same way as XB.

@lauriii in #10:

FWIW, this is called "Default value" in the Field UI module today and it behaves the same way as XB.

You dropped from the call with @f.mazeikis, @jessebaker, @effulgensia and others, in which they explained that precisely this behavior has actually led to a LOT of support requests for Acquia Site Studio. Short version: users expected that changing the default would make the new default appear in all component instances where the default had not been modified.

Hence my proposal from #7.

#8 is a very narrow reading/interpretation of the problem described with nuance in the issue summary, which @f.mazeikis had nothing to add to, and @mglaman added #2 to.

Crucially, #8's ignores that it cannot work like that for SDC's default images — otherwise they'd end up being saved into Drupal's Media Library. Or is that what you're implying? 🤔 That'd be counter to what you said before.

larowlan → credited heyyo → .

From slack via @heyyo

The first example is used as default, but not the default property itself. What's the purpose of default as?

i.e. if a default is provided, we're ignoring it and using the example value. That feels like a bug and we should address it here or open a separate issue - thoughts on which you'd prefer?

Still needs @lauriii per #11.