[Tracking] Reports Page v1

[eryc-cc]

Summary

We need to have reports ready for the hacktoberfest event.

A lot of conversation around a more complete version of the Reports page happened on #93, but for now, we'll stick to an MVP-version, providing only the CSV, and scoping a PDF Report.

🔗 View Designs in Figma

We'll have two versions, for each persona:

1. For Digital Ocean (during the Hacktoberfest event)
2. For the Insiders group

Design Tasks:

• [ ] #92
• [x] #153
• [x] #154

Development Tasks:

• Hacktoberfest top priority
  • [x] #166
  • [x] #167
  • [x] #168
  • [x] #169
• Insiders after the hacktoberfest is released
  • [ ] [Front-End] Create the SidebarContents component
  • [ ] [Front-End] Create a Search input component
  • [ ] [Front-End] Create a Repository Card component for reports search results
  • [ ] [Front-End] Create the ReportSummary component
  • [ ] [Front-End] Implement the Insider Reports Page
  • [ ] Create the logic for generating the Insider reports

---

Hacktobefest Version

• Can only filter (by the pre-defined opinionated filters we have)
• History will show below

Insiders Version

• Cannot use the pre-defined opinionated filters (because it would grab too many repos)
• User has to select which repos they want reports from
• History will be shown in another page (user can navigate through the left sidebar)

[eryc-cc]

@bdougie @chadstewart

I think it'd be better to focus on the Hacktoberfest Reports, rather than try to implement for Insiders...

My thought process is: we can get better feedback if we keep insiders focused. When the Hacktoberfest Reports is done, we can proceed with implementing it for Insiders.

What do you think?

[bdougie]

I agree. Only digital needs access to these reports.

[eryc-cc]

Okay, I haven't created issues for the insiders, but we're tracking them here... I think it'll make more sense to provide them reports when we have a nice PDF, or a feature to share on social media.