Skip to content

refactor: update UI/UX terminology to match Naruon philosophy - #340

Merged
seonghobae merged 6 commits into
developfrom
fix/ui-ux-terminology-4048639708573802158
Jun 4, 2026
Merged

refactor: update UI/UX terminology to match Naruon philosophy#340
seonghobae merged 6 commits into
developfrom
fix/ui-ux-terminology-4048639708573802158

Conversation

@seonghobae

@seonghobae seonghobae commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Replaces outdated terminology like 'AI Summary', 'Insight', 'Dashboard', 'Todo', etc., with '맥락 종합', '판단 포인트', '홈', '실행 항목', and other Naruon-approved terms across the frontend codebase as defined in the provided guidelines. All corresponding unit tests and playwright specs have been updated to ensure the build passes.


PR created automatically by Jules for task 4048639708573802158 started by @seonghobae

Summary by CodeRabbit

  • Chores

    • Unified Korean UI terminology across the app: "할 일" → "실행 항목", "이메일/캘린더 반영" → "메일/일정 반영", "대시보드" → "홈", and "요약" → "맥락 종합". Button labels, menu items, status/error messages, and accessibility labels updated for consistency on desktop and mobile.
  • Tests

    • Updated unit and end-to-end test expectations and locators to match the revised UI copy and accessibility labels.

- Map 'AI Summary' to '맥락 종합'
- Map 'Insight' to '판단 포인트'
- Map 'Todo' to '실행 항목'
- Map 'Calendar Sync' to '일정 반영'
- Map 'Dashboard' to '홈'
- Map 'Email' to '메일'
- Update related test cases and e2e specs to reflect new text
- Fix grammatical postpositions for Korean strings
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@seonghobae, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 56 minutes and 42 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9dc1d939-e586-4f97-9d6d-32eee1d77b06

📥 Commits

Reviewing files that changed from the base of the PR and between fe56f3e and 8561abf.

📒 Files selected for processing (1)
  • .github/workflows/strix.yml
📝 Walkthrough

Walkthrough

This PR updates Korean UI terminology across the frontend: 이메일→메일, 캘린더 반영→일정 반영, 할 일→실행 항목, and 요약→맥락 종합 in components, unit/page tests, and e2e specs.

Changes

Korean UI Terminology and Branding Update

Layer / File(s) Summary
Core component UI text implementations
src/components/DashboardLayout.tsx, src/components/EmailDetail.tsx, src/components/EmailList.tsx, src/components/NetworkGraph.tsx, src/components/ProjectsLayout.tsx, src/components/SettingsLayout.tsx, src/components/TasksLayout.tsx, src/components/WorkspaceHome.tsx, src/components/mobile-workspace-panels.tsx
Header actions, startup view labels, button/menu text, empty-state copy, and ARIA labels updated to new Korean terminology.
Component unit test assertions
src/components/DashboardLayout.test.tsx, src/components/EmailDetail.test.tsx, src/components/SettingsLayout.test.tsx, src/components/ui/control-sizing.test.tsx
Unit test expectations updated to match renamed labels and aria text.
Page-level metadata and example text
src/app/layout.tsx, src/app/prompt-studio/page.tsx
Root metadata description and Prompt Studio example string updated (이메일메일).
Page and app-level test updates
src/app/layout.test.tsx, src/app/ai-hub/page.test.tsx, src/app/page.test.tsx, src/app/tasks/page.test.tsx
Page tests adjusted for new card titles, startup status text, and page headings (e.g., “의사결정 로그 맥락 종합”, “일정 반영 대기”, “실행 항목 추적”).
E2E test assertion updates
tests/e2e/dashboard-branding.spec.ts, tests/e2e/dashboard-flows.spec.ts, tests/e2e/scrolling.spec.ts
Playwright specs updated for aria-label selectors, header/menu action labels, pending text, confirmation copy, and /tasks heading expectations across viewports.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

Poem

🐰 작은 토끼가 속삭여요,
"메일로 바뀐 말들을 꾹꾹,
대시보드는 홈으로, 요약은 맥락으로,
버튼과 라벨이 춤을 추네,
Naruon의 얼굴이 반짝반짝!"

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely summarizes the main change—a systematic terminology update across the frontend codebase to align with Naruon philosophy—matching the primary objective evident in the raw summary.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/ui-ux-terminology-4048639708573802158

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

PR governance metadata gate is not ready for 8561abf765380a83c3f88c0768096a16faa583a6:

  • Required check metadata could not be read: no required checks reported on the 'fix/ui-ux-terminology-4048639708573802158' branch.
  • Current-head CodeRabbit issue comment has blocking warning/failure evidence on 8561abf.

