Skip to content

feat: faq and seal calculation changes - #194

Open
emmambd wants to merge 3 commits into
mainfrom
seal-copy-change
Open

feat: faq and seal calculation changes#194
emmambd wants to merge 3 commits into
mainfrom
seal-copy-change

Conversation

@emmambd

@emmambd emmambd commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Summary:

  • Added 2 new FAQ questions to the Seal of Reliability description page
    How It Is Calculated page
  • Fixed minor issues with the Official criterion on the
  • Modified and clarified Stable and Available criteria

Expected behavior:

Explain and/or show screenshots for how you expect the pull request to work in your testing (in case other devices exhibit different behavior).

Testing tips:

Go to /seal-of-reliability and /seal-of-reliability/how-it-is-calculated in Vercel

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Run the unit tests with yarn test to make sure you didn't break anything
  • Add or update any needed documentation to the repo
  • Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
  • Linked all relevant issues
  • Include screenshot(s) showing how this pull request works and fixes the issue(s)

@welcome

welcome Bot commented Sep 9, 2026

Copy link
Copy Markdown

Thanks for opening this pull request! You're awesome. We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix. Examples of titles with semantic prefixes:

  • fix: Bug with ssl network connections + Java module permissions.
  • feat: Initial support for multiple @PrimaryKey annotations.
  • docs: update RELEASE.md with new process
    To get this PR to the finish line, please do the following:
  • Include tests when adding/changing behavior
  • Include screenshots

@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
mobilitydatabase-web Ready Ready Preview Sep 10, 2026 6:10pm UTC

Request Review

@emmambd
emmambd marked this pull request as draft September 9, 2026 18:38
@emmambd emmambd linked an issue Sep 9, 2026 that may be closed by this pull request
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

*Lighthouse ran on https://mobilitydatabase-9fs8mnfo9-mobility-data.vercel.app/ * (Desktop)
⚡️ HTML Report Lighthouse report for the changes in this PR:

Performance Accessibility Best Practices SEO
🟠 85 🟢 94 🟢 96 🟢 100

*Lighthouse ran on https://mobilitydatabase-9fs8mnfo9-mobility-data.vercel.app/feeds * (Desktop)
⚡️ HTML Report Lighthouse report for the changes in this PR:

Performance Accessibility Best Practices SEO
🟠 86 🟠 88 🟢 96 🟢 100

*Lighthouse ran on https://mobilitydatabase-9fs8mnfo9-mobility-data.vercel.app/feeds/gtfs/mdb-2126 * (Desktop)
⚡️ HTML Report Lighthouse report for the changes in this PR:

Performance Accessibility Best Practices SEO
🔴 34 🟢 94 🟢 96 🟢 100

*Lighthouse ran on https://mobilitydatabase-9fs8mnfo9-mobility-data.vercel.app/feeds/gtfs_rt/mdb-2585 * (Desktop)
⚡️ HTML Report Lighthouse report for the changes in this PR:

Performance Accessibility Best Practices SEO
🟠 85 🟠 84 🟢 96 🟢 100

*Lighthouse ran on https://mobilitydatabase-9fs8mnfo9-mobility-data.vercel.app/feeds/gbfs/gbfs-flamingo_porirua * (Desktop)
⚡️ HTML Report Lighthouse report for the changes in this PR:

Performance Accessibility Best Practices SEO
🟠 81 🟢 94 🟢 96 🟢 100

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.

Pilot launch step: Copy updates to the Seal of Reliability pages

2 participants