微信公眾號無需二次登錄

重點 (Top highlight)

The design system concept can be differently defined according to each person’s background. Designers may say that a design system is a style guide while developers may say it is UI standards, or specs, or even assets. Whatever the words used, a solid design system might have different purposes, but one can go through all backgrounds and areas: to be documentation.

可以根據每個人的背景不同地定義設計系統概念。 設計師可能會說設計系統是樣式指南，而開發人員可能會說它是UI標準，規范甚至資產。 不管使用什么措辭，一個堅實的設計系統可能都有不同的目的，但是一個系統可以遍及所有背景和領域：作為文檔。

Design systems are documentation: document how components look, how they should be used, how they made part of products.設計系統是文檔：記錄組件的外觀，應如何使用它們，如何將它們制成產品的一部分。

There are several ways to represent one. You can have static documentation using tools like Sketch, Invision, or Figma, usually preferred and used by designers. Interactive representation using tools like Storybook, bit.dev, or Zeplin, typically lead by developers. The great benefit of the second kind of documentation is that it can show all different states, dynamically changed by you, as if you were interacting with the implementation in the “real” product. No more unexpected states or “what is the button color when hovered?” slack messages.

有幾種表示方法。 您可以使用設計人員通常首選和使用的工具(例如Sketch ， Invision或Figma)獲得靜態文檔。 使用工具，如交互式表示故事書 ， bit.dev ，或Zeplin ，通常由開發商引起。 第二種文檔的最大好處是，它可以顯示您動態更改的所有不同狀態，就像您正在與“真實”產品中的實現進行交互一樣。 不再出現意外狀態或“ 懸停時按鈕的顏色是什么？” 松弛消息。

bit.dev component explorerbit.dev組件瀏覽器

Everybody knows that naming things is hard, right? If you use the design system’s components, you no longer have to deal with that. Stop having different names for the same thing: one project with input, another with form field, and another with text field. Have just one, rich and well defined, and everybody will be on the same page.

大家都知道命名很難，對嗎？ 如果使用設計系統的組件，則不再需要處理。 停止為同一事物使用不同的名稱：一個帶有輸入的項目，另一個帶有表單字段的項目 ，另一個帶有文本字段的項目 。 只有一個，內容豐富且定義明確， 每個人都會在同一頁面上 。

解決問題(一次！) (Solve problems (once!))

Even the smallest component can have to deal with multiple usage scenarios. If you solve a problem properly in one place, you don’t need to solve it every time you have the same usage scenario, and you won’t forget to implement some edge and not common scenarios. Make room for productivity, implement wisely. New use case? Solve it in the design system, you’ll have it solved next time, and you can skip it in a blink of an eye.

即使是最小的組件也可能必須處理多種使用情況。 如果您在一個地方正確地解決了一個問題，那么您不必每次都具有相同的使用場景時就解決它，并且您將不會忘記實施某些優勢和不常見的場景。 為生產力騰出空間，明智地實施。 新用例？ 在設計系統中解決它，下一次您將解決它，您可以在眨眼之間跳過它。

When you implement a design system, you join all components in just one place. You can have it exported as a library to use in all projects, allowing to code reuse, avoiding code duplication. It also means less CSS and less styling, no more slightly different components that should be equal, no more different margins and colors, no more small style fixes kind of commits. However, have in mind that changing anything in the library will change in all products when updated. That can be either good or bad: be careful with breaking changes.

實施設計系統時，將所有組件僅放在一個地方。 您可以將其導出為庫以在所有項目中使用，從而允許代碼重用，避免代碼重復。 這也意味著更少CSS和更少的樣式，不再應該具有相同的組件，沒有更多不同的邊距和顏色，沒有更多的小樣式修復提交。 但是，請記住，更改庫中的任何內容都會在更新所有產品時對其進行更改。 這可能是好事或壞事：小心更改。

重復 (Iterate)

