Improve how hero headline hyphenated compound words render#388
Merged
Conversation
✅ Deploy Preview for positron-posit-co ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A followup to #384
The homepage headline ("The data science IDE. Human-driven, AI-assisted.") wrapped awkwardly at most widths. Because a hyphen is a valid line-break point, the browser would split hyphenated compounds mid-word (e.g. "AI-" / "assisted"), and the break landed inconsistently.
This PR:
<br>, so the H1 reads as two clean lines: "The data science IDE." / "Human-driven, AI-assisted.".nowrapspans (with a newwhite-space: nowraprule scoped to.index-section h1) so those compounds never split mid-word, including when the second sentence wraps on narrow mobile screens.The H1 sits above the profile-specific content blocks, so this applies to both the public and Workbench builds.
Here's what we'll have after this change for big screens:
For little screens: