Skip to main content

Recommended Tech Stack

About these recommendations​

This section documents Aliz's recommended tech stack for frontend projects. These are sensible defaults — not mandates. Teams may deviate when there's a good reason, but starting here means less time debating tooling and more time shipping.

Recommendations are reviewed periodically by the Web Hub maintainers. Each page is a short introduction with rationale and links to official docs — not a deep tutorial.

When to follow this stack​

  • New greenfield projects at Aliz
  • When choosing between equivalent options and you need a tiebreaker
  • When onboarding new team members and you want a consistent baseline

When to deviate​

  • Legacy projects already using a different stack — don't rewrite for the sake of it
  • Specific client requirements that dictate other choices
  • Prototypes, throwaway scripts, or one-off experiments where setup cost matters more than long-term maintainability

What's covered​

Core​

Styling & UI​

  • Tailwind CSS — utility-first CSS framework
  • shadcn/ui — component collection (Radix + Tailwind)
  • MUI — Material UI component library

State & Data​

Build & Dev​

  • npm — package manager
  • Vite — build tool and dev server
  • Vitest — testing framework
  • Playwright — end-to-end testing

Data Visualization​

  • Recharts — React charting library (default for dashboards)
  • Apache ECharts — enterprise-grade visualization (maps, 3D, big data)

Security​

  • DOMPurify — XSS sanitizer for HTML content

Documentation Frameworks​

  • Docusaurus — React-based documentation site generator (powers this Web Hub)
  • Astro Starlight — zero-JS documentation framework built on Astro
tip

This section will grow over time — contributions welcome. If your team has settled on a tool that works well, open a PR.

tip

For guidance on using AI tools and agents in your development workflow, see AI-Assisted Development.