¥University of Amsterdam
Radix Primitives 使我们能够为我们的设计系统构建可访问且可定制的组件，而无需强制我们使用预定义的样式。这为我们节省了大量重复造轮子的时间。
¥Radix Primitives allow us to build accessible and customisable components for our design system, without forcing us into a pre-defined style. This saves us a lot of time reinventing the wheel.
请描述一下你正在使用 Radix Primitives 的项目类型？
¥Describe the type of project you are using Radix Primitives on?
在阿姆斯特丹大学，我们正在彻底重建学生信息门户。因为我们可以忽略所有遗留代码，所以我们从头开始建立一个设计系统。此设计系统仍处于起步阶段，但将在多个学生平台上使用。我们目前的团队规模相对较小，只有 2 名前端开发者和 1 名后端开发者。
¥At the University of Amsterdam we’re completely rebuilding the student information portal. Because we can ignore all legacy code, we’re setting up a design system from scratch. This design system is still in its infancy but will be used across multiple student platforms. Our current team is relatively small, with only 2 front-end and 1 back-end developer.
Radix Primitives 在哪些方面帮助了你和你的公司？
¥In what ways have Radix Primitives helped you and your company?
Radix Primitives 使我们能够为我们的设计系统构建可访问且可定制的组件，而无需强制我们使用预定义的样式。Radix 是我们设计系统的完美起点，因为大多数基元都符合我们的确切需求。这为我们节省了大量重复造轮子的时间。
¥Radix Primitives allow us to build accessible and customisable components for our design system, without forcing us into a pre-defined style. Radix is the perfect starting point for our design system, because most of the primitives line up with our exact needs. This saves us a lot of time reinventing the wheel.
你对 Radix 开发者体验有何看法？
¥What are your thoughts on Radix developer experience?
我们最喜欢 Radix 的地方在于它为开发者提供的体验非常新颖。它没有被大量的组件或需要遵循的约定所淹没。它提供了一组优秀的基元组件，易于定制，并可根据我们自己的需求进行样式设置。
¥What we like the most about Radix is the fact that its developer experience is so fresh. It's not bloated by tons of components or conventions you should adhere to. It just provides a great set of primitive components that are easy to customise and easy to style to our own needs.
从一开始就很清楚，开发者体验是 Radix 的主要卖点之一。我们将 TypeScript 与 VSCode 结合使用，Radix Primitives 提供的开箱即用的代码建议使 API 非常易于实现。在实现一个基础组件后，我们很少需要重新阅读文档。
¥It was clear from the start that the developer experience was one of the main selling points for Radix. We use TypeScript in combination with VSCode and the code suggestions Radix Primitives provide out of the box because of this make the API very easy to implement. We rarely need to re-read the documentation after implementing a primitive.
另一个可主题化的 React 组件库 Chakra UI，虽然本身就很出色，但由于其自身规则和工具过于臃肿，我不再推荐它。
¥Another themeable React component library, Chakra UI, while great in its own way, became so bloated with its own rules and utils that I stopped recommending it.
Radix 只提供逻辑属性和直接的类型定义。每个组件都有单独的版本控制，这使我们能够选择要实现的基元。我们喜欢它的简洁性。
¥Radix just provides you with logical props and straightforward typings. Each component is separately versioned which allows us to pick and choose which primitives we want to implement. We like the simplicity of this.
你对 Radix 文档有何看法？
¥What are your thoughts on Radix docs?
文档很棒！它们提供了精彩的介绍，并清晰地展示了每个基础组件的代码示例。我喜欢“结构”和基本示例之间的分离。
¥The docs are great! They provide a great introduction and clearly show code examples for each primitive. I like the split between the ‘anatomy’ and a basic example.
虽然我注意到某些功能或“最佳实践”并不总是在文档中提及。这可能是因为它们仍有可能发生变化，我想。我使用 Radix 设计系统来获取一些组件的更多实际使用示例，该代码库中使用的一些实践经验值得添加到 Radix 文档中（例如，将多态性与 Stitches 结合使用）。
¥Although I noticed some functionality or “best practices” are not always mentioned in the docs. This might be because they are still subject to change I can imagine. I used the Radix design system for more practical use examples of some components and some of the practices used in that repo would be welcome additions to the Radix documentation (E.g polymorphism in combination with Stitches).