feat(brand): Graphite 아이덴티티 적용 - #127
Conversation
차가운 종이와 매화색 팔레트, 로고와 favicon을 Ark에 적용했습니다. IntelliJ Graphite Theme 소스와 Marketplace 자산을 함께 추가했습니다.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 926269855f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 4. Select `Graphite Theme` from | ||
| `Settings | Appearance & Behavior | Appearance`. | ||
|
|
||
| For offline installation, download the ZIP from [Releases](../../releases), |
There was a problem hiding this comment.
For users following the offline installation path, ../../releases is interpreted as a repository-relative content path rather than the GitHub Releases page; a repo-wide search confirms that no corresponding releases directory exists, so the download link leads to a missing page. Link directly to the repository's actual Releases URL so users can obtain the packaged ZIP.
Useful? React with 👍 / 👎.
| <option name="CARET_COLOR" value="252525" /> | ||
| <option name="CARET_ROW_COLOR" value="E2E2E5" /> | ||
| <option name="CONSOLE_BACKGROUND_KEY" value="252525" /> | ||
| <option name="CONSOLE_NORMAL_OUTPUT" value="EAEBEA" /> |
There was a problem hiding this comment.
When this scheme is used in Run or Debug consoles, IntelliJ reads CONSOLE_NORMAL_OUTPUT from the scheme's <attributes> section, not <colors>, so this entry is ignored. Because the theme separately changes CONSOLE_BACKGROUND_KEY to dark graphite, normal output then inherits the light parent scheme's dark foreground and can become nearly unreadable; define the foreground through an attribute value instead.
Useful? React with 👍 / 👎.
| <svg xmlns="http://www.w3.org/2000/svg" width="512" height="512" viewBox="108 108 296 296" role="img" aria-labelledby="title desc"> | ||
| <title id="title">Graphite blossom mark</title> | ||
| <desc id="desc">A transparent five-petal graphite plum blossom with a plum center.</desc> | ||
| <g fill="#FFFFFF"> |
There was a problem hiding this comment.
On every non-home route this asset is rendered at only 1.75rem against the new #eceeef page surface, but its petals are plain white with no graphite stroke, yielding only about 1.16:1 contrast and leaving little more than the tiny plum center dots visible. The matching favicon already applies a graphite stroke to these paths; the shell asset needs the same treatment or another contrasting petal color for the blossom to remain recognizable.
Useful? React with 👍 / 👎.
1 participant
변경 사항
이유
블로그와 IDE 테마에 같은 브랜드 정체성을 적용합니다.
검증