Flutter and Dart Unify Web Presence: All Official Sites Now Built with Jaspr Framework

Breaking: Flutter Team Completes Major Web Infrastructure Overhaul

In a significant shift, the Flutter team has revealed that all three official websites—dart.dev, flutter.dev, and docs.flutter.dev—are now fully powered by Jaspr, an open-source Dart web framework. The move eliminates a fragmented mix of Node.js and Python tools, replacing them with a single Dart-based stack.

What this means for developers: Contributors now only need Dart expertise to modify any part of the site. No more switching between JavaScript tooling for one site and Python for another.

A Fragmented Past

Previously, the documentation sites ran on Eleventy (Node.js), while flutter.dev used Wagtail (Python/Django). This created a high barrier for team members and community contributors. A Flutter team spokesperson explained: “Our old setup required additional experience and tooling outside the Dart ecosystem. That made code sharing nearly impossible and increased setup friction for everyone.”

Adding interactive elements like code samples or quizzes meant writing custom imperative DOM logic—a slow, error-prone process.

Why Jaspr?

Jaspr supports client-side rendering, server-side rendering, and static site generation. Its component model feels natural to Flutter developers, easing the transition. The framework is fully open-source and written in Dart, aligning perfectly with the team’s long-term vision.

“We wanted a single, unified stack built on the language and tools our team and community already know,” said a lead engineer involved in the migration.

Background: The Fragmentation Problem

The migration addresses years of technical debt. Fragmenting the sites across different ecosystems limited code reuse and slowed development. Interactive components required separate implementations for each site, leading to inconsistencies. The Jaspr rewrite consolidates all logic into one Dart codebase.

Notable code example from the new setup—a FeatureCard component written in Jaspr looks nearly identical to a Flutter widget:

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

This familiarity means 80% of Flutter developers can immediately contribute to the websites.

What This Means for the Community

The unified stack lowers the barrier for contributions—only Dart knowledge is required. It also paves the way for richer interactivity, such as live code samples, tutorials with quizzes, and dynamic documentation. The team expects faster iteration on features and improved consistency across all sites.

Furthermore, Jaspr’s static site generation capabilities ensure the sites remain fast and SEO-friendly. In the long term, the team may open up more of the website’s interactive components as reusable packages.

Next Steps and Impact

Developers can explore the new codebase on the Jaspr website and in the Flutter GitHub repositories. The migration is already live, and the team encourages community feedback. “This is a foundational change that will make maintaining and improving our web presence much simpler,” noted a spokesperson.

For those curious about building web experiences with Dart beyond standard Flutter web apps, this migration serves as a real-world case study. The team plans to share more technical deep-dives in the coming weeks.

Key Takeaways

• Unified stack: All official Flutter and Dart sites now run on Jaspr (Dart).
• Lower contribution barrier: Only Dart knowledge needed.
• Familiar syntax: Jaspr components mirror Flutter widgets.
• Future-proof: Enables richer interactive content.

Learn more about Jaspr and see the updated sites.