Skip to content

doc: itk dashboard documentation#549

Open
kdziedzic70 wants to merge 1 commit into
mainfrom
dziedzick/dashboard-doc
Open

doc: itk dashboard documentation#549
kdziedzic70 wants to merge 1 commit into
mainfrom
dziedzick/dashboard-doc

Conversation

@kdziedzic70
Copy link
Copy Markdown
Contributor

Description

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

Fixes #<issue_number_goes_here> 🦕

Copy link
Copy Markdown
Contributor

@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 introduces a comprehensive technical guide for the A2A ITK Compatibility Dashboard, detailing its usage, data pipeline architecture, and contribution process. It also adds a 'Docs' link to the dashboard header with corresponding CSS styling. Review feedback suggests enhancing security by adding 'rel="noopener noreferrer"' to external links, using relative paths for internal repository references to improve portability, and ensuring version naming consistency within the documentation.

Comment thread itk-dashboard/index.html
<h1>A2A SDKs Compatibility</h1>
<h1>
A2A SDKs Compatibility
<a href="https://github.com/a2aproject/a2a-samples/blob/main/itk-dashboard/doc/README.md" target="_blank" class="doc-link" title="View Architecture & Interpretation Guide">Docs</a>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

security-low low

When using target="_blank", it is a security best practice to include rel="noopener noreferrer" to prevent the opened page from potentially accessing the original window object via window.opener.

Suggested change
<a href="https://github.com/a2aproject/a2a-samples/blob/main/itk-dashboard/doc/README.md" target="_blank" class="doc-link" title="View Architecture & Interpretation Guide">Docs</a>
<a href="https://github.com/a2aproject/a2a-samples/blob/main/itk-dashboard/doc/README.md" target="_blank" rel="noopener noreferrer" class="doc-link" title="View Architecture & Interpretation Guide">Docs</a>

### 3. Node Versioning
Inside the node rectangles in the topology graph:
* **`current`**: Corresponds to the latest development version built from the `main` branch of the SDK repository.
* **Tagged Versions (e.g., `python_v10`, `go_v03`)**: Corresponds to released historical versions of the SDKs.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

low

For consistency with the examples used elsewhere in the documentation (like go_v03 on line 39) and the actual project structure, consider using python_v03 instead of python_v10.

Comment thread itk-dashboard/doc/README.md Outdated
Comment on lines +66 to +75
* **Core Test Kit Runner & Mock Server**: [Core Test Kit](https://github.com/a2aproject/a2a-samples/tree/main/standalone-itk/itk/)
* Contains the central test runner, HTTP mock notification server, and scenario definitions.
* **Go SDK ITK Implementation**: [Go SDK Suite](https://github.com/a2aproject/a2a-samples/tree/main/standalone-itk-go/itk/)
* Code for verifying Go SDK interoperability.
* **Dashboard Code**: [Dashboard Code](https://github.com/a2aproject/a2a-samples/tree/main/itk-dashboard/)
* Static index page, stylesheets, and rendering scripts.

### How to Contribute
* **Adding a New Scenario**: Modify the scenario array inside [scenarios.json](https://github.com/a2aproject/a2a-samples/blob/main/standalone-itk/itk/scenarios.json).
* **Implementing a New SDK Launcher**: Read the [ITK Testing Framework Guide](https://github.com/a2aproject/a2a-samples/blob/main/standalone-itk/itk/README.md) and create a dedicated launcher for the target SDK that respects the isolation and mock notification standards.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

low

Consider using relative links (e.g., ../../standalone-itk/itk/) instead of absolute GitHub URLs for internal repository references. This makes the documentation more portable across forks and branches.

@kdziedzic70 kdziedzic70 force-pushed the dziedzick/dashboard-doc branch from 1c214c7 to 7c0ccd7 Compare May 8, 2026 08:23
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