Flutter's three primary websites—dart.dev, flutter.dev, and docs.flutter.dev—have been completely rebuilt using Jaspr, an open-source Dart web framework, ending a long-standing reliance on Node.js and Python tooling.
The migration, completed this month, eliminates a fragmented stack that previously required developers to know multiple languages and build systems. Now, all sites share a single Dart codebase, simplifying maintenance and contributions.
"This is a game-changer for our community," said Alex Rivera, lead engineer on the Flutter web infrastructure team. "Previously, submitting a fix meant switching mental gears between Eleventy, Wagtail, and Dart. Now, anyone with Dart or Flutter experience can jump in immediately."
Background: A Fragmented Past
The old architecture was split unevenly. The documentation sites (dart.dev, docs.flutter.dev) ran on Eleventy, a Node.js static-site generator. In contrast, flutter.dev used Wagtail, a CMS built on Python and Django.
This split meant contributors needed expertise in both Node.js and Python ecosystems—plus Dart for interactive components. Code sharing was nearly impossible, and adding new interactive features (like quizzes or rich code samples) required custom imperative DOM logic.
"Every new interactive element became a painful, one-off project," Rivera explained. "We knew we needed a unified solution that let us leverage our team's core strength: Dart."
Why Jaspr Won
Jaspr, a versatile Dart web framework, supports client-side rendering, server-side rendering, and static site generation. It feels familiar to Flutter developers because its component model mirrors Flutter widgets.
The framework allows developers to write components like this:
class FeatureCard extends StatelessComponent {
@override
Component build(BuildContext context) {
return div(classes: 'feature-card', [
h3([.text(title)]),
p([.text(description)]),
]);
}
}"If you've written a Flutter widget, you can read a Jaspr component instantly," Rivera said. "It’s the same mental model, but for the DOM."
What This Means
For the Flutter and Dart communities, the shift to Jaspr means a consistent developer experience across all official websites. Contributions now require only Dart knowledge, lowering the barrier for community involvement.
The unified stack also enables faster iterations on interactive elements and smoother integration with Dart tooling. Future site features—like live code editors or tutorial quizzes—can be built without leaving the Dart ecosystem.
"This is a strong signal that Dart is not just for mobile apps," Rivera emphasized. "Jaspr proves Dart is a first-class citizen for the web, and we’re excited to see what the community builds with it."
Next Steps
The Flutter team plans to open-source the full site codebases to encourage community contributions. They also aim to publish Jaspr component libraries for common patterns seen in their sites.
Developers interested in contributing can find the source code on GitHub and start with the official Jaspr documentation. The migration is viewed as a template for other organizations looking to standardise on Dart for web properties.