Comet Sprint 41/ Daylight Sprint 13/ Lark Sprint 16 Review (Apr 2, 2025 – Apr 21, 2025)

Gabriela Montoya -

Comet Sprint 41 / Daylight Sprint 13 / Lark Sprint 16

 What were the goal of Comet Sprint 41 / Daylight Sprint 13 / Lark Sprint 16?

Daylight: Maturing our components so that they’ll be ready for connectivity in order to get the lifecycle and ecosystem fully presentable and demoable.

Lark: Set up Lark and Comet seed data and share JSON-LD serialization code between Lark and Superskunk.

Comet: Finalize QA, Sandbox, Production, and Preview architectures.

What is the milestone that this sprint is supporting?

Daylight: Enhancing accessibility and responsiveness, while also getting ready for future integrations with API endpoints.

Lark: Getting Lark to a place where we can start using it in integrations with other platforms.

Comet: Finalize requirements for staging and production environments, as well as being on the same page regarding discovery preview environments. Also, retiring the old staging environments.

Accomplishments of Comet Sprint 41 / Daylight Sprint 13 / Lark Sprint 16: 

Daylight:

  • Implemented accessibility improvements across several components, including Results-Facet-Menu and Result-Search-Sort.
  • Enhanced the bundler to allow components to reside in a single directory, aligning with our deployment strategy, along with updates to the Results-Complex-Pager to prepare for future endpoints.
  • Revised documentation and READMEs for various components to ensure our team and users have access to the latest information and best practices.
  • Focused on making components more responsive.

Lark:

  • Shared more code between Lark and Superskunk.
  • Developed the capacity to declare class mappings in schemas so that these don’t need to be hardcoded into the application.

Comet: 

  • Sorted out what our production setup will be. We’ll have a sandbox which will be a mirror of production for testing and training, and so on. This will be the architecture of for all of our Surfliner systems.
  • Changed the default page for Comet login to the Dashboard page.
  • Completed file characterization fixes, including calculating checksums on ingest.

What’s next?

Daylight:

  • We will continue to enhance the accessibility and responsiveness of our components, focusing on any additional functionality that may be required for upcoming integrations.

Lark:

  • We will be continuing to develop Lark to a point of being able to integrate it with other platforms.

Comet:

  • Working out requirements for the preview environments.
  • Finalizing nested resources work for Comet and Lark.
  • Improvements to file versioning and replacements.

GitLab link: https://gitlab.com/surfliner/surfliner/-/cadences/2062403/iterations/2541237