website

[![Flutter logo]](https://docs.flutter.dev)

[Flutter logo]: https://github.com/dart-lang/site-shared/blob/main/src/_assets/image/flutter/icon/64.png?raw=1

# [Flutter][] documentation and marketing websites

The [documentation site][] (`docs.flutter.dev`) and
[marketing website][] (`flutter.dev`, including the blog)
for the [Flutter framework][],
built with [Jaspr][] and hosted on [Firebase][].

[documentation site]: https://docs.flutter.dev
[marketing website]: https://flutter.dev
[Flutter framework]: https://flutter.dev
[Jaspr]: https://jaspr.site
[Firebase]: https://firebase.google.com/

[Build Status]: https://github.com/flutter/website/workflows/build/badge.svg
[Flutter]: https://flutter.dev
[Repo on GitHub Actions]: https://github.com/flutter/website/actions?query=workflow%3Abuild+branch%3Amain

## Issues, bugs, and requests

We welcome contributions and feedback on our website.
Please file a request in our
[issue tracker](https://github.com/flutter/website/issues/new/choose)
or create a [pull request](https://github.com/flutter/website/pulls).
For simple changes (such as tweaking some text),
it's easiest to make changes using the GitHub UI.

If you have an issue with the
API docs on [api.flutter.dev](https://api.flutter.dev),
please file them on
the [`flutter/flutter`](https://github.com/flutter/flutter/issues) repo,
not on this (`flutter/website`) repo.
The API docs are embedded in Flutter's source code,
so the engineering team handles them.


## Before you submit a PR

We love it when the community gets involved in improving our docs!
Here are a few things to keep in mind before you submit a PR:

- When triaging issues,
  we sometimes label an issue with the tag **PRs welcome**.
  However, we welcome PRs on other issues as well—
  it doesn't have to be tagged with that label.
- Please don't run our docs through Grammarly (or a similar tool)
  and submit those changes as a PR.
- We follow the [Google Developer Documentation Style Guidelines][]—
  for example, avoid "i.e." or "e.g.",
  avoid writing in the first person,
  and avoid the future tense.
  You can start with the
  [style guide highlights](https://developers.google.com/style/highlights)
  or the [word list](https://developers.google.com/style/word-list),
  or use the search bar at the top of every style guide page.

> We truly thank you for your willingness and helpfulness
> in keeping the website docs up to date!

[Google Developer Documentation Style Guidelines]: https://developers.google.com/style


## Contributing

To update this site, fork the repo, make your changes,
and generate a pull request.
For small, contained changes (such as style and typo fixes),
you probably don't need to build this site.
Often you can make changes using the GitHub UI.
If needed, we can stage the changes automatically in your pull request.

If your change involves code samples, adds/removes pages, or affects navigation,
please build and test your work before submitting.

If you want or nee