A design system is itself a project, but it shouldn’t have an end, it should grow as projects, and the company grows too. The process of defining it is iterative. Improvements are made, and components are added, don’t expect to have a finished design system from one day to the next. New projects bring new components: a design system is like a company’s baby, it starts small and will grow and improve as time goes by. Iterate. Redesign. Improve.

設計系統本身就是一個項目，但它不應有目的，它應隨著項目的發展而增長，公司也應隨之發展。 定義它的過程是迭代的。 進行了改進，并添加了組件，不要指望一天到一天都有完整的設計系統。 新項目帶來了新的組件：設計系統就像公司的嬰兒一樣，從小規模開始，隨著時間的流逝將不斷發展和完善。 重復。 重新設計。 提高。

You can work in a project and update the design system at the same time, npm link is there for you. It allows developers to link the design system’s repository to the project that they are working on.

您可以在一個項目中工作并同時更新設計系統， npm鏈接可為您提供。 它允許開發人員將設計系統的存儲庫鏈接到他們正在從事的項目。

[Design System] npm link
[Project] npm link @your-design-system-library

This way, the project will no longer look for the package online, it will consume it locally, which means that every time the design system changes, your project will be updated. When the library is updated to the next version, there are no unexpected errors or changes. No excuses not to update the design system, right?

這樣，項目將不再在線查找包，而將在本地使用它，這意味著每當設計系統更改時，您的項目就會被更新。 將庫更新到下一個版本時，不會發生意外錯誤或更改。 沒有理由不更新設計系統，對嗎？

真理的單一來源 (Single source of truth)

Communication has a significant role in product success. When having different teams working for the same end, they need to be aligned. They need to work with the same thing in mind and to communicate properly. Having a design system implemented improves the communication between all team members since there is only one single source of truth resulting in transparency, well-defined process, and coherent products.

溝通對于產品成功至關重要。 當有不同的團隊為同一目標工作時，他們需要保持一致。 他們需要牢記同一件事并進行正確溝通。 實施設計系統可以改善所有團隊成員之間的溝通，因為只有一個單一的事實來源會導致透明，定義明確的流程和連貫的產品 。

The communication between designers and developers isn’t always clean and precisely done. If both use the same documentation, designers will know that they only need to review it in one place and not everywhere the component is implemented. On the other hand, developers will be sure that they are using the right and most updated component.

設計師和開發人員之間的交流并非總是干凈無誤的。 如果兩者都使用相同的文檔，則設計人員將知道他們只需要在一個地方而不是在組件實現的所有地方進行審閱。 另一方面，開發人員將確保他們使用的是正確且最新的組件。

We all know that everything changes fast. A single source of truth, updated and well defined, can improve the communication between all team members, avoiding lost or incorrect information. In addition, having all implemented as reusable components lead to a faster and optimized implementation. A design system can contribute to organized teams and to product success, give it a chance.

我們都知道，一切都會快速變化。 更新并定義明確的單個事實來源可以改善所有團隊成員之間的溝通，避免丟失或錯誤的信息。 另外，將所有實現都實現為可重用組件可以實現更快，更優化的實現。 設計系統可以為有組織的團隊和產品成功做出貢獻，給它一個機會。

See more about npm link here.

在此處查看有關npm鏈接的更多信息。

UX Para Minas Pretas (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. Silence against systemic racism is not an option. Build the design community you believe in.UX Para Minas Pretas (UX For Black Women)，這是一個巴西組織，致力于通過采取行動，賦權和知識共享的舉措來促進科技行業中的黑人女性平等。 對系統性種族主義保持沉默是不可行的。 建立您相信的設計社區。

翻譯自: https://uxdesign.cc/you-dont-need-to-solve-problems-twice-you-need-a-design-system-b1b9dbb76685

微信公眾號無需二次登錄

總結

以上是生活随笔為你收集整理的微信公众号无需二次登录_您无需两次解决问题-您需要一个设计系统的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。