Open-source project
flutter/website avatar
flutter/website

flutter/website: the Jaspr site behind docs.flutter.dev

Flutter documentation web site

3,144 stars3,508 forksDartNOASSERTION

At a glance

What is it?
The Flutter documentation and marketing site is a Dart project built with Jaspr and deployed on Firebase. Here is what it does, how to serve it locally, and where it stops being the right repo for your change.
Who is it for?
Adopt flutter/website if you are fixing prose, code samples or navigation on docs.flutter.dev, and you can run Flutter stable plus dart pub get before you push. Do not open a PR here for API reference pages on api.flutter.dev; the README sends those to flutter/flutter because the API docs live in Flutter's source.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly Dart, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • flutter/website3,144 ★ · +23
Star history
Repository2026-09-242026-11-15
flutter/website3.1k3.1k

23 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What flutter/website actually publishes

This repository is not a library you add to a pubspec. It is the source of two public websites: the documentation site at docs.flutter.dev and the marketing site at flutter.dev, which includes the blog. Both are built with Jaspr, a Dart web framework, and hosted on Firebase, according to the README.

The audience is narrow and specific. It is for people who want to change what Flutter's official documentation says, how its code samples behave, or how the marketing pages read. The README frames contributions around an issue tracker and pull requests, and notes that small text tweaks can be done entirely through the GitHub UI without building anything. That is the fastest path for a typo.

The boundary matters more than the scope. If your problem is with the API reference on api.flutter.dev, this is the wrong repository. The README is explicit that those pages are embedded in Flutter's source code, so the engineering team handles them in flutter/flutter. A PR here will not fix an API doc page.

The dash_site tool and the two-site switch

The mechanism is a single Dart CLI that lives in the repository and is invoked as dart run dash_site. It is the entry point for serving, building and validating the site, and the README treats it as the thing to run first, with dart run dash_site --help, to learn the available commands.

The design decision worth noticing is that one repository, one tool and one command set drive two different sites. The documentation site is the default target. Passing --site=www redirects any command to the marketing site and blog. That flag is not a build variant buried in config; it is part of the everyday command line, which means a contributor working on the blog and a contributor working on the docs use the same checkout but different invocations.

Content lives under sites/ and examples/ in the repository layout, with tooling under tool/ and packages/. The README ties validation to exactly those directories: if you change code in /examples, /sites or /tool, you are expected to run the check-all command before submitting. That is a reasonable split. Prose edits do not need a full build, but anything that touches a sample or navigation does.

Serving docs.flutter.dev locally

The prerequisites are the latest stable release of Flutter, which brings Dart with it. The README points to the Install Flutter and Upgrading Flutter pages on docs.flutter.dev, and suggests verifying the toolchain before anything else. Run this from a shell and confirm the output reports a stable channel:

console
flutter --version

Next, clone the repository. The README recommends a fork under your own account if you are not a member of the Flutter organization, so that you can open a pull request from it:

bash

git clone https://github.com/flutter/website.git

From the repository root, fetch the Dart dependencies:

console
dart pub get

Then start the documentation site. The command generates and serves the site on a local port, and that port is printed to your terminal:

terminal
dart run dash_site serve

Open the printed URL in a browser. Edits to the local repo should trigger a rebuild on most changes; the README warns that if something does not update, you should exit the process and rerun the command. To work on the marketing site or blog instead, add the site flag:

terminal
dart run dash_site --site=www serve

Validation is a separate step, and it is not optional for code changes

Serving the site proves it renders. It does not prove the samples compile or that links resolve. The README splits those concerns into two checks.

The first covers documentation and example code. After committing work that touches /examples, /sites or /tool, run:

terminal
dart run dash_site check-all

If the script reports errors or warnings, the README says to address them and rerun. There is a support channel for questions: the #hackers-devrel channel on the Flutter contributors Discord.

The second check covers links. The README describes building the site locally and then running commands to verify that internal links and Markdown link references are valid. The excerpt of the README available here cuts off mid-command, so the exact link-checking invocation is not fully visible. Treat check-all as the documented starting point and confirm the link-check command in the repository's own README before relying on it.

Style rules that reject otherwise correct edits

The contribution rules are stricter than a typical docs repo, and they are the most likely reason a first pull request gets pushed back. Contributors are asked to follow the Google Developer Documentation Style Guidelines. The README names concrete consequences: avoid "i.e." and "e.g.", avoid writing in the first person, and avoid the future tense.

