Skip to content

Use explicit 3.0 version in logo - #297

Open
camillobruni wants to merge 2 commits into
WebKit:mainfrom
camillobruni:2026-03-25_update_logo
Open

camillobruni wants to merge 2 commits into
WebKit:mainfrom
camillobruni:2026-03-25_update_logo

Conversation

@camillobruni

@camillobruni camillobruni commented Mar 25, 2026 •

Copy link
Copy Markdown
Contributor

This makes it easier to spot minor fixes in the future.

  • Add resources/JetStreamLogo.src.svg as editable svg
  • Exported new logo to resources/JetStream30Logo.svg

@netlify

netlify Bot commented Mar 25, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for webkit-jetstream-preview ready!

Name Link
🔨 Latest commit f15017d
🔍 Latest deploy log https://app.netlify.com/projects/webkit-jetstream-preview/deploys/6aeb974bb6bb376ad46a3c17
😎 Deploy Preview https://deploy-preview-297--webkit-jetstream-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@danleh danleh 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.

LGTM with nit. Lets also update the main branch afterwards (this PR goes to the 3.0 branch directly)

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.

tiny typography nit: Could you very slightly reduce the letter spacing around the . in 3.0?

@kmiller68

Copy link
Copy Markdown
Contributor

I don't have super strong feelings about this but one downside is that incremental updates require touching up the logo. I kinda prefer the paragraph at the top so we can quickly roll out the number.

@camillobruni

Copy link
Copy Markdown
Contributor Author

It would be in sync with speedometer where we did the same change (though the "logo" is just text):

It would just eliminate an easy source of error if we ever do an incremental dot-release.

@kmiller68

Copy link
Copy Markdown
Contributor

It would just eliminate an easy source of error if we ever do an incremental dot-release.

What easy source of error are you thinking? That we copy the wrong branch?

I guess I'd prefer to make this change in 3.1 (if needed).

@camillobruni

Copy link
Copy Markdown
Contributor Author

Mostly about accidentally using the wrong minor version without noticing since the log doesn't feature the number immediately. It's a bit less of an issue with jetstream since it does mention the minor version in the text.

In the past these two were pretty easy to confuse (since it's only in the tab title).

@camillobruni
camillobruni force-pushed the 2026-03-25_update_logo branch 3 times, most recently from 7512beb to de004c2 Compare November 4, 2026 17:47
@camillobruni
camillobruni changed the base branch from JetStream3.0 to main November 4, 2026 17:47
@camillobruni
camillobruni force-pushed the 2026-03-25_update_logo branch from de004c2 to f15017d Compare November 4, 2026 20:36
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.

3 participants