starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #2357] Design consistency: hardcoded #7AC455 in navigation links #663

New issue

Closed

opened 2026-02-26 18:47:58 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 18:47:58 +03:00

Owner

Originally created by @dylantarre on GitHub (Jan 5, 2026).
Original GitHub issue: https://github.com/documenso/documenso/issues/2357

Summary

While exploring the codebase, I noticed the color #7AC455 is hardcoded in 6 files for "back" navigation links, while other elements use design tokens like text-documenso.

Current State

Files using text-[#7AC455]:

apps/remix/app/components/general/skeletons/document-edit-skeleton.tsx
apps/remix/app/routes/_authenticated+/t.$teamUrl+/documents.$id.logs.tsx
apps/remix/app/routes/_authenticated+/t.$teamUrl+/templates.$id._index.tsx
apps/remix/app/routes/_authenticated+/t.$teamUrl+/templates.$id.legacy_editor.tsx
apps/remix/app/routes/_authenticated+/t.$teamUrl+/documents.$id.legacy_editor.tsx
apps/remix/app/routes/_authenticated+/t.$teamUrl+/documents.$id._index.tsx

Interestingly, document-edit-skeleton.tsx uses both:

Line 10: text-[#7AC455] (hardcoded)
Line 26: text-documenso (token)

Question

Is this intentional? The color sits between documenso-600 and documenso-700 in your scale.

If you'd like this standardized, I'm happy to submit a PR that either:

A) Adds it to your color scale (e.g., documenso-550: '#7AC455')
B) Replaces with an existing token like text-documenso-600

Let me know your preference!

Found with Buoy — design system drift detection

Originally created by @dylantarre on GitHub (Jan 5, 2026). Original GitHub issue: https://github.com/documenso/documenso/issues/2357 ## Summary While exploring the codebase, I noticed the color `#7AC455` is hardcoded in 6 files for "back" navigation links, while other elements use design tokens like `text-documenso`. ## Current State **Files using `text-[#7AC455]`:** - `apps/remix/app/components/general/skeletons/document-edit-skeleton.tsx` - `apps/remix/app/routes/_authenticated+/t.$teamUrl+/documents.$id.logs.tsx` - `apps/remix/app/routes/_authenticated+/t.$teamUrl+/templates.$id._index.tsx` - `apps/remix/app/routes/_authenticated+/t.$teamUrl+/templates.$id.legacy_editor.tsx` - `apps/remix/app/routes/_authenticated+/t.$teamUrl+/documents.$id.legacy_editor.tsx` - `apps/remix/app/routes/_authenticated+/t.$teamUrl+/documents.$id._index.tsx` Interestingly, `document-edit-skeleton.tsx` uses both: - Line 10: `text-[#7AC455]` (hardcoded) - Line 26: `text-documenso` (token) ## Question Is this intentional? The color sits between `documenso-600` and `documenso-700` in your scale. If you'd like this standardized, I'm happy to submit a PR that either: - **A)** Adds it to your color scale (e.g., `documenso-550: '#7AC455'`) - **B)** Replaces with an existing token like `text-documenso-600` Let me know your preference! --- *Found with [Buoy](https://github.com/buoy-design/buoy) — design system drift detection*

kerem

2026-02-26 18:47:58 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:58 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 5, 2026):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Jan 5, 2026): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:47:58 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Jan 5, 2026):

Great catch, needs to be consistent. Replacing with an existing token will be the test option

@ephraimduncan commented on GitHub (Jan 5, 2026): Great catch, needs to be consistent. Replacing with an existing token will be the test option

kerem referenced this issue

2026-02-26 19:31:52 +03:00

[PR #663] [MERGED] feat: add/update title of the Document #1108

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#663

No description provided.

Rows
Columns