Flutter and Dart Websites Unified Under One Framework: Jaspr Migration Complete

Breaking: Dart and Flutter Official Sites Now Powered Entirely by Jaspr

The Flutter team has completed a comprehensive migration of three primary websites—dart.dev, flutter.dev, and docs.flutter.dev—to Jaspr, an open-source Dart-based web framework. The move eliminates a fragmented stack that previously relied on Node.js (Eleventy) and Python/Django (Wagtail), unifying development under a single language.

Flutter and Dart Websites Unified Under One Framework: Jaspr Migration Complete

According to a Flutter engineering lead, “This is a foundational change. Contributors now only need Dart knowledge to work on any of our sites.” The migration aims to reduce setup friction and enable richer interactive features like code samples and quizzes.

Background

Before the migration, the documentation sites ran on Eleventy, a static-site generator built on Node.js, while flutter.dev used Wagtail, a Python/Django CMS. This fragmentation required contributors to master multiple toolchains and limited code sharing.

“The old setup worked, but adding interactivity was an uphill battle—each new component needed custom imperative DOM logic. We knew we needed a consistent stack built on Dart,” said a senior engineer on the web infrastructure team.

What This Means

For the Dart and Flutter community, the switch to Jaspr means a unified developer experience. Anyone with Flutter skills can immediately contribute to website features, as Jaspr’s component model closely mirrors Flutter widgets.

“If you can write a Flutter widget, you can write a Jaspr component,” the team explained. “This dramatically lowers the barrier for community contributions.” The unified stack also simplifies maintenance and accelerates the addition of interactive content across all three sites.

Why Jaspr?

Jaspr supports client-side rendering, server-side rendering, and static site generation—all within Dart. Its component structure was designed to feel familiar to Flutter developers while remaining compatible with the standard DOM model.

A code example shared by the team shows a FeatureCard component written in Dart with Jaspr, closely resembling a Flutter StatelessWidget. This direct skill transfer is expected to boost community involvement and reduce onboarding time for new contributors.

“We wanted a single stack built on the language our team and community already use. Jaspr delivered that seamlessly.” – Flutter Infrastructure Lead

Next Steps and Broader Impact

The migration is now live. The Flutter team encourages developers to explore Jaspr for building web experiences with Dart beyond standard Flutter web apps.

The change also sets a precedent for other Dart-based projects: a fully unified web presence is now achievable without leaving the Dart ecosystem. As the team noted, “This is just the beginning of more interactive, community-driven documentation and marketing websites.”

Related Resources

How the migration eliminated Node.js and Python dependencies
What the Jaspr switch means for Flutter developers

Tags: