Glossary entry

Edit Vs. Save

In modern WordPress block development, the "Edit vs. Save" concept refers to the two distinct functions that define a block's behavior and output. The `edit` function describes how the block appears within the Gutenberg editor UI; it includes the controls, settings, and interactive elements that the content creator sees. The `save` function, on the other hand, describes the static HTML that is actually stored in the `wp_posts` table and rendered on the front end of the site. This separation allows developers to create high-end, complex admin experiences (like our link suggester sidebar) that result in lean, high-performance HTML for the end-user. Understanding the relationship between these two functions is critical for ensuring data integrity and preventing "Block Validation" errors. While the `edit` function often uses React components to provide a rich user interface, the `save` function must produce consistent, valid HTML that search engines and browsers can process efficiently. For manufacturing or enterprise sites, this means you can build extremely sophisticated internal tools that never add "bloat" to the public-facing website.

No published articles use Edit Vs. Save yet.

When new articles use this term, they will appear here.