Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions docs/2025/ux-ui-design/updates/2025-06-24.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
title: Week 4
author: Devanshi Sachan
---
<!--
SPDX-License-Identifier: CC-BY-SA-4.0

SPDX-FileCopyrightText: 2025 Devanshi Sachan <devs221102gmail.com>
-->

# Week 4: Meeting Summary and Activities

**Date:** June 24, 2025

## Attendees
- Devanshi Sachan
- Katharina Ettinger
- Shaheem Azmal M MD
- Amrit Verma
- Gaurav Mishra
- Kaushlendra Pratap
- Tiyasa Kundu

## Discussion Points
- We discussed why using FOSSology’s brand red for CTAs and interactive elements could be problematic. Since red is typically associated with errors or warnings, using it for everyday interactions might confuse users or create unnecessary tension. We agreed it’s better reserved for alerts and critical states. A calmer, more neutral color—likely a shade of blue—is being considered for CTAs to convey trust and action without alarming users.
- There was an in-depth discussion around the different secondary navigation bar layouts we’ve been exploring. Some felt too cramped, especially on smaller screens, while others lacked clarity or visual balance. We talked through which patterns might scale well, how much flexibility we need, and what kind of constraints we should design within to keep things clean and usable.

## Activities Completed
- Audited the current color usage across the FOSSology UI and documented it. Ran accessibility checks based on usage context (text, icons, background), and adjusted colors where contrast ratios fell short of standards.
- Added a clear breakdown of the grid system and responsive breakpoints in the design system to guide layout behavior across devices.
- Created and exported custom icons in multiple sizes to suit different contexts within the new design. These icons have been integrated into the design system.

## Next Steps
- Continue expanding the design system by finalizing a typographic scale and documenting all completed header components, including interaction behaviors.
- Begin designing an additional core page in parallel with refining the secondary navigation bar, allowing us to cover more screens and components within the timeline.
- Iterate further on the secondary navigation bar based on internal feedback-focus on cleaner structure, space-efficient design, and visual consistency with the rest of the interface.
38 changes: 38 additions & 0 deletions docs/2025/ux-ui-design/updates/2025-07-01.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
title: Week 5
author: Devanshi Sachan
---
<!--
SPDX-License-Identifier: CC-BY-SA-4.0

SPDX-FileCopyrightText: 2025 Devanshi Sachan <devs221102gmail.com>
-->

# Week 5: Meeting Summary and Activities

**Date:** July 1, 2025

## Attendees
- Devanshi Sachan
- Katharina Ettinger
- Shaheem Azmal M MD
- Amrit Verma
- Gaurav Mishra
- Kaushlendra Pratap
- Soham Banerjee
- Tiyasa Kundu

## Discussion Points
- Reviewed updated versions of the secondary navigation bar, evaluating whether they meet layout constraints and usability expectations. Key concerns included visual heaviness, the number of visible options, and how to reduce cognitive load without losing functionality.
- Introduced a new shade of blue into the color palette, derived from the blue used in table components across the existing FOSSology UI. This aims to create visual continuity while enhancing the new design system.

## Activities Completed
- Reassessed earlier secondary nav bar iterations and incorporated feedback to address issues around visual weight, spacing, and clarity.
- Added both primary and secondary buttons to the design system, covering all interactive states (default, hover, active) and variations (with and without icons).
- Progressed on the Search page design, creating supporting components such as accordions, radio buttons, and form elements tailored to the page’s structure.
- Designed a full set of alert components - error, warning, info, and success, with variations to support flexible use across different interface contexts.

## Next Steps
- Finalize the Search page layout and ensure all supporting components are fully designed and documented.
- Wrap up and validate the secondary navigation bar design, incorporating final feedback and preparing it for system-wide use.
- Continue documenting all completed components in the design system, clearly outlining their usage, interaction states, and behavioral logic for consistency and easier developer handoff.
37 changes: 37 additions & 0 deletions docs/2025/ux-ui-design/updates/2025-07-08.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
---
title: Week 6
author: Devanshi Sachan
---
<!--
SPDX-License-Identifier: CC-BY-SA-4.0

SPDX-FileCopyrightText: 2025 Devanshi Sachan <devs221102gmail.com>
-->

# Week 6: Meeting Summary and Activities

**Date:** July 8, 2025

## Attendees
- Devanshi Sachan
- Katharina Ettinger
- Shaheem Azmal M MD
- Amrit Verma
- Gaurav Mishra
- Kaushlendra Pratap
- Dearsh Oberoi

## Discussion Points
- Finalized the placement of breadcrumbs in relation to the secondary navigation bar. Discussed whether breadcrumbs should always be visible or collapsible, considering their role in helping users navigate through nested sections.
- Finalized the layout, size, and behavior of the secondary navigation bar, ensuring it aligns with content structure, remains visually balanced, and functions intuitively across different screen sizes.
- Reviewed and wrapped up the design for the Search page, confirming that all components behave as intended and follow consistent interaction patterns.

## Activities Completed
- Applied all feedback to the secondary navigation bar, adjusting its placement and reducing visual clutter by limiting the number of options shown upfront; finalized the design.
- Refined the Search page design by incorporating feedback, especially on the accordion component, ensuring it is accessible, clean, and consistent with the rest of the UI; marked this page as complete.
- Documented core components - Header, Footer, and Alert messages - in the design system, including usage guidelines, interaction states, and integration notes to support consistent implementation.

## Next Steps
- Begin documentation of the secondary navigation bar and Search page components in the design system, clearly outlining their intended use, responsive behavior, and all state variations.
- Kick off design work on the "Schedule an Analysis" page, starting with basic components like checkboxes, inputs, and layout structure.
- Start analyzing and ideating on the Data Table component reviewing existing patterns, identifying pain points, and exploring cleaner, more scalable design options.