Atom 学习

¥Atom Learning

结合设计系统中的 Stitches，Radix Primitives 让我们能够专注于优化 UI 的可用性，而无需从头构建或钻研难以访问且 props 繁多的 UI 库。

¥Combined with Stitches in our design system, Radix Primitives allowed us to focus on optimising the usability of our UI rather than building from scratch or hacking our way through inaccessible and prop-heavy UI libraries.

请描述一下你正在使用 Radix Primitives 的项目类型？

¥Describe the type of project you are using Radix Primitives on?

我们在内部设计系统中使用 Radix Primitives，它即将发布 1.0 初始版本，我们正在开始将当前的 monorepo 迁移到它。它独立于我们的主要应用，因此我们将其开源，并计划在 Atom 需要创建的任何 Web 组件中使用它。我们有一些来自设计和工程团队的核心利益相关者，但长期目标是让两个团队的成员都做出贡献。

¥We’re using Radix Primitives on our internal design system, it’s getting close to an initial 1.0 release and we’re starting the process of migrating our current monorepo over to it. It’s independent from our main application so we open-sourced it and are planning to use it across any web properties we need to create at Atom. We have a few core stakeholders from design and engineering but the long-term aim is to have contributions from members of both teams.

Radix Primitives 在哪些方面帮助了你和你的公司？

¥In what ways have Radix Primitives helped you and your company?

Radix Primitives 有很多优点，对我们非常有用：无头 UI 和组合模型、广泛的基元选择，以及其构建和测试的可访问性。它也比我们之前用于 UI 的许多其他包轻量级得多。

¥There are a bunch of things that have made Radix Primitives incredibly useful for us: the headless UI and composition model, the broad selection of primitives, and the fact that it’s built and tested for accessibility. It’s also far more lightweight than a lot of the other packages that we were previously using for our UI.

对于我们来说，创建复杂的界面并仍然依赖于良好的可访问性基准非常简单。结合设计系统中的 Stitches，我们能够专注于优化 UI 的可用性，而无需从头构建或钻研难以访问且 props 繁多的 UI 库。

¥It has been really simple for us to create complex interfaces and still rely on a good baseline of accessibility. Combined with Stitches in our design system, it has allowed us to focus on optimising the usability of our UI rather than building from scratch or hacking our way through inaccessible and prop-heavy UI libraries.

软件包和库来来去去，你会发现自己每年都在从一个 API 迁移到另一个 API，各个 API 之间总是存在不一致的情况。因此，找到大量能够解决明确定义的问题的组件令人耳目一新。它让我有信心，采用 Radix 意味着未来的组件将匹配相同的值，并且我们的 UI 基元将保持一致性。

¥Packages and libraries come and go, you can find yourself migrating from one API to another every year, inconsistencies abound from one to the next. So to find a large set of components that tackle a clear and well-defined problem is refreshing. It gives me confidence that adopting Radix will mean future components will match these same values and our UI primitives will continue to be consistent.

你对 Radix 开发者体验有何看法？

¥What are your thoughts on Radix developer experience?

跨基元的一致性非常好，易于理解并在它们之间移动。过去，我们在配置大型库时遇到了一些问题，因此组合模型非常适合我们构建 React 应用的方式。我们倾向于依赖 Radix 设置的默认值，因此我无法对许多可用的属性发表评论。

¥The consistency across primitives is great, it’s easy to understand and move between them. We’ve had issues with configuring heavy libraries in the past so the composition model is great for how we like to build React applications. We tend to rely on the defaults set by Radix so I can’t comment on many of the props that are available.

你对 Radix 文档有何看法？

¥What are your thoughts on Radix docs?

基础组件的文档非常精彩，这也是我们在 Atom 中采用它的主要卖点之一。这些示例、实时代码、详细的 prop 解释以及对“为什么”的深入解释对我们来说非常突出。在文档的正中央放置一个精心编写的“愿景”对我们来说尤为重要。

¥The documentation for the primitives is fantastic and was one of the main selling points for us to adopt it at Atom. The examples, live code, detailed prop explanations and high-level explanation of the “why” were stand-outs for us. Having a well written “Vision” front and center of the docs was especially important for us.