Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixes #96 #110

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fixes #96 #110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions chapter-3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -370,7 +370,7 @@ The types of code to be highlighted in a pattern library nauturally varies from

{% include figure.html src="../images/content/salesforce-code-example.png" caption="Salesforce's Lightning design system showcases the UI components' HTML and SCSS code." %}

Showcasing patterns' front-end code leads to authors writing more consistent code, but that doesn't guarantee perfection. There's still room for developers to go rogue and write sloppy, incongruent code, which is why some organizations have gone above and beyond to establish incredibly sophisticated design systems. **Companies like Lonely Planet have achieved the Holy Grail of pattern libraries, which is to say their pattern library and production environment are perfectly in sync**. We'll discuss the Holy Grail in more detail in the next chapter, but it's worth brining up in this section to demonstrate how that affects the code exposed in the context of a pattern library. Rather than surfacing HTML and CSS, Lonely Planet's [Rizzo style guide](http://rizzo.lonelyplanet.com/) surfaces the include code for teams to pull in the appropriate UI component.
Showcasing patterns' front-end code leads to authors writing more consistent code, but that doesn't guarantee perfection. There's still room for developers to go rogue and write sloppy, incongruent code, which is why some organizations have gone above and beyond to establish incredibly sophisticated design systems. **Companies like Lonely Planet have achieved the Holy Grail of pattern libraries, which is to say their pattern library and production environment are perfectly in sync**. We'll discuss the Holy Grail in more detail in the next chapter, but it's worth bringing up in this section to demonstrate how that affects the code exposed in the context of a pattern library. Rather than surfacing HTML and CSS, Lonely Planet's [Rizzo style guide](http://rizzo.lonelyplanet.com/) surfaces the include code for teams to pull in the appropriate UI component.

{% include figure.html src="../images/content/lonely-planet-code.png" caption="Lonely Planet's Rizzo design system pattern library showcases the template usage." %}

Expand Down Expand Up @@ -421,4 +421,4 @@ When choosing tools to create your pattern library, you should keep your eyes op
- Providing contextual information like which patterns make up a particular component as well as where that component gets utilized

At the end of the day, it's not about the tools we use to create pattern libraries, but rather how we use them. Creating and maintaining an effective design system means dramatically changing your organization's culture, processes, and workflows. If that sounds hard to you, it's because it is! But fear not! The next chapter will detail the entire process of creating and maintaining a successful design system to set your organization up for longterm success.