Skip to content

chore(docs): july update #208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
coryrylan merged 1 commit into from
Aug 4, 2026
+33 −0
Merged

chore(docs): july update #208

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions projects/site/src/docs/whats-new/07-2026.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
{
title: 'What’s new in NVIDIA Elements: July 2026',
description: 'July adds the Gauge component, expands design linting, and improves editor metadata, typography, and interactive component behavior.',
layout: 'whats-new.11ty.js',
tags: ['whats-new', 'updates'],
date: '2026-08-03',
datePublished: '2026-08-03',
dateModified: '2026-08-03',
updateMonth: '2026-07-01'
}
---

July makes dense telemetry interfaces easier to build and gives teams stronger guidance, metadata, and component behavior across the stack.

## Highlights

- **Visualize system metrics with Gauge.** The new [Gauge](/docs/elements/gauge/) component renders accessible progress values in 270-degree or half-circle shapes, with fill, dot, and needle indicators plus sizes, statuses, custom maximums, and gradient styling.
- **Catch design problems during linting.** [Elements lint rules](/docs/lint/) now flag excessive primary actions, labels that crowd form controls inside toolbars and page headers, and `container="full"` outside supported page-level positions. Framework event bindings and flexible gap values also avoid false positives.

@coderabbitai coderabbitai Bot Aug 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Make the lint-rule subject explicit.

The current sentence makes framework event bindings and flexible gap values the things that avoid false positives. Make the lint rules the subject.

Proposed wording 
-- Framework event bindings and flexible gap values also avoid false positives.
+- The rules also avoid false positives for framework event bindings and flexible gap values.

As per coding guidelines, Markdown documentation should follow the repository's technical writing style, including Google developer documentation style and write-good rules.

📝 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.

Suggested change
- **Catch design problems during linting.** [Elements lint rules](/docs/lint/) now flag excessive primary actions, labels that crowd form controls inside toolbars and page headers, and `container="full"` outside supported page-level positions. Framework event bindings and flexible gap values also avoid false positives.
- **Catch design problems during linting.** [Elements lint rules](/docs/lint/) now flag excessive primary actions, labels that crowd form controls inside toolbars and page headers, and `container="full"` outside supported page-level positions. The rules also avoid false positives for framework event bindings and flexible gap values.
🤖 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 `@projects/site/src/docs/whats-new/07-2026.md` at line 19, Revise the “Catch
design problems during linting” bullet so the lint rules are explicitly the
subject of the final sentence, making clear that they avoid false positives for
framework event bindings and flexible gap values. Preserve the existing list of
newly flagged patterns and the documentation link.

Source: Coding guidelines

- **Get better editor and framework metadata.** Published HTML custom data now links components to their documentation, Markdown exposes its custom-data entry point, and Core generates clearer property, attribute, slot, JSX, and Vue declarations.
- **Make type and layout predictable.** [Typography utilities](/docs/foundations/typography/) add `nve-text="grow"` for fitting content, set sensible default line heights, and improve inline code and links. Logical spacing and full-width, space-between rows make layouts more consistent across directions.
- **Keep interactive controls steady.** [Tooltips](/docs/elements/tooltip/) now hand off cleanly when the same trigger opens an interactive popover. Form controls remove stale ARIA values and reset native defaults, drawers adhere to viewport edges, sized selects fit exact visible rows, and repeated connections no longer duplicate observers.

## Released packages

- `@nvidia-elements/cli` 2.1.4–2.1.9
- `@nvidia-elements/code` 2.0.2
- `@nvidia-elements/core` 2.0.3–2.0.4, 2.1.0–2.1.6, 2.2.0–2.2.2
- `@nvidia-elements/forms` 2.0.2–2.0.5
- `@nvidia-elements/lint` 2.1.0–2.1.3, 2.2.0, 2.3.0
- `@nvidia-elements/markdown` 2.0.2–2.0.3
- `@nvidia-elements/monaco` 2.0.2
- `@nvidia-elements/styles` 2.1.0–2.1.2