Component Libraries Permalink: Component Libraries Bookmark Icon

This article from Clearleft on building component libraries resonates with me a lot. Especially this part right in the beginning made me smile, because I recently had a similar conversation about how to call "this thing" now. It's not easy to choose the right words and language around what we build, especially to make it understandable to people that might not be as involved as we developers are.

Libraries, styleguides, components, patterns, modules, layouts, pages, atoms, molecules, organisms, blocks, modifiers, variants… there is a lot of domain-specific language floating around this niche corner of design and development. Like with anything, language can either clarify or obfuscate, and so it’s important to define and then be consistent with the words that you are using on your projects.

Not only this, but there are many other great points in there, and the article is definitely worth a read.


Leave a comment

Available formatting commands

Use Markdown commands or their HTML equivalents to add simple formatting to your comment:

Text markup
*italic*, **bold**, ~~strikethrough~~, `code` and <mark>marked text</mark>.
Lists
- Unordered item 1
- Unordered list item 2
1. Ordered list item 1
2. Ordered list item 2
Quotations
> Quoted text
Code blocks
```
// A simple code block
```
```php
// Some PHP code
phpinfo();
```
Links
[Link text](https://example.com)
Full URLs are automatically converted into links.

Replied on your own website? Send a Webmention!