This directory contains the source of the Flutter documentation on https://firebase.google.com/docs/.

We welcome your corrections and improvements! If you're interested in contributing, see CONTRIBUTING.md for general guidelines.

This file has some information on how our documentation is organized and some non-standard extensions we use.

Only the code snippets are on GitHub. You can find them in the firebase/snippets-flutter repository.

There are two kinds of source file for our docs:

• Standalone files map one-to-one to a single page on firebase.google.com. These files are mostly-standard Markdown with filenames that correspond with the URL at which they're eventually published.

  For example, the file read-and-write.md is published to https://firebase.google.com/docs/database/flutter/read-and-write.

  Standalone pages must have filenames that don't begin with an underscore (_).

• Page fragments are included in other pages. We use page fragments either to include common text in multiple pages or to help organize large pages. Like standalone files, page fragments are also mostly-standard Markdown, but their filenames often don't correspond with the URL at which they're eventually published.

  For example, the file _deobfuscated.md is published to https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports?platform=flutter.

  Page fragments almost always have filenames that begin with an underscore (_).

Probably not useful to you as a contributor, but documented FYI.

We use double angle brackets to include content from another file:

<<path/to/file>>

Note that the path is based on our internal directory structure, and not the layout on GitHub. Also note that we sometimes use this to include non-Flutter related content that's not on GitHub.

Probably not useful to you as a contributor, but documented FYI.

Every standalone page begins with the following header:

Project: /docs/_project.yaml
Book: /docs/_book.yaml

These are non-standard metadata declarations used by our internal publishing system. There's nothing you can really do with this, but it has to be on every standalone page.

Code snippets are included from standalone Dart files, which helps facilitate automated testing. The following custom Jinja tag includes a code snippet into a file:

{% includecode github_path="organization/repository/path/to/file" region_tag="tag_name" %}

For example, the file firestore.dart in the firebase/snippets-flutter repository contains a passage like this:

void addData_addADocument() {
    // [START add_data_add_a_document]
    db.collection("cities").doc("new-city-id").set({"name": "Chicago"});
    // [END add_data_add_a_document]
}

To include the line between the START and END tags in a page, do the following:

{% includecode
   github_path="firebase/snippets-flutter/packages/firebase_snippets_app/lib/snippets/firestore.dart"
   region_tag="add_data_add_a_document"
   adjust_indentation="auto" %}

To update a snippet, submit a PR to the snippets-flutter repo.