Menu

False Affordance in WordPress (4wp.dev Methodologies): When UI Promises What Code Doesn't Deliver
📰

False Affordance in WordPress (4wp.dev Methodologies): When UI Promises What Code Doesn't Deliver

DEV Community: frontend·Anatoliy Dovgun·24 days ago
#9irIpHbM
#devtofrontend#devto#dev#button#nothing
Reading 0:00
15s threshold

A "Show more" button on my own portfolio showed nothing, and the console stayed clean. This post is the write-up: what a false affordance is, why it slips into WordPress themes and plugins, and how to fix it in a classic PHP template and in a block theme (FSE) with a Query Loop + JS. It is part of the Methodologies series on 4wp.dev.

Related on 4wp.dev: Full Site Editing and theme.json · Component-Driven Development · Atomic Design · TDD

What a false affordance is

A false affordance is an interface element that suggests an action is possible, but the action does not actually happen. A button that does nothing. A toggle with no effect. A setting that is saved and never applied.

The term comes from Don Norman's The Design of Everyday Things : a door handle you are supposed to push is a false affordance, because the handle invites you to pull.

It sounds like a design topic, but in WordPress it is mostly an engineering one. The design shows the promise. The code is what breaks it.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.