@coderabbitai coderabbitai Bot left a comment

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.

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/src/components/DashboardLayout.tsx`:
- Line 76: The message string for the menu item object (label: '실행 항목 생성',
action: 'create-task', icon: CheckCircle2) in DashboardLayout.tsx contains a
duplicated phrase ("실행 항목을 실행 항목으로"); update the message to a clear,
non-redundant Korean phrase (for example, "메일 상세 패널에서 실행 항목으로 정리합니다." or "메일 상세
패널에서 실행 항목을 생성합니다.") by editing the message value in that object so the
user-facing text reads naturally and without repetition.

In `@frontend/src/components/TasksLayout.tsx`:
- Line 523: The div in TasksLayout.tsx with class "flex items-center gap-1
hover:text-primary transition-colors cursor-pointer" is visually clickable but
inert; replace it with a real interactive element (preferably an anchor <a> if
it navigates to the mail source or a <button> if it triggers an action) and wire
it to the appropriate handler/href (use the mail source URL prop used in this
component), add keyboard accessibility (focus styles, onKeyDown if needed) and
an accessible name/aria-label (preserve the title "메일 출처 바로가기"), or if no
interaction is intended remove the cursor-pointer and hover styles to avoid
misleading affordance. Ensure the element in TasksLayout.tsx exposes proper
semantics rather than leaving the plain div.

In `@frontend/tests/e2e/dashboard-branding.spec.ts`:
- Line 1537: The test fixes a typo in the expected string: update the call to
detailRegion.getByText that currently looks for '2개 실행 항목을 티켓형 실행 항목로 추적합니다.' to
instead expect the grammatically correct '2개 실행 항목을 티켓형 실행 항목으로 추적합니다.' so the
assertion uses the corrected copy; locate the assertion using
detailRegion.getByText and replace the incorrect substring accordingly.

In `@frontend/tests/e2e/dashboard-flows.spec.ts`:
- Line 55: Typo in the assertion string inside
frontend/tests/e2e/dashboard-flows.spec.ts: update the text passed to
detailRegion.getByText from '2개 실행 항목을 티켓형 실행 항목로 추적합니다.' to the correct '2개 실행
항목을 티켓형 실행 항목으로 추적합니다.' so the expectation matches the UI copy; locate the call
to detailRegion.getByText and replace the mistaken '로' with '으로'.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f8e63cc1-d63c-4400-918f-79338a0d5f34

📥 Commits

Reviewing files that changed from the base of the PR and between 8b9c770 and 57bf6a0.

📒 Files selected for processing (22)
  • frontend/src/app/ai-hub/page.test.tsx
  • frontend/src/app/layout.test.tsx
  • frontend/src/app/layout.tsx
  • frontend/src/app/page.test.tsx
  • frontend/src/app/prompt-studio/page.tsx
  • frontend/src/app/tasks/page.test.tsx
  • frontend/src/components/DashboardLayout.test.tsx
  • frontend/src/components/DashboardLayout.tsx
  • frontend/src/components/EmailDetail.test.tsx
  • frontend/src/components/EmailDetail.tsx
  • frontend/src/components/EmailList.tsx
  • frontend/src/components/NetworkGraph.tsx
  • frontend/src/components/ProjectsLayout.tsx
  • frontend/src/components/SettingsLayout.test.tsx
  • frontend/src/components/SettingsLayout.tsx
  • frontend/src/components/TasksLayout.tsx
  • frontend/src/components/WorkspaceHome.tsx
  • frontend/src/components/mobile-workspace-panels.tsx
  • frontend/src/components/ui/control-sizing.test.tsx
  • frontend/tests/e2e/dashboard-branding.spec.ts
  • frontend/tests/e2e/dashboard-flows.spec.ts
  • frontend/tests/e2e/scrolling.spec.ts

Comment thread frontend/src/components/DashboardLayout.tsx Outdated
Comment thread frontend/src/components/TasksLayout.tsx Outdated
Comment thread frontend/tests/e2e/dashboard-branding.spec.ts Outdated
Comment thread frontend/tests/e2e/dashboard-flows.spec.ts Outdated
seonghobae and others added 3 commits June 4, 2026 04:38
- Map 'AI Summary' to '맥락 종합'
- Map 'Insight' to '판단 포인트'
- Map 'Todo' to '실행 항목'
- Map 'Calendar Sync' to '일정 반영'
- Map 'Dashboard' to '홈'
- Map 'Email' to '메일'
- Update related test cases and e2e specs to reflect new text
- Fix grammatical postpositions for Korean strings
- Map 'AI Summary' to '맥락 종합'
- Map 'Insight' to '판단 포인트'
- Map 'Todo' to '실행 항목'
- Map 'Calendar Sync' to '일정 반영'
- Map 'Dashboard' to '홈'
- Map 'Email' to '메일'
- Update related test cases and e2e specs to reflect new text
- Fix grammatical postpositions for Korean strings
coderabbitai[bot]
coderabbitai Bot previously approved these changes Jun 4, 2026
- Increase overall job timeout-minutes from 90 to 120
- Increase `process_budget_seconds` from 2400 to 3600
- Increase `LLM_TIMEOUT` from 90 to 120
- Increase `STRIX_TOTAL_TIMEOUT_SECONDS` from 4800 to 7200
This addresses the `Strix run timed out after 2400s (exit code 124)` failure observed in CI.
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