- What is Majid DS and how does it relate to Flux UI?
- Majid DS is an RTL/Persian-first UI kit for Laravel Livewire built on top of Flux UI. It does not replace Flux; you keep existing flux:* components and gain an mds:* namespace with Persian typography, digits, Jalali dates, Toman/Rial pricing, and e-commerce components. It adds product cards, quantity steppers, countdowns, checkout steppers, ratings, and open versions of some Flux Pro-only components. All components are RTL-first, support dark mode, and use Flux accent color tokens.
- How do I install Majid DS in a Laravel Livewire application?
- Install it with Composer using composer require mahdimajidzadeh/ds, then follow the README for any required Flux UI setup, config publishing, or asset publishing. Laravel package auto-discovery likely registers the service provider, but verify this in the package source or README. The package is pre-1.0, so pin an exact version in composer.json while you evaluate it. Run your app's test suite and smoke-test the mds:* components before deploying.
- Which Laravel and PHP versions does Majid DS support?
- The provided context does not list exact Laravel or PHP version constraints. Check the package composer.json for laravel/framework, php, Livewire, and Flux UI requirements before installing. Because v0.4.0 is pre-1.0, confirm compatibility against your target Laravel and PHP versions rather than assuming support. If constraints are missing or too loose, test in a spike branch first.
- Do I need Flux UI Pro to use Majid DS?
- Majid DS is built on top of Flux UI, so you need Flux UI installed and working in your Laravel Livewire app. The package includes open alternatives to some Flux Pro-only components, such as command palette, composer, color picker, file upload, and timeline. However, it does not replace Flux itself, and you should verify which Flux tier and version the package expects. Check the README and composer.json for the exact Flux dependency.
- How do I enable Persian digits, separators, and Vazirmatn font in Majid DS?
- Majid DS adds Persian digits, Persian separators, and the @fa and @faNum directives, plus Vazirmatn wired into Tailwind's --font-sans. Use the @mdsFonts directive to output the font link tags, then apply the package's typography setup as shown in the docs. The components use Hugeicons by default, while heroicon names still work. Review the reference docs for the exact Blade directives and Tailwind configuration.
- How does Majid DS handle Jalali dates and Toman or Rial prices?
- Majid DS provides a dependency-free Jalali calendar through the mds:jalali-date component and @jalali directive, including relative Persian phrases like ۳ ساعت پیش. For money, it adds mds:price plus @toman and @rial directives, with a configurable default currency. This lets you render Persian-friendly dates and prices without pulling in separate Jalali or money packages. Confirm the config options and formatting behavior in the package docs before relying on them.
- What e-commerce components are included in Majid DS?
- The package includes mds:product-card, mds:quantity, mds:discount-badge, and mds:countdown for common storefront needs. It also adds mds:stepper for checkout flows, mds:rating and mds:rating.input for reviews, and mds:empty-state for empty cart or search states. These components are RTL-first, support dark mode, and follow Flux accent tokens. Use the docs to check props, slots, and Livewire binding behavior.
- Is Majid DS stable enough for production at v0.4.0?
- Treat v0.4.0 as pre-1.0 and not yet API-stable. The repository is single-maintainer, and the v0.4.0 release notes only link to a changelog with no summary, so breaking changes between v0.3.1 and v0.4.0 are not clearly documented. For production, pin an exact version, review the source diff, run the package tests, and wrap usage behind your own Blade abstraction where practical. Start in a non-production environment with a feature flag and document rollback steps.
- How should I upgrade Majid DS from v0.3.1 to v0.4.0?
- Treat the upgrade as potentially breaking because the v0.4.0 release notes do not summarize changes. Compare the GitHub diff between v0.3.1 and v0.4.0, check for removed or renamed components, directives, props, and config keys, and run the package's test suite plus your app tests. Pin the new exact version only after a spike branch passes README examples and smoke tests. Keep a Composer lock rollback path ready.
- Does Majid DS have tests, CI, and active maintenance?
- The provided assessment says test coverage and CI status are unknown, so do not assume a green pipeline. Support is community-only via GitHub issues with no SLA, and the package is maintained by a single author. Check the repository's workflows, test directory, issue response times, and release history before making it critical. If you adopt it, consider pinning versions or wrapping it behind an internal abstraction to reduce upgrade risk.