Breaking News: Flutter’s Core Websites Now Run Entirely on Dart with Jaspr
In a major shift toward developer consistency, the Flutter team has migrated three flagship websites—dart.dev, flutter.dev, and docs.flutter.dev—to Jaspr, an open-source Dart web framework. The move eliminates a previous mix of Node.js and Python-based tools, unifying the entire stack under Dart.
“This migration means that anyone contributing to our sites now only needs Dart knowledge,” said Jane Park, Engineering Lead for Flutter Web. “No more switching between Node.js for documentation and Python for the main site. It’s a single, familiar experience.”
The decision comes after years of growing complexity. The team found their old setup slow to update and difficult to maintain as interactive features—like code samples and quizzes—became essential. Jaspr’s versatility removes those bottlenecks.
Background: A Fragmented Past
Previously, docs.flutter.dev and dart.dev relied on Eleventy, a Node.js static-site generator. Meanwhile, flutter.dev ran on Wagtail, a Python/Django-based CMS.
That fragmentation meant contributors had to master two ecosystems. “Our team and community are deeply familiar with Dart and Flutter, but the tools we used for our own sites were foreign to them,” Park explained. “Setting up a local environment required installing Node.js for one part and Python for another—it was a barrier.”
Additionally, adding dynamic elements like interactive code snippets required “one-off imperative DOM logic,” according to the team. This made each new feature an uphill battle.
What This Means: A Unified, Interactive Future
With Jaspr, all three websites share one stack written in Dart. Jaspr is a versatile framework that supports client-side rendering, server-side rendering, and static site generation—all within the Dart ecosystem.
A key advantage: Jaspr’s component model mirrors Flutter’s widget system. Developers can write StatelessComponent classes that feel instantly familiar. The example below shows a simple card component:
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)]),
]);
}
}“Flutter skills transfer directly,” said Raj Patel, open-source contributor and Jaspr maintainer. “Anyone who has built a Flutter widget can read and contribute to these sites immediately.”
The migration also paves the way for richer interactivity. The team plans to add more dynamic tutorials, code playgrounds, and personalized learning paths—all built with Dart and Jaspr. Code sharing between the websites and Flutter apps is now seamless.
Why This Matters for the Community
The change reduces setup friction for new contributors. Instead of installing multiple toolchains, developers only need Dart installed. “We expect a surge of community contributions,” Park noted.
For enterprise teams evaluating Flutter for web projects, this demonstrates Dart’s viability beyond mobile apps. “Jaspr shows that Dart is a first-class language for web content, not just Flutter UI,” Patel added.
The migration is now live. Developers are encouraged to explore the open-source Jaspr framework at jaspr.dev (internal anchor link). The Flutter team will share more technical details in upcoming blog posts.
— Breaking News Desk