Align Reports with updated Cal-ITP/MobiMart styles

[srhhnry]

• India to review updated style guide for cal-itp/mobimart
• If possible, integrate updated style guide into the Reports

[thekaveman]

@srhhnry FYI I'm going to transfer this issue to the Reports repository... not related to Benefits.

[srhhnry]

@thekaveman Thanks--we actually realized we needed a repository that's more agnostic than any of the given sites as some of these new issues cover multiple sites (also a problem is that I didn't have access to Reports when I created the issue). I'm going to see if I can make that repository now with my access level and if not I'll circle back. OH, before I do so--any protocol I should be aware of there?

[srhhnry]

Update: I figured out how to make one: https://github.com/cal-itp/cross-team-design and it didn't seem too intrusive. This issue could either live in the new repository or in Reports, but Reports needs a design tag or else the issue will get lost from the digital services project page.

[thekaveman]

@srhhnry this is really what the cal-itp/services-team repository is for... I'd rather we didn't create yet another repo just to track issues like this. Can we please move over to that repo for cross-team stuff?

[indexing]

@srhhnry Can we close this issue and/or migrate it to the services-team repo?

[srhhnry]

I don't see the option to transfer the issue and I think it's because I don't have permissions in the services-team repo.

As it's been several months, I don't have any insight anymore into who might make these alignment changes, as the designer who was working on Reports is no longer on that project. Basically, aligning the Reports site with the rest of the Cal-ITP properties is now a cross-team (Compiler + Jarvus) product decision, not really a design decision. I can see the argument for doing this work from a design perspective but don't really know about priority or resourcing.

[indexing]

I just realized this issue is already in the reports repo. I've removed it from the Digital Services project, but we can add it back if it becomes relevant again.