base on A styling system for Flutter <picture> <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/leoafarias/mix/main/assets/dark.svg"> <img alt="Mix logo" src="https://raw.githubusercontent.com/leoafarias/mix/main/assets/light.svg"> </picture>  [](https://pub.dev/packages/mix/changelog)   [](https://opensource.org/licenses/mit-license.php) [](https://github.com/Solido/awesome-flutter) Mix is a simple and intuitive styling system for Flutter, enabling the creation of beautiful and consistent UIs with ease. Mix brings industry-proven design system concepts to Flutter. It separates style semantics from widgets while maintaining an easy-to-understand and manageable relationship between them. - Easily compose, merge, and apply styles across widgets. - Write cleaner, more maintainable styling definitions. - Apply styles conditionally based on the BuildContext. ## Why Mix? Flutter developers often face challenges when it comes to styling widgets and maintaining a consistent look and feel across their apps. Flutter is heavily dependent on the Material Design System and theming, and that can be challenging, especially when creating your own design system. Mix addresses these challenges by creating a styling system that uses utility functions for a more intuitive and composable way to style. This approach can be kept consistent across widgets and files. ## Goals with Mix - Define visual properties outside the widget's build method while still allowing access to the BuildContext. This is done by having the style definition resolved during widget build, similar to how the current `Theme.of` works, but with much more flexibility. - Ensure consistent styling throughout your app. By having separate style definitions, you can reuse not only specific values, like colors and typography, but also entire style definitions across other styles. - Quickly adapt to changing design requirements. By promoting style composability and inheritance, you can more easily maintain a `DRY` approach to managing your design system. - Create adaptive designs and layouts by leveraging style variants, which are based on existing styles but can be applied conditionally or responsively. - Type-safe composability. Mix leverages the power of Dart's type system and class to create a type-safe styling experience. ## Guiding Principles - **Simple Abstraction**: A low-cost layer over the Flutter API, letting you style widgets without altering their core behavior, ensuring they remain compatible and predictable. - **Consistent**: Even though we are creating a new styling system, we should always keep the styling API consistent with its Flutter equivalents. - **Composable**: Styles should be easily composable by combining simple, reusable elements, promoting code reuse and maintainability. - **Extensible**: Mix should allow for reasonable overrides and reuse of its utilities, making it easy to fit your own needs. ## Key Features ### **Powerful Styling API**: Styles are easily defined using the `Style` class, which allows you to define a style's properties and values. Here's an example of defining a style: ```dart final style = Style( $box.height(100), $box.width(100), $box.color.purple(), $box.borderRadius(10), ); ``` Learn more about [styling](https://fluttermix.com/docs/guides/styling) ### **First-Class Variant Support**: First-class support for variants, allowing you to define styling variations that can be applied conditionally or responsively. ```dart {1, 8-12, 15} const onOutlined = Variant('outlined'); final baseStyle = Style( $box.borderRadius(10), $box.color.black(), $text.style.color.white(), onOutlined( $box.color.transparent(), $box.border.color.black(), $text.style.color.black(), ), ); final outlinedStyle = baseStyle.applyVariant(onOutlined); ``` Learn more about [variants](https://fluttermix.com/docs/guides/variants) ### **BuildContext Responsive Styling**: Mix allows you to define styles that are context-aware, allowing you to apply styles conditionally based on the BuildContext. ```dart {4-7} final style = Style( $box.color.black(), $text.style.color.white(), $on.dark( $box.color.white(), $text.style.color.black(), ), ); ``` Learn more about [context variants](https://fluttermix.com/docs/guides/variants#context-variants) ### **Design Tokens and Theming**: Mix goes beyond the Material `Theme` definitions by allowing the definition of design tokens and properties that can be used across all styling utilities. ### **Utility-First Approach**: A complete set of utility primitives allows you to define styling properties and values in a more intuitive and composable way. ```dart $box.padding(20); /// Padding 20 on all sides $box.padding(20, 10); /// Padding 20 on top and bottom, 10 on left and right $box.padding.top(20); /// Padding 20 on top $box.padding.horizontal(20); /// Padding 20 on left and right ``` Learn more about [utilities](https://fluttermix.com/docs/overview/utility-first) ## Contributors <a href="https://github.com/conceptadev/mix/graphs/contributors"> <img src="https://contrib.rocks/image?repo=conceptadev/mix" /> </a> ", Assign "at most 3 tags" to the expected json: {"id":"11673","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"