There is also an explicit prohibition on running the docs through Grammarly or a similar tool and submitting those changes. This is a real limitation on workflow, not a suggestion. A grammar pass that rewrites voice and tense across a page will conflict with the house style, so a well-intentioned cleanup PR can be rejected on policy rather than on accuracy.

The README also notes that issues labeled "PRs welcome" are not the only issues open to contributions. The label is a triage signal, not a gate. That said, a contributor who has not read the style guide is likely to spend more time in review than on the edit itself.

Where this repository is the wrong tool

Three cases stand out.

API reference documentation on api.flutter.dev is out of scope here. The README redirects those issues to flutter/flutter, because the API docs are generated from Flutter's source. Opening an issue or PR in flutter/website for an API page wastes a review cycle.

A change that only alters a sentence does not need the local build at all. The README says small, contained changes such as style and typo fixes can be made through the GitHub UI, and that changes can be staged automatically in the pull request when needed. Setting up Flutter, running dart pub get and serving the site for a one-word fix is more process than the task requires.

The repository also has no release artifacts. It has no published releases, and it is a website source tree rather than a versioned package. If you are looking for a dependency to install, this is not one. The thing you consume is the published site, not the code.

Alternatives and the difference in approach

The obvious alternative for Flutter API questions is the flutter/flutter repository. The split is by content type: flutter/website holds the hand-written documentation and marketing pages, while flutter/flutter holds the framework source and the API docs embedded in it. If your change is to a dartdoc comment, it belongs in flutter/flutter; if it is to a tutorial page, it belongs here.

The other alternative is not a repository at all. For a typo or a wording fix, editing directly in the GitHub UI produces the same result as a local checkout, and the README endorses that route for small changes. The difference is that you give up the edit-refresh loop and the ability to run check-all before submitting. For a change that touches a code sample or navigation, that trade is bad; for a comma, it is fine.

Maintenance, licence and what to verify before contributing

The repository is not archived, and the last push was on 2026-09-23. That is recent activity, and the project is backed by the Flutter organization with a CODEOWNERS file and a documented review process. There are no releases to track, so upgrade cost is not a version-bump question. It is a toolchain question: you keep a stable Flutter SDK current, run dart pub get when dependencies change, and rerun dart run dash_site check-all when you touch examples or tooling.

The licence is recorded as NOASSERTION in the repository metadata. The repository does contain a LICENSE file at the top level, but the metadata does not resolve it to a standard identifier. Before you reuse content or code from this repository outside a contribution to the site, read that file directly; the metadata alone does not tell you the terms.

The first thing to verify is which site your change targets, since the same checkout serves both docs.flutter.dev and flutter.dev depending on the --site flag. The second is whether your edit belongs in this repository at all, given the api.flutter.dev boundary. The third is the style guide, because first-person and future-tense phrasing will be flagged in review regardless of how clear the sentence is.

Editorial conclusion

Adopt flutter/website if you are fixing prose, code samples or navigation on docs.flutter.dev, and you can run Flutter stable plus dart pub get before you push. Do not open a PR here for API reference pages on api.flutter.dev; the README sends those to flutter/flutter because the API docs live in Flutter's source. Before you submit, run dart run dash_site check-all and confirm your branch targets the right site, because the same repository serves both docs.flutter.dev and flutter.dev through the --site flag.

Frequently asked questions

How do I install flutter/website and serve it locally?

Install the latest stable release of Flutter, clone the repository, run dart pub get from the root, then run dart run dash_site serve. The site is generated and served on a local port that is printed to your terminal.

How do I serve the flutter.dev marketing site and blog instead of the docs?

Pass the site flag to any dash_site command. The README gives dart run dash_site --site=www serve for the marketing site and blog, and notes that the flag works with other commands too.

Do I need to build flutter/website for a small text change?

No. The README says small, contained changes such as style and typo fixes can be made using the GitHub UI, and that changes can be staged automatically in the pull request. Build and test when your change involves code samples, adds or removes pages, or affects navigation.

Where do I report a problem with the API docs on api.flutter.dev?

File it on the flutter/flutter repository, not on flutter/website. The README states that the API docs are embedded in Flutter's source code, so the engineering team handles them there.

Official sources

  1. flutter/website on GitHub
  2. Issues
  3. Project website
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/flutter-website.svg)](https://hysenlabs.com/projects/flutter-website)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/flutter-website.svg)](https://hysenlabs.com/projects/flutter-website)

Was this useful?