Skip to content

Uiupdates - #212

Open
Mrankit47 wants to merge 2 commits into
floci-io:mainfrom
Mrankit47:uiupdates
Open

Uiupdates#212
Mrankit47 wants to merge 2 commits into
floci-io:mainfrom
Mrankit47:uiupdates

Conversation

@Mrankit47

Copy link
Copy Markdown

Summary

Type of change

  • Bug fix (fix:)
  • New feature / service UI (feat:)
  • Breaking change (feat!: or fix!:)
  • Docs / chore

Area

  • Frontend (packages/frontend)
  • API / Cloud Proxy (packages/api)
  • Cloud Explorer adapter / schema
  • Build / CI / Docker

Verification

Checklist

  • pnpm lint, pnpm type-check, pnpm test, and pnpm build pass locally
  • New or updated tests added where it makes sense (bun test in packages/api)
  • No fake/mock data added — unwired states stay empty or show an explicit placeholder
  • Commit messages / PR title follow Conventional Commits

@greptile-apps

greptile-apps Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR refreshes the frontend’s typography, color tokens, spacing, and component styling toward an Inter/JetBrains Mono and slate/terracotta visual system.

  • Updates the externally loaded font families and weights.
  • Revises dark and light theme variables and interactive colors.
  • Restyles navigation, service cards, statuses, selectors, console summaries, and primary buttons.
  • Adds an empty example file.

Confidence Score: 4/5

The PR appears functionally safe to merge, with non-blocking accessibility and typography-consistency issues worth correcting.

The styling changes do not expose a functional or security failure, but primary-button labels have insufficient contrast and the removed Space Mono download leaves client-dependent font rendering.

Files Needing Attention: packages/frontend/index.html, packages/frontend/src/index.css

Important Files Changed

Filename Overview
packages/frontend/index.html Replaces Sora and Space Mono font loading with Inter and expanded JetBrains Mono weights, leaving inconsistent Space Mono-first declarations elsewhere.
packages/frontend/src/index.css Applies a broad visual theme refresh; the new primary-button color combination has insufficient normal-text contrast.
example.txt Adds an empty file with no functional effect.

Reviews (1): Last reviewed commit: "ui update" | Re-trigger Greptile

Comment on lines 3302 to +3314
.button.primary {
background: #3949ab;
border-color: #3949ab;
color: white;
background: var(--accent);
border-color: var(--accent);
color: #ffffff;
font-weight: 600;
box-shadow: 0 1px 2px rgba(0, 0, 0, 0.15);
}

.button.primary:hover {
background: #5c6bc0;
border-color: #5c6bc0;
background: var(--accent-hover);
border-color: var(--accent-hover);
color: #ffffff;
box-shadow: 0 2px 4px rgba(0, 0, 0, 0.2);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Primary Button Contrast

Primary buttons now render 11–12px white labels on #d97757, changing to #c46545 on hover. These combinations provide approximately 3.1:1 and 4.0:1 contrast, below the 4.5:1 threshold for normal text, so primary actions may be difficult to read. Please adjust the foreground or background colors to provide sufficient contrast in both states.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

<link rel="icon" href="/src/assets/floci-black.svg" />
<link
href="https://fonts.googleapis.com/css2?family=Sora:wght@300;400;500;600;700;800&family=Space+Mono:wght@400;700&family=JetBrains+Mono:wght@400;500&display=swap"
href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500;600&display=swap"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Inconsistent Monospace Rendering

The updated font request stops loading Space Mono, but several CSS declarations still prioritize it over JetBrains Mono. Clients with Space Mono installed locally will use it, while other clients will fall back to JetBrains Mono, producing inconsistent code, log, and metadata typography. Please update those declarations or continue loading Space Mono.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant