Skip to content

docs: getting started documentation for web FirebaseUI v7#1340

Merged
jhuleatt merged 13 commits into
mainfrom
getting-started-doc
Jun 26, 2026
Merged

docs: getting started documentation for web FirebaseUI v7#1340
jhuleatt merged 13 commits into
mainfrom
getting-started-doc

Conversation

@russellwheatley

Copy link
Copy Markdown
Member

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request adds a comprehensive getting started guide for the latest FirebaseUI for Web library. It provides developers with step-by-step instructions on how to integrate FirebaseUI into their web applications, covering installation, initialization, authentication method setup, and UI customization for React, Shadcn, and Angular platforms. The guide also highlights key differences from the previous FirebaseUI version and offers migration guidance.

Highlights

  • Getting Started Guide: This PR introduces a new 'Getting Started' document for the latest FirebaseUI web library, mirroring the structure of the previous version.
  • Modernization: The new FirebaseUI for Web features a complete rewrite with a modern modular architecture, offering benefits like modular SDK support, composable UI elements, and support for React, Shadcn, and Angular.
  • Configuration: The guide details how to initialize FirebaseUI with the new initializeUI(...) method, set up sign-in methods, include styles, and configure behaviors for OAuth flows, Google One Tap, and anonymous user upgrades.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a comprehensive "Getting Started" guide that mirrors the structure of the classic FirebaseUI documentation. The guide is well-written and covers installation and usage for React, Shadcn, and Angular, along with key features like authentication methods, UI customization, and behaviors. I've identified a couple of minor inconsistencies in the documentation that should be addressed to ensure clarity for developers. My detailed feedback is in the comments below.

Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
@russellwheatley russellwheatley marked this pull request as ready for review March 24, 2026 09:04
@russellwheatley russellwheatley changed the title docs: getting started documentation docs: getting started documentation for web FirebaseUI v7 Mar 24, 2026
Comment thread GETTING_STARTED.md Outdated
@russellwheatley

Copy link
Copy Markdown
Member Author

CI failure is addressed in this PR: #1345

@russellwheatley

Copy link
Copy Markdown
Member Author

@jhuleatt - if you want to take a pass at this, I'd be grateful 🙏

Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
@russellwheatley russellwheatley requested a review from jhuleatt April 9, 2026 11:26

@jhuleatt jhuleatt left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorporate client review changes including React-first platform ordering,
updated intro and sign-out wording, and streamlined translations section.
@mikehardy

This comment was marked as resolved.

@mikehardy mikehardy requested a review from dackers86 June 16, 2026 00:36
Comment thread GETTING_STARTED.md
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated
Comment thread GETTING_STARTED.md Outdated

@mikehardy mikehardy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry about the lack of fidelity on that hunk - thanks for the catch @dackers86 - very much appreciated.

Point readers to CSS variable overrides and the theming documentation
after the include styles section.
@mikehardy mikehardy force-pushed the getting-started-doc branch from 63a14ca to 220186f Compare June 25, 2026 20:23
@jhuleatt

Copy link
Copy Markdown
Collaborator

Thanks all!

@jhuleatt jhuleatt merged commit 3f1c4ac into main Jun 26, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants