<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/the-case-for-null-in-design-systems-5qawl2dlh" -->

---
title: The case for null in design systems | daily.dev
description: Exploring how the concept of null—an intentional absence—can be a useful tool in design systems, especially those with parent and child variants across an...
canonical: https://daily.dev/posts/the-case-for-null-in-design-systems-5qawl2dlh
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: The case for null in design systems | daily.dev
og:description: Exploring how the concept of null—an intentional absence—can be a useful tool in design systems, especially those with parent and child variants across an...
og:url: https://daily.dev/posts/the-case-for-null-in-design-systems-5qawl2dlh
og:image: https://api.daily.dev/og/posts/5qaWL2Dlh.png
og:image:alt: The case for null in design systems
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The case for null in design systems

**[Eric Bailey](https://daily.dev/sources/ericwbailey)** · 6 min read · 0 upvotes · 0 comments

## Summary

Exploring how the concept of null—an intentional absence—can be a useful tool in design systems, especially those with parent and child variants across an organization. Drawing on the art history concept of horror vacui (fear of empty space), the piece argues that unexplained gaps in component coverage tempt teams to fill them unnecessarily. Using an audit of button component variants across a parent design system and two child design systems as an example, it proposes marking deliberate gaps as 'null' rather than leaving them ambiguous, and suggests documentation techniques like inline notes and unlinked 'ghost' pages to communicate why a component or variant is intentionally missing.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://adhocteam.us/2022/07/05/null-in-design-systems>

## Questions this post answers

### How should I document a component variant that exists in one design system but not another?

Mark the absence as intentional rather than leaving it ambiguous, using a null designation to signal that the gap is deliberate rather than a mistake. For a missing variant, add a note on the component's documentation page explaining the discrepancy; for an entirely missing component, create an unlinked 'ghost' page that explains why it isn't present and links to supporting material.

_daily.dev surfaces practical design-system patterns for teams documenting intentional gaps across products._

## Similar posts on daily.dev

- [The Empty State Illusion: Why Your “No Data” Screens Are Quietly Destroying User Trust](https://daily.dev/posts/the-empty-state-illusion-why-your-no-data-screens-are-quietly-destroying-user-trust-rbpmrrbca) · Medium · 0 upvotes · 0 comments
- [What Actually Happens to a Design System When the Founder Leaves](https://daily.dev/posts/what-actually-happens-to-a-design-system-when-the-founder-leaves-zh8qqhoto) · Medium · 7 upvotes · 1 comments
- [Atomic Design Systems: Why the Labels Don’t Matter](https://daily.dev/posts/atomic-design-systems-why-the-labels-don-t-matter-l5axjec20) · Qt · 162 upvotes · 1 comments
- [Empty box is not enough](https://daily.dev/posts/empty-box-is-not-enough-4kvvqjknf) · Hardik Pandya · 4 upvotes · 0 comments
- [Design Principles Unpacked, No. 2 Hierarchy](https://daily.dev/posts/design-principles-unpacked-no-2-hierarchy-n6itih0xk) · Telerik · 0 upvotes · 0 comments

---

Tags: [#ui-design](https://daily.dev/tags/ui-design), [#design-systems](https://daily.dev/tags/design-systems)

[View this post on daily.dev](https://daily.dev/posts/the-case-for-null-in-design-systems-5qawl2dlh)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"The case for null in design systems","url":"https://daily.dev/posts/the-case-for-null-in-design-systems-5qawl2dlh","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-case-for-null-in-design-systems-5qawl2dlh"},"datePublished":"2026-09-20T07:43:57.776Z","dateModified":"2026-09-20T07:45:35.641Z","description":"Exploring how the concept of null—an intentional absence—can be a useful tool in design systems, especially those with parent and child variants across an...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e0b7681003e2f410cd3886978f60cc35?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e0b7681003e2f410cd3886978f60cc35?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Eric Bailey","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Eric Bailey","logo":"https://media.daily.dev/image/upload/s--r1vwe6z1--/f_auto,q_auto/v1789890198/logos/ericwbailey?_a=BAMAMicg0","url":"https://daily.dev/sources/ericwbailey"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-case-for-null-in-design-systems-5qawl2dlh","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ui-design,design-systems","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Eric Bailey","item":"https://daily.dev/sources/ericwbailey"},{"@type":"ListItem","position":3,"name":"The case for null in design systems"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-case-for-null-in-design-systems-5qawl2dlh#faq","mainEntity":[{"@type":"Question","name":"How should I document a component variant that exists in one design system but not another?","acceptedAnswer":{"@type":"Answer","text":"Mark the absence as intentional rather than leaving it ambiguous, using a null designation to signal that the gap is deliberate rather than a mistake. For a missing variant, add a note on the component's documentation page explaining the discrepancy; for an entirely missing component, create an unlinked 'ghost' page that explains why it isn't present and links to supporting material. daily.dev surfaces practical design-system patterns for teams documenting intentional gaps across products."}}]}
```

