Merge branch 'main' into feat-ui-translations-20240814

web-app/public/locales/en/feeds.json

@@ -1,17 +1,17 @@
 {
   "feeds": "Feeds",
-  "dataType": "Data Type",
+  "dataType": "Data Format",
   "transitProvider": "Transit Provider",
   "location": "Location",
-  "feedDescription": "Feed Description",
+  "feedDescription": "Description",
   "searchFor": "Search For",
   "resultsFor": "{{startResult}}-{{endResult}} of {{totalResults}} results",
   "deprecated": "Deprecated",
   "searchPlaceholder": "Transit provider, feed name, or location",
   "noResults": "We're sorry, we found no search results for “{{activeSearch}}”.",
   "searchSuggestions": "Search suggestions: ",
   "searchTips": {
-    "twoDigit": "Use a two digit code to search for country, e.g “FR” for France",
+    "twoDigit": "Use the full English name of a location e.g \"France\" or \"New York City\"",
     "fullName": "Include the full name for transit provider, e.g “Toronto Transit Commission” instead of “TTC”",
     "checkSpelling": "Double check the spelling"
   },

web-app/src/app/screens/FAQ.tsx

@@ -35,11 +35,39 @@ export default function FAQ(): React.ReactElement {
             Why would I use the Mobility Database?
           </Typography>
           <Typography className='answer'>
-            The Mobility Database catalogs has over 100 feeds that were
-            inaccurate on TransitFeeds, and over 150 new feeds. It&apos;s a more
-            accurate and comprehensive resource for ensuring your data is
-            discoverable and for scraping the data you need. The community
-            regularly adds and updates feeds using Github.
+            The Mobility Database has over 100 feeds that were inaccurate on
+            TransitFeeds, and over 250 new feeds. It&apos;s a more accurate and
+            comprehensive resource for ensuring your data is discoverable and
+            for scraping the data you need. The community regularly adds and
+            updates feeds using Github. The Mobility Database integrates with{' '}
+            <a
+              href='https://gtfs-validator.mobilitydata.org/'
+              target='_blank'
+              rel='noreferrer'
+            >
+              the Canonical GTFS Schedule Validator
+            </a>{' '}
+            to display data quality information about each feed.
+          </Typography>
+          <Typography className='question'>
+            How do I use the Mobility Database?
+          </Typography>
+          <Typography className='answer'>
+            There are 3 ways to use the Mobility Database:
+            <br />
+            <br />
+            1. The feed search on the website, where you can discover feeds and
+            see details on their bounding box, data quality, and historical
+            data. 2. The API, where you can pull feed information to display in
+            your own application or for research analysis 3. The{' '}
+            <a href='https://bit.ly/catalogs-csv'>
+              spreadsheet export available here
+            </a>
+            . You can find{' '}
+            <a href='https://github.com/MobilityData/mobility-database-catalogs?tab=readme-ov-file#schemas'>
+              the GTFS Schedule and Realtime schemas for the spreadsheet here
+            </a>
+            .
           </Typography>
           <Typography className='question'>
             Why are you making this change?
@@ -66,20 +94,16 @@ export default function FAQ(): React.ReactElement {
             longer term solutions for the architecture that require more
             community investment.
           </Typography>
-          <Typography className='question'>
-            What about the TransitFeeds user interface?
-          </Typography>
+          <Typography className='question'>What about TransitFeeds?</Typography>
           <Typography className='answer'>
-            We plan to develop a new user interface as part of the Mobility
-            Database by summer 2024, since this is critical for making data
-            discoverable and fostering collaboration on data quality
-            improvements.
+            TransitFeeds.com is still available to access historical data before
+            February 2024 and see feed visualizations. It will be deprecated
+            once both these features are available on the Mobility Database. We
+            commit to giving 6 months notice once the decision is finalized.
             <br /> <br />
-            In order to ensure the community has access to more up-to-date data
-            as soon as possible, we&apos;ve focused on providing a catalog of
-            data without an interface as a first step. How quickly we scale the
-            architecture to build the user interface depends on how much
-            engagement and contribution we get from the community in this phase.
+            How quickly we scale the architecture to add these features depends
+            on how much engagement and contribution we get from the community in
+            this phase.
           </Typography>
           <Typography className='question'>
             What about the TransitFeeds API?
@@ -100,15 +124,8 @@ export default function FAQ(): React.ReactElement {
           </Typography>
           <Typography className='question'>What’s coming next?</Typography>
           <Typography className='answer'>
-            The MobilityData team is working to add validation info from the{' '}
-            <a
-              href='https://gtfs-validator.mobilitydata.org/'
-              target='_blank'
-              rel='noreferrer'
-            >
-              Canonical GTFS Schedule Validator
-            </a>{' '}
-            for each feed, and create a user interface.
+            The MobilityData team is working to add historical data before 2024
+            and route and stop visualizations to the Mobility Database.
             <br /> <br />
             <a
               href='https://mobilitydata.org/roadmaps/'
@@ -127,9 +144,9 @@ export default function FAQ(): React.ReactElement {
             How often do you check for feed updates?
           </Typography>
           <Typography className='answer'>
-            The Mobility Database checks for feed updates every week using the
-            producer&apos;s URL. We store the new feed version if we detect a
-            change.
+            The Mobility Database checks for feed updates twice a week using the
+            producer&apos;s URL, on Mondays and Thursdays. We store the new feed
+            version if we detect a change.
           </Typography>
         </Box>
       </Box>

web-app/src/app/screens/Home.tsx

@@ -101,7 +101,7 @@ function Component(): React.ReactElement {
           sx={{ textAlign: 'center', color: 'black', fontWeight: 700, mt: 4 }}
         >
           Currently serving over <span style={{ color: '#3859FA' }}>2000</span>{' '}
-          GTFS feeds from <span style={{ color: '#3859FA' }}>70</span>{' '}
+          transit data feeds from <span style={{ color: '#3859FA' }}>70</span>{' '}
           countries.
         </Typography>
         <Box
@@ -217,9 +217,13 @@ function Component(): React.ReactElement {
               mt: 5,
             }}
           >
-            The Mobility Database catalogs is a repository of 2000+ mobility
-            feeds across the world. It has over 150 updated feeds previously
-            unavailable on TransitFeeds (OpenMobilityData).
+            The Mobility Database is a directory of 2000+ mobility feeds across
+            the world. It has over 250 updated feeds previously unavailable on
+            TransitFeeds (OpenMobilityData) and shares data quality reports from{' '}
+            <a href='https://gtfs-validator.mobilitydata.org/'>
+              the Canonical GTFS Schedule Validator
+            </a>
+            .
             <br />
             <br />
             We’re in the first phase of building a sustainable, central hub for