feat(docs-site): complete landing page and docs redesign#42
Conversation
gehrig-netlify
commented
Jun 22, 2026
gehrig-netlify
commented
- New landing page matching Figma design — Digerati headings, Instrument Sans body, #f6f6f7 background
- Restyled docs pages — white bordered sidebar, unified nav card, dark code blocks
- New report-ui theme matching landing page design tokens
- Added Digerati font, AXIS SVG logo, OG image, updated favicon
- Agent scrolling marquee, founding contributors section (Auth0 + Netlify)
- Mobile responsive improvements throughout
- SEO: og:site_name, twitter:image:alt, theme-color, canonical, sitemap
✅ Deploy Preview for axisproject ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for axis-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
More reviews will be available in 55 minutes and 10 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (32)
📒 Files selected for processing (11)
📝 WalkthroughWalkthroughThe PR delivers two parallel workstreams. For the docs site, it adds React (plus framer-motion and type packages) as a new integration, configures JSX in tsconfig, introduces a Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/docs-site/src/pages/index.astro (1)
394-407:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winHandle clipboard write failures to prevent unhandled promise rejections.
The click handler only handles success; permission-denied/unsupported flows should be caught.
Proposed change
- navigator.clipboard.writeText(text).then(function () { + navigator.clipboard.writeText(text).then(function () { var prev = btn.getAttribute("aria-label"); btn.setAttribute("aria-label", "Copied!"); btn.classList.add("copied"); setTimeout(function () { btn.setAttribute("aria-label", prev || "Copy command"); btn.classList.remove("copied"); }, 1400); - }); + }).catch(function () { + // Optional: keep silent or surface lightweight UI feedback. + });🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/docs-site/src/pages/index.astro` around lines 394 - 407, The clipboard.writeText promise chain in the click event listener for .lp-step-copy buttons only handles the success case with .then() but does not handle failures. Add error handling by chaining a .catch() method to the navigator.clipboard.writeText() promise to gracefully handle cases where clipboard access is denied, not supported, or fails for any reason, preventing unhandled promise rejections.
🧹 Nitpick comments (1)
src/docs-site/src/pages/index.astro (1)
166-166: 🧹 Nitpick | 🔵 Trivial | ⚡ Quick winAvoid hydrating
DimensionCardson load when it has no client interactivity.
client:loadships client JS for a static section. Rendering it server-only here avoids unnecessary hydration cost.Proposed change
- <DimensionCards client:load /> + <DimensionCards />🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/docs-site/src/pages/index.astro` at line 166, The DimensionCards component is using the client:load directive which unnecessarily ships and hydrates client-side JavaScript for a static component that has no interactivity. Remove the client:load directive from the DimensionCards component so it renders server-only, eliminating the unnecessary hydration cost while maintaining the same functionality.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/docs-site/package.json`:
- Around line 11-18: The `@astrojs/react` dependency version ^5.0.7 is
incompatible with the currently specified Astro version ^5.7.10, as
`@astrojs/react` v5.x is designed for Astro v6. Update the `@astrojs/react` version
in the package.json to use v4.x instead, which is compatible with Astro v5.7.10,
while keeping all other dependencies as specified.
In `@src/docs-site/src/components/DimensionCards.tsx`:
- Around line 30-35: The DimensionCards.tsx component uses "Score" and "scores"
terminology in user-facing copy which conflicts with the documentation
guidelines that require "Result" and "results". Replace "Agent Experience Index
Score" with "Agent Experience Index Result" and change "AXIS scores" to "AXIS
results" in the eyebrow heading, section title, and descriptive text within the
component to align with the established wording guidelines.
In `@src/docs-site/src/pages/index.astro`:
- Around line 11-12: Update the user-facing landing page copy to use "AXIS
Result" terminology instead of "AXIS Score". In the title prop, change "AXIS —
Agent Experience Index Score" to use "AXIS Result" instead of "Score". In the
description prop, replace "0–100 score" with appropriate "AXIS Result"
terminology that aligns with the guidelines. Apply the same terminology updates
to all occurrences mentioned (also at line 40) to ensure consistent messaging
throughout the landing page.
In `@src/docs-site/src/styles/docs.css`:
- Line 2: The stylelint errors are caused by incorrect quoting in font-family
declarations and potentially incorrect keyword casing. Fix the
font-family-name-quotes error by replacing double quotes with single quotes
around font family names (e.g., change the "Digerati" declaration and all other
font-family declarations mentioned at lines 56, 280, 293, 1896-1898, 2012, 2392,
2484, 2660, 2709, and 2821). Additionally, review any CSS keyword values in
these same areas to ensure they follow lowercase convention as required by the
value-keyword-case rule. Apply these quote style and casing corrections
consistently across all flagged locations in the docs.css file.
In `@src/report-ui/src/styles/global.css`:
- Line 1767: The CSS selector targeting `.site-logo-mark` in the global.css file
needs to be updated to match the current SVG logo markup. Replace
`.site-logo-mark` with `.axis-logo` in the selector that also targets
`.report-badge` for the font-size rule. This ensures the mobile logo sizing
(1.5rem) is properly applied to the actual SVG logo class that is now rendered
in the header markup instead of the outdated class reference.
- Around line 3-50: In the global.css file, fix the stylelint violations in the
font declarations. For the font-family-name-quotes rule, ensure all font names
in the font-family values are wrapped in quotes, particularly in the :root CSS
variables where --font, --font-mono, and --font-display are defined. Generic
font families like monospace, sans-serif, system-ui and named fonts like
BlinkMacSystemFont, SFMono-Regular, Menlo, and Consolas all need to be quoted.
For the value-keyword-case rule, verify that all CSS keywords like normal, swap,
and woff are in lowercase. Apply these quotes and case corrections throughout
the `@font-face` block and the :root variable declarations to resolve the lint
errors.
- Around line 1353-1358: The deprecated `word-break: break-word` CSS property
appears in two locations in the file and both need to be updated for modern
browser compatibility. First, locate the `.sparse-line-content pre` selector and
replace `word-break: break-word;` with `word-break: normal;` followed by
`overflow-wrap: anywhere;` on separate lines. Second, apply the same replacement
to the modal prompt styles block (visible in the diff context with properties
like border, border-radius, padding, white-space, word-break, and max-height).
Both locations should use the modern `overflow-wrap: anywhere;` property
combined with `word-break: normal;` to ensure proper text wrapping behavior
across browsers.
---
Outside diff comments:
In `@src/docs-site/src/pages/index.astro`:
- Around line 394-407: The clipboard.writeText promise chain in the click event
listener for .lp-step-copy buttons only handles the success case with .then()
but does not handle failures. Add error handling by chaining a .catch() method
to the navigator.clipboard.writeText() promise to gracefully handle cases where
clipboard access is denied, not supported, or fails for any reason, preventing
unhandled promise rejections.
---
Nitpick comments:
In `@src/docs-site/src/pages/index.astro`:
- Line 166: The DimensionCards component is using the client:load directive
which unnecessarily ships and hydrates client-side JavaScript for a static
component that has no interactivity. Remove the client:load directive from the
DimensionCards component so it renders server-only, eliminating the unnecessary
hydration cost while maintaining the same functionality.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 1f18becd-d759-42df-bb59-48fa6948fbee
⛔ Files ignored due to path filters (32)
package-lock.jsonis excluded by!**/package-lock.jsonsrc/docs-site/public/AXIS_OG.pngis excluded by!**/*.pngsrc/docs-site/public/Digerati-Regular.woffis excluded by!**/*.woffsrc/docs-site/public/Header/AXIS.svgis excluded by!**/*.svgsrc/docs-site/public/agents/auggie.pngis excluded by!**/*.pngsrc/docs-site/public/agents/blackbox.pngis excluded by!**/*.pngsrc/docs-site/public/agents/claude.svgis excluded by!**/*.svgsrc/docs-site/public/agents/cline.svgis excluded by!**/*.svgsrc/docs-site/public/agents/codex.svgis excluded by!**/*.svgsrc/docs-site/public/agents/copilot.pngis excluded by!**/*.pngsrc/docs-site/public/agents/cursor.pngis excluded by!**/*.pngsrc/docs-site/public/agents/cursor.svgis excluded by!**/*.svgsrc/docs-site/public/agents/factorydroid.pngis excluded by!**/*.pngsrc/docs-site/public/agents/fastagent.pngis excluded by!**/*.pngsrc/docs-site/public/agents/gemini.svgis excluded by!**/*.svgsrc/docs-site/public/agents/goose.svgis excluded by!**/*.svgsrc/docs-site/public/agents/kilo.svgis excluded by!**/*.svgsrc/docs-site/public/agents/kimi.svgis excluded by!**/*.svgsrc/docs-site/public/agents/kiro.pngis excluded by!**/*.pngsrc/docs-site/public/agents/mistral.svgis excluded by!**/*.svgsrc/docs-site/public/agents/opencode.svgis excluded by!**/*.svgsrc/docs-site/public/agents/openhands.pngis excluded by!**/*.pngsrc/docs-site/public/agents/poolside.svgis excluded by!**/*.svgsrc/docs-site/public/agents/qoder.svgis excluded by!**/*.svgsrc/docs-site/public/agents/qwen.svgis excluded by!**/*.svgsrc/docs-site/public/agents/stakpak.pngis excluded by!**/*.pngsrc/docs-site/public/apple-touch-icon.pngis excluded by!**/*.pngsrc/docs-site/public/favicon-16x16.pngis excluded by!**/*.pngsrc/docs-site/public/favicon-32x32.pngis excluded by!**/*.pngsrc/docs-site/public/favicon.icois excluded by!**/*.icosrc/docs-site/public/logos/auth0.pngis excluded by!**/*.pngsrc/docs-site/public/logos/netlify.pngis excluded by!**/*.png
📒 Files selected for processing (11)
.gitignoresrc/docs-site/astro.config.mjssrc/docs-site/package.jsonsrc/docs-site/src/components/DimensionCards.tsxsrc/docs-site/src/layouts/DocsLayout.astrosrc/docs-site/src/pages/index.astrosrc/docs-site/src/styles/docs.csssrc/docs-site/tsconfig.jsonsrc/report-ui/src/pages/index.astrosrc/report-ui/src/scripts/render.tssrc/report-ui/src/styles/global.css
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
netlify/blueprints(manual)
| "@astrojs/react": "^5.0.7", | ||
| "@astrojs/sitemap": "^3.7.2", | ||
| "astro": "^5.7.10" | ||
| "@types/react": "^19.2.17", | ||
| "@types/react-dom": "^19.2.3", | ||
| "astro": "^5.7.10", | ||
| "framer-motion": "^12.40.0", | ||
| "react": "^19.2.7", | ||
| "react-dom": "^19.2.7" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Check TypeScript version and verify compatibility.
# Test 1: Display TypeScript version
npm list typescript || echo "TypeScript not found in node_modules; checking package.json..."
grep -A2 '"typescript"' src/docs-site/package.json || echo "TypeScript not explicitly listed in docs-site package.json"
# Test 2: Verify Astro and `@astrojs/react` in package.json for versions
echo "=== Checking Astro and `@astrojs/react` versions ==="
grep -E '(astro|`@astrojs/react`)' src/docs-site/package.json | grep -v '//'Repository: netlify/axis
Length of output: 1256
🏁 Script executed:
#!/bin/bash
# Get the actual docs-site package.json content
cat src/docs-site/package.json | head -30Repository: netlify/axis
Length of output: 499
🌐 Web query:
@astrojs/react v5.0.7 Astro 5 compatibility requirements
💡 Result:
The @astrojs/react v5.0.7 integration is designed for use with Astro v6, not Astro v5 [1][2]. While @astrojs/react v5.0.0 and above include major changes that align the integration with Astro v6, such as increased minimum Node.js version requirements (Node.js >= 22.12.0) and upgrades to support Vite 7.0 [2][3], they are not intended for use with the older Astro v5 ecosystem. If you are using Astro 5, you should use the corresponding v4.x versions of @astrojs/react [1][2]. Users on Astro 5 looking to upgrade their React integration should consult the specific migration documentation for the version of Astro they are running [4]. Projects currently on Astro 5 should not attempt to force usage of @astrojs/react v5.x, as it is architected for the requirements and dependencies of Astro 6 [2][3].
Citations:
- 1: https://npmjs.com/package/@astrojs/react
- 2: https://github.com/withastro/astro/releases/tag/@astrojs%2Freact@5.0.0
- 3: https://github.com/withastro/astro/blob/cbd7eb50b143e63f72677b77c83bf574d815092d/packages/integrations/react/CHANGELOG.md
- 4: https://docs.astro.build/en/guides/upgrade-to/v5/
Fix @astrojs/react version incompatibility with Astro v5.
The project targets Astro v5.7.10 but specifies @astrojs/react@^5.0.7, which is designed for Astro v6 and incompatible with Astro v5. For Astro v5, use @astrojs/react v4.x instead.
TypeScript 5.9.3 is installed and meets React 19's minimum requirement of TypeScript 5.9+.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/docs-site/package.json` around lines 11 - 18, The `@astrojs/react`
dependency version ^5.0.7 is incompatible with the currently specified Astro
version ^5.7.10, as `@astrojs/react` v5.x is designed for Astro v6. Update the
`@astrojs/react` version in the package.json to use v4.x instead, which is
compatible with Astro v5.7.10, while keeping all other dependencies as
specified.
| <div className="lp-eyebrow">Agent Experience Index Score</div> | ||
| <h2 className="lp-section-title">Four dimensions, one score.</h2> | ||
| <p className="lp-section-blurb"> | ||
| A single pass/fail tells you nothing about <em>why</em> an agent | ||
| struggled. AXIS scores four independent dimensions so you can focus on | ||
| what matters: a slow API, a confusing layout, a noisy tool, or the |
There was a problem hiding this comment.
Replace “Score/scores” wording with “Result/results” in user-facing copy.
This section still uses “Agent Experience Index Score” and “AXIS scores…”, which conflicts with the docs wording rule.
As per coding guidelines, use “AXIS Result” in all user-facing text, display output, and documentation instead of “AXIS Score.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/docs-site/src/components/DimensionCards.tsx` around lines 30 - 35, The
DimensionCards.tsx component uses "Score" and "scores" terminology in
user-facing copy which conflicts with the documentation guidelines that require
"Result" and "results". Replace "Agent Experience Index Score" with "Agent
Experience Index Result" and change "AXIS scores" to "AXIS results" in the
eyebrow heading, section title, and descriptive text within the component to
align with the established wording guidelines.
Source: Coding guidelines
| title="AXIS — Agent Experience Index Score" | ||
| description="AXIS is open source tooling and a scoring framework to measure how well services work for AI agents. Run real scenarios, get a 0–100 score, and fix what's slowing agents down." |
There was a problem hiding this comment.
Update landing copy to “AXIS Result” terminology.
The title/description still present “AXIS … Score” / “0–100 score” in user-facing text.
As per coding guidelines, use “AXIS Result” in all user-facing text, display output, and documentation instead of “AXIS Score.”
Also applies to: 40-40
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/docs-site/src/pages/index.astro` around lines 11 - 12, Update the
user-facing landing page copy to use "AXIS Result" terminology instead of "AXIS
Score". In the title prop, change "AXIS — Agent Experience Index Score" to use
"AXIS Result" instead of "Score". In the description prop, replace "0–100 score"
with appropriate "AXIS Result" terminology that aligns with the guidelines.
Apply the same terminology updates to all occurrences mentioned (also at line
40) to ensure consistent messaging throughout the landing page.
Source: Coding guidelines
| @@ -1,3 +1,11 @@ | |||
| @font-face { | |||
| font-family: "Digerati"; | |||
There was a problem hiding this comment.
Resolve Stylelint error-level violations before merge.
There are multiple font-family-name-quotes and value-keyword-case errors in changed lines; these will fail lint-gated pipelines.
Also applies to: 56-56, 280-280, 293-293, 1896-1898, 2012-2012, 2392-2392, 2484-2484, 2660-2660, 2709-2709, 2821-2821
🧰 Tools
🪛 Stylelint (17.13.0)
[error] 2-2: Expected no quotes around "Digerati" (font-family-name-quotes)
(font-family-name-quotes)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/docs-site/src/styles/docs.css` at line 2, The stylelint errors are caused
by incorrect quoting in font-family declarations and potentially incorrect
keyword casing. Fix the font-family-name-quotes error by replacing double quotes
with single quotes around font family names (e.g., change the "Digerati"
declaration and all other font-family declarations mentioned at lines 56, 280,
293, 1896-1898, 2012, 2392, 2484, 2660, 2709, and 2821). Additionally, review
any CSS keyword values in these same areas to ensure they follow lowercase
convention as required by the value-keyword-case rule. Apply these quote style
and casing corrections consistently across all flagged locations in the docs.css
file.
Source: Linters/SAST tools
| border: 1px solid var(--border-light); | ||
| border-radius: var(--radius); | ||
| padding: 12px 16px; | ||
| white-space: pre-wrap; | ||
| word-break: break-word; | ||
| max-height: 240px; |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify there are no remaining deprecated word-break values in report-ui CSS.
rg -n 'word-break:\s*break-word' src/report-ui/src/styles/global.cssRepository: netlify/axis
Length of output: 118
🏁 Script executed:
#!/bin/bash
# Check context around line 1212
echo "=== Context around line 1212 ==="
sed -n '1205,1220p' src/report-ui/src/styles/global.css
echo ""
echo "=== Context around line 1357 ==="
sed -n '1350,1365p' src/report-ui/src/styles/global.cssRepository: netlify/axis
Length of output: 873
🌐 Web query:
word-break: break-word deprecated CSS overflow-wrap alternative
💡 Result:
The CSS value word-break: break-word is officially deprecated [1][2][3]. It is maintained solely for legacy backward compatibility and should not be used in new style sheets [4][3]. The recommended alternative is the overflow-wrap property [2]. Specifically, word-break: break-word functions as an alias for overflow-wrap: anywhere [1][5][3]. Depending on your specific layout requirements, you should choose between the following overflow-wrap values: 1. overflow-wrap: anywhere: This is the modern, standard equivalent to the deprecated word-break: break-word [1][6]. It allows the browser to break an otherwise unbreakable string at any point to prevent overflow [7]. Importantly, it considers these forced break opportunities when calculating min-content intrinsic sizes, which often results in more predictable layout behavior for containers [8][7][3]. 2. overflow-wrap: break-word: This value also prevents overflow by allowing breaks in otherwise unbreakable strings [7]. However, unlike anywhere, it does not consider the soft wrap opportunities introduced by these breaks when calculating min-content intrinsic sizes [8][7][3]. In most modern use cases, overflow-wrap: anywhere is the preferred replacement because it handles intrinsic sizing more effectively than the legacy break-word behavior [5][6][3].
Citations:
- 1: https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/word-break
- 2: https://web-platform-dx.github.io/web-features-explorer/features/word-break-break-word/
- 3: https://www.w3.org/TR/css-text-3/
- 4: [css-text-3] Normatively disallow break-word w3c/csswg-drafts#4087
- 5: https://stackoverflow.com/questions/66724509/overflow-wrap-break-word-vs-word-break-break-word
- 6: https://stackoverflow.com/questions/17259916/difference-between-overflow-wrap-and-word-break
- 7: https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/overflow-wrap
- 8: https://github.com/mdn/content/blob/main/files/en-us/web/css/reference/properties/overflow-wrap/index.md
Address deprecated word-break: break-word values in two locations, not just line 1357.
The codebase contains two instances of the deprecated word-break: break-word value:
- Line 1212:
.sparse-line-content preselector - Line 1357: Modal prompt styles (as noted in the original comment)
Both should be updated to use the modern overflow-wrap: anywhere; property. The suggested replacement (word-break: normal; + overflow-wrap: anywhere;) is appropriate for cross-browser compatibility.
Required changes
At line 1212, replace:
- word-break: break-word;
+ word-break: normal;
+ overflow-wrap: anywhere;At line 1357, replace:
- word-break: break-word;
+ word-break: normal;
+ overflow-wrap: anywhere;📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| border: 1px solid var(--border-light); | |
| border-radius: var(--radius); | |
| padding: 12px 16px; | |
| white-space: pre-wrap; | |
| word-break: break-word; | |
| max-height: 240px; | |
| border: 1px solid var(--border-light); | |
| border-radius: var(--radius); | |
| padding: 12px 16px; | |
| white-space: pre-wrap; | |
| word-break: normal; | |
| overflow-wrap: anywhere; | |
| max-height: 240px; |
🧰 Tools
🪛 Stylelint (17.13.0)
[error] 1357-1357: Deprecated keyword "break-word" for property "word-break" (declaration-property-value-keyword-no-deprecated)
(declaration-property-value-keyword-no-deprecated)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/report-ui/src/styles/global.css` around lines 1353 - 1358, The deprecated
`word-break: break-word` CSS property appears in two locations in the file and
both need to be updated for modern browser compatibility. First, locate the
`.sparse-line-content pre` selector and replace `word-break: break-word;` with
`word-break: normal;` followed by `overflow-wrap: anywhere;` on separate lines.
Second, apply the same replacement to the modal prompt styles block (visible in
the diff context with properties like border, border-radius, padding,
white-space, word-break, and max-height). Both locations should use the modern
`overflow-wrap: anywhere;` property combined with `word-break: normal;` to
ensure proper text wrapping behavior across browsers.
Source: Linters/SAST tools
|
I don’t see Resend in the Founding Contributors list. Updated marquee of models looks nice. Only critique: Can we get rid of this extra vertical line? and this horizontal line? |
- New landing page matching Figma design — Digerati headings, Instrument Sans body, #f6f6f7 background - 3D spinning prism animation for the Four Dimensions section (Framer Motion) - Restyled docs pages — white bordered sidebar, unified nav card, dark code blocks - New report-ui theme matching landing page design tokens - Added Digerati font, AXIS SVG logo, OG image, updated favicon - Agent scrolling marquee, founding contributors section (Auth0 + Netlify) - Mobile responsive improvements throughout - SEO: og:site_name, twitter:image:alt, theme-color, canonical, sitemap Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sean-roberts
force-pushed
the
feat/docs-site-redesign
branch
from
f200f70 to
59ee5af
Compare
3 participants
