Updated the documentation logo and replaced the favicon with the chevron mark. - #158
Merged
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (6)
📒 Files selected for processing (1)
Comment |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #158 +/- ##
=======================================
Coverage 98.05% 98.05%
=======================================
Files 150 150
Lines 6054 6054
=======================================
Hits 5936 5936
Misses 118 118 ☔ View full report in Codecov by Harness. |
AlexSkrypnyk
added
the
Needs review
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
1 participant
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.
Summary
The documentation site's logo was replaced with the new PHPTUI wordmark, widening the SVG viewBox from
0 0 307 101to0 0 541 106and redrawing every letter path while keeping the existing colour-scheme-aware mechanism intact. The favicon moved off that same wordmark SVG, which is unreadable at 16px, onto a dedicatedfavicon.icobuilt from the teal chevron mark, with PNG and Apple touch icon variants declared through explicit<link>tags. The social card was regenerated so its baked-in logo matches the new paths.Changes
Logo
docs/static/img/logo.svgupdated to the new wordmark (viewBox0 0 541 106), taken from the repository rootlogo-light.svg/logo-dark.svg. Every letter path keepsclass="tui-letter", defaulting to#E6E2D6and flipping to#1A1D23under aprefers-color-scheme: lightmedia query, so the colour-scheme-aware mechanism carries over unchanged.Favicon
docs/docusaurus.config.js:faviconmoved fromimg/logo.svg(the full wordmark, unreadable at 16px) toimg/favicon.ico(the teal chevron mark).headTagsblock declaring the 32x32 and 16x16 PNG icons and the Apple touch icon as explicit<link>tags, since those files live under/img/rather than the site root a browser probes by default.docs/static/img/:favicon.ico,favicon-32x32.png,favicon-16x16.png,apple-touch-icon.png.Social card
docs/assets/social-card.pngregenerated withphp docs/util/render-social-card.php. That script inlinesdocs/static/img/logo.svgand forces.tui-letterto cream, so the card went stale the moment the logo paths changed underneath it.Screenshots
docs/assets/social-card.pngin this diff is itself the regenerated visual - see the binary change to that file above. The logo and favicon were verified rendered in both colour schemes on the running docs site: all four icon<link>tags were confirmed present in the hydrated DOM, and every icon file served 200 with the correct content type.Before / After