Skip to content

🎨 Palette: [UX improvement] Enhance README for accessibility and DX#35

Open
Igor Holt (igor-holt) wants to merge 1 commit into
mainfrom
palette/readme-ux-enhancements-9694488231638940670
Open

🎨 Palette: [UX improvement] Enhance README for accessibility and DX#35
Igor Holt (igor-holt) wants to merge 1 commit into
mainfrom
palette/readme-ux-enhancements-9694488231638940670

Conversation

@igor-holt
Copy link
Copy Markdown
Member

This PR introduces micro-UX and accessibility improvements to the project's primary interface: the README.

💡 What:

  1. High-Visibility Status: Replaced the "Experimental" badge with a GitHub-native [!CAUTION] alert block to ensure users are immediately aware of the project's maturity.
  2. Visual Architecture: Added a Mermaid diagram illustrating the relationship between Cloud Native, Orchestration (Arbiter), and Infrastructure layers.
  3. Badge Accessibility: Added descriptive alt-text and title attributes to the License badge.

🎯 Why:

For infrastructure projects, the documentation is the primary User Experience. These changes reduce cognitive load for new developers and ensure critical status information is accessible and highly visible.

♿ Accessibility:

  • Added alt-text that describes the license type rather than just saying "License".
  • Added title attribute to provide a tooltip on hover.
  • Used a semantic alert block for the project status.

PR created automatically by Jules for task 9694488231638940670 started by Igor Holt (@igor-holt)

- Replace experimental badge with a high-visibility `[!CAUTION]` alert.
- Add Mermaid architecture diagram to visualize system components.
- Improve badge accessibility with descriptive alt-text and titles.

Co-authored-by: igor-holt <125706350+igor-holt@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the README.md to include a cautionary warning about the project's experimental status and adds a Mermaid diagram illustrating the system architecture. A review comment suggests improving accessibility by providing a text-based description of the diagram for screen reader users.

Comment thread README.md
Comment on lines +16 to +40
```mermaid
graph TD
subgraph CloudNative [Cloud Native]
K8s[Kubernetes]
Workloads[AI Workloads]
end

subgraph Orchestration [Orchestration]
Arbiter((Arbiter Core))
Scheduler[Quantum Scheduler]
end

subgraph Infrastructure [Infrastructure]
BareMetal[Bare Metal]
VRAM[aSHARD VRAM Pinning]
end

Workloads --> K8s
K8s --> Arbiter
Arbiter --> Scheduler
Arbiter --> VRAM
VRAM --> BareMetal

style Arbiter fill:#f96,stroke:#333,stroke-width:4px
```
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

While the Mermaid diagram significantly improves the visual architecture overview, it may not be fully accessible to users relying on screen readers. Since accessibility is a key goal of this PR, consider adding a brief text-based description or a nested list below the diagram to describe the relationships and flow. This ensures that the architectural information is available to all users, even if the diagram fails to render or for users with visual impairments.

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.

1 participant