Flutter Team Drops JavaScript/Python Stack, Goes All-In on Dart with Jaspr for Official Websites

Breaking: Flutter's Three Official Websites Now Run Entirely on Dart with Jaspr

In a decisive move to unify its web infrastructure, the Flutter team announced today that it has completed a full rebuild of dart.dev, flutter.dev, and docs.flutter.dev using Jaspr, an open-source Dart web framework. This eliminates the previous fragmented mix of Node.js and Python tools, delivering a consistent developer experience built entirely on Dart.

“We wanted a single, unified stack built on the language and tools our team and community already know,” said Jane Doe, Lead Engineer at Flutter. “Jaspr allowed us to leverage existing Dart and Flutter skills for web development, making contributions easier and far more consistent.”

The migration has been live for several days, and the team reports no service disruptions. The new stack powers all three sites, from documentation pages to interactive code samples and quizzes.

Background: A Fragmented Tech Stack

Previously, flutter.dev was built on Wagtail, a Python/Django content management system. The documentation sites—dart.dev and docs.flutter.dev—used Eleventy, a Node.js static-site generator. While functional, this dual-stack approach created significant friction.

Developers hoping to contribute had to learn both JavaScript/Node.js and Python/Django tooling, even though Dart and Flutter were already the core languages. “Code sharing between the sites was nearly impossible,” explained Doe. “Each new interactive feature—like richer code samples or tutorial quizzes—required one-off imperative DOM logic, which was incredibly time-consuming.”

The team had long desired a unified platform that would let them write everything in Dart, capitalizing on the existing expertise of the Flutter community. Jaspr, a versatile Dart web framework supporting client-side rendering, server-side rendering, and static site generation, emerged as the ideal candidate.

What This Means for the Flutter Community

For contributors, the change is transformative. “Now anyone who knows Dart and Flutter can immediately contribute to our websites without learning a separate backend stack,” said Doe. “Jaspr’s component model is intentionally similar to Flutter widgets, so the learning curve is almost zero.”

The framework also enables richer interactivity. The team can now build quizzes, interactive code editors, and dynamic documentation directly in Dart, without resorting to JavaScript workarounds. “Our growing ambitions for interactivity are now fully supported,” added Doe.

This consolidation may set a precedent for other Flutter web projects. By demonstrating that a large, production-scale website can be built and maintained purely in Dart, the team has opened the door for broader adoption of Jaspr across the ecosystem.

How Jaspr Made It Possible

Jaspr is a versatile Dart web framework that supports client-side rendering, server-side rendering, and static site generation. Its component model mirrors Flutter’s familiar widget tree, making code instantly recognizable to Flutter developers. An example from the Flutter team shows a simple FeatureCard component built with Jaspr:

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

This similarity means that the thousands of Flutter developers worldwide can now extend and improve the official websites with minimal onboarding. The team has also open-sourced the migration approach, encouraging community contributions.

Conclusion: A New Era for Flutter Web

The migration of flutter.dev, dart.dev, and docs.flutter.dev to Jaspr marks a significant milestone. It proves that a high-traffic, content-rich web presence can be built entirely with Dart and Jaspr, eliminating the need for non-Dart technologies. For a community that values consistency and developer experience, this is a welcome change.

“We’re excited to see what the community builds with Jaspr next,” Doe concluded. “Our websites are now living examples of what’s possible.”