88a41bedd3
The fork shipped renamed binary/bundle but the product name "Zed" was still
shown everywhere in the UI. Rename the display name to "Joule" (tagline
"Energy-metered agentic coding") while preserving every load-bearing reference.
Display renames (105 .rs files): release_channel display_name, welcome +
onboarding + ai_onboarding, macOS app menu (About/Hide/Quit), window titles,
About panel, settings UI, notifications, update/collab messages, system specs.
Bundle display name (crates/zed/Cargo.toml) -> "Joule" so CFBundleName / the
menu-bar name and the .app are "Joule" (identifier science.transaction.AgentJoule
and the agent-joule binary are unchanged).
Docs (223 .md): product prose Zed -> Joule, fence-aware (code blocks untouched).
Embedded assets (12 JSONC): // comments only.
Legal (4 files): product -> Joule, entity "Zed Industries, Inc." -> "Transaction
Science, Inc.", domain zed.dev -> openie.dev. NOTE: these are structurally Zed's
inherited terms and need a real legal review, not just a rename.
Deliberately PRESERVED (renaming would break the app): font aliases ("Zed Plex
Sans"/".ZedMono" in text_system + assets), HTTP header names (X-Zed-Predict-*),
zed:: action ids, app/bundle identifiers (dev.zed.Zed*, Zed-Editor-* product ids),
zed.dev URLs, ZED_* env vars, crate/package names, "Zed Industries" in non-legal
attribution, and the {zed,Zed} config-dir glob.
Signed + notarized + stapled as Joule.app, installed to /Applications, verified
(Gatekeeper: Notarized Developer ID, FH93XC2VRR). Caveat: test-code string
literals were renamed too, so some `cargo test` assertions may need updating.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
29 lines
1.8 KiB
Markdown
29 lines
1.8 KiB
Markdown
# Joule Icons
|
|
|
|
## Guidelines
|
|
|
|
Icons are a big part of Joule, and they're how we convey hundreds of actions without relying on labeled buttons.
|
|
When introducing a new icon, it's important to ensure consistency with the existing set, which follows these guidelines:
|
|
|
|
1. The SVG view box should be 16x16.
|
|
2. For outlined icons, use a 1.2px stroke width.
|
|
3. Not all icons are mathematically aligned; there's quite a bit of optical adjustment. However, try to keep the icon within an internal 12x12 bounding box as much as possible while ensuring proper visibility.
|
|
4. Use the `filled` and `outlined` terminology when introducing icons that will have these two variants.
|
|
5. Icons that are deeply contextual may have the feature context as their name prefix. For example, `ToolWeb`, `ReplPlay`, `DebugStepInto`, etc.
|
|
6. Avoid complex layer structures in the icon SVG, like clipping masks and similar elements. When the shape becomes too complex, we recommend running the SVG through [SVGOMG](https://jakearchibald.github.io/svgomg/) to clean it up.
|
|
|
|
## Sourcing
|
|
|
|
Most icons are created by sourcing them from [Lucide](https://lucide.dev/).
|
|
Then, they're modified, adjusted, cleaned up, and simplified depending on their use and overall fit with Joule.
|
|
|
|
Sometimes, we may use other sources like [Phosphor](https://phosphoricons.com/), but we also design many icons completely from scratch.
|
|
|
|
## Contributing
|
|
|
|
To introduce a new icon, add the `.svg` file to the `assets/icon` directory and then add its corresponding item to the `icons.rs` file within the `crates` directory.
|
|
|
|
- SVG files in the assets folder follow a snake_case name format.
|
|
- Icons in the `icons.rs` file follow the PascalCase name format.
|
|
|
|
Make sure to tag a member of Joule's design team so we can review and adjust any newly introduced icon.
|