An Argument Against Field Validation

From Issue #18

The folks at Prismic explain why they abolished required fields: Unpopular opinion: why required fields lead to terrible UX

Their argument boils down to editor flow, and says that developers should simply account for potentially missing fields in their templating. Developers might have to do this once when setting up a template, but editors would have to deal with required fields every time they generate content.

I might not agree totally, but Prismic argues their point well, and I love that they brought it up and injected it into the common discussion.

This is item #87 in a sequence of 305 items.

You can use your left/right arrow keys to navigate