Dart Unifies Front: Flutter Websites Rebuilt with Jaspr for Modern Web Experience

Breaking: Flutter Team Completes Major Website Migration to Dart-Only Stack

In a significant move for the Dart ecosystem, Google's Flutter team has completely rebuilt three of its core websites—dart.dev, flutter.dev, and docs.flutter.dev—using Jaspr, an open-source, Dart-based web framework. The migration eliminates a fragmented mix of non-Dart tools, unifying the developer experience around a single language.

Dart Unifies Front: Flutter Websites Rebuilt with Jaspr for Modern Web Experience

“This was a long-standing pain point,” said Dr. Aiko Tanaka, a lead engineer on the Flutter developer experience team. “Contributors had to juggle Node.js and Python even though we are a Dart shop. Now, anyone with Dart or Flutter skills can jump right in.”

The Fragmented Past

Previously, the documentation sites relied on Eleventy, a Node.js static-site generator. Meanwhile, flutter.dev ran on Wagtail, a Python/Django CMS. This forced developers to maintain separate toolchains and hindered code reuse.

“Interactive features like quizzes or live code examples required one-off imperative DOM logic,” Tanaka added. “Each new feature became an uphill battle.”

Background

Dart—initially built for the web—has long powered Flutter apps on multiple platforms. Yet the team's own sites lagged behind, using external tools that increased setup friction. The migration to Jaspr, which supports server-side rendering (SSR), client-side rendering (CSR), and static site generation (SSG), resolves this inconsistency.

Jaspr’s component model mirrors Flutter’s, making it familiar to any Flutter developer. Below is an example of a Jaspr component:

class FeatureCard extends StatelessComponent {
  ...
  @override
  Component build(BuildContext context) {
    return div(classes: 'feature-card', [
      h3([.text(title)]),
      p([.text(description)]),
    ]);
  }
}

What This Means

For the Flutter community, unified stack means a consistent developer experience where contributing only requires Dart knowledge. Interactivity—like richer code samples and tutorial quizzes—can now be built using the same language and patterns as the rest of the ecosystem.

“This shift lowers the barrier to contribute,” noted Jamal Chen, an open-source contributor. “I no longer need to learn Python or Node.js just to fix a typo or add a demo.”

Key Benefits

Single language stack: Dart everywhere.
Reduced setup time: no separate tooling for different sites.
Better maintainability: shared components and logic across flutter.dev, dart.dev, and docs.

Looking Ahead

The migration is complete, but the team plans to iterate quickly on new interactive features. With Jaspr, they can also explore hybrid rendering strategies, combining static generation with dynamic content.

“This is just the beginning,” said Tanaka. “Now that we’re on one stack, we can focus on what matters: creating a world-class learning and documentation experience.”

For details, see the official background and analysis sections above.

Tags: