Comet Sprint 33 / Daylight Sprint 5 / Lark Sprint 8 Review (July 10, 2024 - July 23, 2024)

What was the goal of Comet Sprint 33 / Daylight Sprint 5 / Lark Sprint 8?

Comet: The primary aim was to resolve inconsistencies on the Object’s list display tabs.

Daylight: The primary deliverable for this summer's work cycle is an example of Daylight's micro frontend component usage and during this first sprint the focus was on bettering the developer experience.

Lark: The goal was to engage in a technical demo and discussion within the team concerning the initial needs for front end development.

What is the milestone that this sprint is supporting?

Comet: Resolving UI inconsistencies in Object listings.

Daylight: Understanding and improving the foundational developer experience for micro frontend development.

Lark: Initial technical discussions and demo for frontend development requirements.

Accomplishments of Comet Sprint 33 / Daylight Sprint 5 / Lark Sprint 8:

Comet: 

• Addressed and fixed various UI inconsistencies within the Object’s list display headers and search wording.

Daylight:

• To streamline development, the Ruby gem's functionality was translated into a single JavaScript file, allowing developers to use Daylight examples without needing a full Ruby app installation.
• Added a README explaining how to use the newly created JavaScript file for easier integration and use of Daylight components
• Set up basic CI and testing.

Lark:

• Conducted a technical demo to showcase the current Authority Record workflow used by UCSD.
• Created initial mockups.
• Engaged in the discussions within the team to refine the mockups and better understand the frontend development needs.

Overall: We began adjusting to the new team dynamics, including the inclusion of UCSC and the departure of one of our team leads.

What’s next?

Daylight: Setup and document the developer environment.

GitLab link: https://gitlab.com/surfliner/surfliner/-/milestones/112#tab-issues