Merge branch 'main' into feat-update-contact-email-address-2025-09-02

Author: fredericsimard

.github/workflows/lint.yml

@@ -2,10 +2,15 @@ name: Lint and style checks
 
 on:
   workflow_dispatch:
-  push:
-    branches: [ main ]
-  pull_request:
-    branches: [ main ]
+# Disabled the other triggers do to part of workflow is not working, will investigate later:
+#      Run pre-commit/[email protected]
+#      install pre-commit
+#      Error: getCacheEntry failed: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0yfa6aAAAAAAwdZzfWtlpQ7MU6zq78uD6QkwyQUEyMDMwMTA1MDUxAEVkZ2U=
+#
+#  push:
+#    branches: [ main ]
+#  pull_request:
+#    branches: [ main ]
 
 jobs:
   lint:

docs/en/index.md

@@ -32,9 +32,9 @@ The coauthors are responsible for:
 - building the movement for mobility data interoperability.
 
 The coauthor coalition is:
-{%  include "coalition.md"  %}
+--8<-- "docs/en/coalition.md"
 
---8<-- "../../assets/co-authors-logo-grid.html"
+--8<-- "overrides/assets/co-authors-logo-grid.html"
 
 ---
 

docs/en/policies/mdip-coalition-composition.md

@@ -38,7 +38,7 @@ Members MAY be removed from the [MDIP Coalition](../governance.md#mdip-coalition
 
 ## Coalition Members
 
-{%  include "coalition.md"  %}
+--8<-- "docs/en/coalition.md"
 
 ## Document Changelog
 

docs/en/procurement.md

@@ -144,7 +144,7 @@ Fixed-route scheduling system functions:
 - Manage assignment of vehicles and drivers
 - Optionally, importing information from agency databases for these purposes
 
-![The image depicts a flowchart with five boxes in three columns, flowing left to right. On the left side are the boxes "agency staff" and "agency database", both flowing into the middle box "scheduling system", which flows into two boxes on the right side, "CAD/AVL system (ODS)" and "trip planners (GTFS)". All boxes are dark blue and connected by a solid arrow, except for "agency database" which is a light blue box connecting to the "scheduling system" by a dashed arrow.](../../assets/images/fixed_route_scheduling_system.png "fixed route scheduling system")
+![The image depicts a flowchart with five boxes in three columns, flowing left to right. On the left side are the boxes "agency staff" and "agency database", both flowing into the middle box "scheduling system", which flows into two boxes on the right side, "CAD/AVL system (TODS)" and "trip planners (GTFS)". All boxes are dark blue and connected by a solid arrow, except for "agency database" which is a light blue box connecting to the "scheduling system" by a dashed arrow.](../../assets/images/fixed_route_scheduling_system.png "fixed route scheduling system")
 
 Demand-response scheduling system functions include the following:
 
@@ -164,7 +164,7 @@ Fixed-route scheduling systems should meet the following requirements to be cons
 | |
 | :--- |
 | **Input/Output** |
-| The scheduling system shall receive, process, store, and export customer-generated data and derived data, free from additional costs or restrictions. <br />The scheduling system shall receive, store, provide access to, and make available via an appropriate API, data in the most recent version of the following open standards including their best practices:<ul><li>Rider-facing schedule data in GTFS Schedule; and</li><li>As-operated data in the Operational Data Standard (ODS). </li></ul>Best practices shall be defined as both should statements in the standard itself as well as official best practices documents such as the [GTFS Schedule Best Practices](https://gtfs.org/schedule/best-practices/). <br />The scheduling system shall be enabled to receive the following inputs both through an ad-hoc import or by fetching using an API. <ul><li>Driver/operator rosters and associated data necessary to assign drivers/operators to runs in a Well-documented Data Format.</li><li>Vehicle inventory and associated data necessary to assign vehicles to blocks in a Well-documented Data Format. </li></ul>Input data schemas and APIs shall be consistent with any other relevant open standards |
+| The scheduling system shall receive, process, store, and export customer-generated data and derived data, free from additional costs or restrictions. <br />The scheduling system shall receive, store, provide access to, and make available via an appropriate API, data in the most recent version of the following open standards including their best practices:<ul><li>Rider-facing schedule data in GTFS Schedule; and</li><li>As-operated data in the Operational Data Standard (TODS). </li></ul>Best practices shall be defined as both should statements in the standard itself as well as official best practices documents such as the [GTFS Schedule Best Practices](https://gtfs.org/schedule/best-practices/). <br />The scheduling system shall be enabled to receive the following inputs both through an ad-hoc import or by fetching using an API. <ul><li>Driver/operator rosters and associated data necessary to assign drivers/operators to runs in a Well-documented Data Format.</li><li>Vehicle inventory and associated data necessary to assign vehicles to blocks in a Well-documented Data Format. </li></ul>Input data schemas and APIs shall be consistent with any other relevant open standards |
 | **Built-in Enforcement + Monitoring** |
 | The scheduling system shall include a mechanism to ensure that exported data is consistent with the above requirements using relevant canonical validators.  Data which would not pass the above requirements using relevant canonical validators shall require an explicit override to export.  Validation reports for each export shall be transparent to the customer and provide a course of action to remedy. <br />Validation errors which are the result of scheduling software errors and cannot be remedied by the customer shall be automatically reported to Customer and Contractor and are subject to Performance Minimums and Recovery Time Objectives.  |
 
@@ -190,7 +190,7 @@ Fixed route CAD/AVL system functions:
 - Output real-time information regarding the status of the transit system
 - Optionally, control various downstream onboard or offboard systems
 
-![The image depicts a flowchart with four boxes in three columns, flowing left to right. On the left side is the box "scheduling system (ODS)", flowing into the middle box "CAD/AVL system", which flows into two boxes on the right side, "Reporting system (TIDES)" and "Trip planners (GTFS-RT)". All boxes are dark blue and connected by a solid arrow.](../../assets/images/fixed_route_cad_avl.png "fixed route cad/avl system")
+![The image depicts a flowchart with four boxes in three columns, flowing left to right. On the left side is the box "scheduling system (TODS)", flowing into the middle box "CAD/AVL system", which flows into two boxes on the right side, "Reporting system (TIDES)" and "Trip planners (GTFS-RT)". All boxes are dark blue and connected by a solid arrow.](../../assets/images/fixed_route_cad_avl.png "fixed route cad/avl system")
 
 #### CAD/AVL system requirements
 

docs/en/requirements.txt

@@ -10,9 +10,7 @@ Cosign the principles to support an interoperable vision for the future of trans
 Additional information about eligibility, roles, and duties can be found in our [governance documentation](governance.md).
 
 ## Cosignatories
-
-{% include 'cosignatories.md' %}
+--8<-- "docs/en/cosignatories.md"
 
 ## Coalition
-
-{% include 'coalition.md' %}
+--8<-- "docs/en/coalition.md"

docs/en/support.md

@@ -1,70 +1,70 @@
 <div class="logo-grid">
   <div class="logo-grid__item">
-    <img src="img/calact.png" alt="California Association of Coordinated Transportation  (CALACT)" />
+    <img src="../assets/images/calact.png" alt="California Association of Coordinated Transportation  (CALACT)" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/calitp.png" alt="California Integrated Travel Project (Cal-ITP)" />
+    <img src="../assets/images/calitp.png" alt="California Integrated Travel Project (Cal-ITP)" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/rtd.png" alt="Denver Regional Transportation District (RTD)" />
+    <img src="../assets/images/rtd.png" alt="Denver Regional Transportation District (RTD)" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/entur.png" alt="ENTUR" />
+    <img src="../assets/images/entur.png" alt="ENTUR" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/king-county-wa.jpg" alt="King County, Washington" />
+    <img src="../assets/images/king-county-wa.jpg" alt="King County, Washington" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/metro.png" alt="Los Angeles County Metropolitan Transportation Authority" />
+    <img src="../assets/images/metro.png" alt="Los Angeles County Metropolitan Transportation Authority" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/mbta.png" alt="Massachusetts Bay Transportation Authority (MBTA)" />
+    <img src="../assets/images/mbta.png" alt="Massachusetts Bay Transportation Authority (MBTA)" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/metrotransit.png" alt="MetroTransit" />
+    <img src="../assets/images/metrotransit.png" alt="MetroTransit" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/mtc.png" alt="Metropolitan Transportation Commission (MTC)" />
+    <img src="../assets/images/mtc.png" alt="Metropolitan Transportation Commission (MTC)" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/mdot.png" alt="Michigan Department of Transportation (MDOT)" />
+    <img src="../assets/images/mdot.png" alt="Michigan Department of Transportation (MDOT)" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/mndot.png" alt="Minnesota Department of Transportation" />
+    <img src="../assets/images/mndot.png" alt="Minnesota Department of Transportation" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/mobilitydata.png" alt="MobilityData" />
+    <img src="../assets/images/mobilitydata.png" alt="MobilityData" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/ncdot.png" alt="North Carolina Department of Transportation" />
+    <img src="../assets/images/ncdot.png" alt="North Carolina Department of Transportation" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/odot.png" alt="Oregon Department of Transportation" />
+    <img src="../assets/images/odot.png" alt="Oregon Department of Transportation" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/sumc.png" alt="Shared Use Mobility Center (SUMC)" />
+    <img src="../assets/images/sumc.png" alt="Shared Use Mobility Center (SUMC)" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/sound-transit.png" alt="Sound Transit" />
+    <img src="../assets/images/sound-transit.png" alt="Sound Transit" />
   </div>
   <div class="logo-grid__item">
     <div class="show-light-mode">
-      <img src="img/taskar-light.png" alt="Taskar Center for Accessible Technology" />
+      <img src="../assets/images/taskar-light.png" alt="Taskar Center for Accessible Technology" />
     </div>
     <div class="show-dark-mode">
-      <img src="img/taskar-dark.png" alt="Taskar Center for Accessible Technology" />
+      <img src="../assets/images/taskar-dark.png" alt="Taskar Center for Accessible Technology" />
     </div>
   </div>
   <div class="logo-grid__item">
-    <img src="img/trimet.png" alt="Tri-Met" />
+    <img src="../assets/images/trimet.png" alt="Tri-Met" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/vttrans.png" alt="Vermont Agency of Transportation" />
+    <img src="../assets/images/vttrans.png" alt="Vermont Agency of Transportation" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/via.png" alt="VIA Metropolitan Transit San Antonio" />
+    <img src="../assets/images/via.png" alt="VIA Metropolitan Transit San Antonio" />
   </div>
   <div class="logo-grid__item">
-    <img src="img/wsdot.png" alt="Washington State Department of Transportation (WSDOT) Public Transportation Division" />
+    <img src="../assets/images/wsdot.png" alt="Washington State Department of Transportation (WSDOT) Public Transportation Division" />
   </div>
 </div>