-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement new homepage edits #463
Comments
2 notes:
|
Moving to Blocked until content is finalized, ETA is 9/5. |
|
I suggest this ticket be broken down into 3 tickets, so they can be done in parallel:
cc @angela-tran |
Thank you @machikoyasuda for breaking this down! In which ticket are we including the development of the banner? Our GTFS-RT RFP draft is ready for comment and we are asking DGS if we can make an announcement on MobiMart. If possible as a stretch goal this sprint, I'd like to make that announcement via a banner. If not, we can put it in the existing section. We are sending the below announcement for their review and approval: DGS has issued a Draft Request for Proposals (RFP) for GTFS-Realtime software to enable public transit agencies to provide riders with the real time location of their fleets. Responses are due by 2:00 PM Pacific Time on October 12, 2023. Learn more here. |
Hi @mrose914, we're focused on deploying the Veterans code out to production for the first half of this week, with our Sprint ending on Tuesday 9/19. We can come back to MobiMart over the latter half of the week. |
Thank you @thekaveman!! Sounds like a plan. |
@mrose914 we talked through some of this today, and noticed that this banner text:
Is much longer than what the design supports: Was the intention to use this exact text on the banner, or a shortened version? Might it be easier to get DGS to approve a shortened version first? |
@thekaveman Very much expect to need to shorten it, but figured it would be simpler to have them approve a longer one that we can then shorten than the other way around. I let Zach and Lauren know to message to DGS that we would likely shorten for space. What is the character limit more or less so I can rework a few versions? And thank you for discussing it so quickly! |
Here are a few shortened versions: DGS has issued a Draft Request for Proposals (RFP) for GTFS-Realtime software to enable public transit agencies to provide riders with the real time location of their fleets. Respond by 2:00 PM PT on 10/12/23. Learn more here. DGS has issued a Draft Request for Proposals for GTFS-Realtime software so public transit agencies can provide riders with real time fleet location. Responses due by 2pm PT on 10/12/23. Learn more here. DGS has issued a Draft RFP for GTFS-Realtime software so public transit agencies can provide riders with real time fleet location. Responses due by 2pm PT on 10/12/23. Learn more here. DGS has issued a Draft RFP for GTFS-Realtime software so public transit agencies can provide riders with real time fleet location. Learn more here. |
Thanks to @segacy1, we have two options here: https://www.figma.com/file/TfWk1iDHdlt7bSA3DjQuQv/Mobility-Marketplace?type=design&node-id=6819-1391&mode=design&t=oEjptJXGLi8oeVZg-0 For the shorter version (max of 150 characters): For the longer version (max of 250 characters): I favor the longer version given that most of the content we expect to make announcements about, contracts and products, on MobiMart is acronym-laden and unlikely to lend itself to super concise one-liners. |
@thekaveman @mrose914 I cleaned everything up here for folks to see. There are options for 150, 240, and 250 character limits. One note—you'll see that in the 150 & 250 character options, the action link (e.g. learn more) needs to be included in the character count. |
Copy is approved and agency logo use was approved. |
Designs here: https://www.figma.com/file/TfWk1iDHdlt7bSA3DjQuQv/Mobility-Marketplace?type=design&node-id=6819-1396&mode=design&t=4BtRBjMIZXThxpmP-0
Copy here: https://docs.google.com/document/d/1XLUM0EuFa9-A1icT3rySVEUfyZcohOB0D-NTpla8TtI/edit#heading=h.n4fzxa1e69w7
cc @segacy1
The text was updated successfully, but these errors were encountered: