Docs site improvements: getting started, chaining operations, and UX enhancements#112
Conversation
- Convert plain text to proper ordered/unordered lists - Add working links to installation and API reference pages - Add CSS styles for lists in the quickstart section Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Basic example - Sessions: what they are, dashboard visibility, explicit sessions - Getting session URLs for monitoring - Async operations with _async variants - Crash recovery with fetch_task_data Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- ChainedOpsTabs component with 5 arrow-shaped tabs - CSS using clip-path for chevron/arrow effect - Placeholder content for each step Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Larger/bolder text for active tab - Subtle scale-up on hover for inactive tabs - Pulse animation on next tab after switching (draws eye forward) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Avoids confusion with the 'Getting Started' page having the same name as its parent section. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The sidebar section is named "Overview" to avoid redundancy with the "Getting Started" page, but the landing page card should still display "Getting Started" as the user-facing title. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
| button.addEventListener("click", async () => { | ||
| const code = pre.textContent || ""; | ||
| await navigator.clipboard.writeText(code); |
There was a problem hiding this comment.
Bug: The call to navigator.clipboard.writeText() lacks error handling, which can lead to an unhandled promise rejection and misleading UI feedback if the copy operation fails.
Severity: MEDIUM
Suggested Fix
Wrap the await navigator.clipboard.writeText(text) call in a try-catch block. The catch block should handle the potential rejection gracefully, for instance by reverting the button icon to its original state to provide accurate user feedback.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: docs-site/src/components/CodeBlockEnhancer.tsx#L29-L31
Potential issue: The `navigator.clipboard.writeText()` call is not wrapped in error
handling. If the clipboard API call fails, such as when a user denies permission, it
will cause an unhandled promise rejection. While this will not crash the application,
the UI will incorrectly display a success checkmark even on failure, providing
misleading feedback to the user. The unhandled rejection may also be logged to
configured analytics services.
Did we get this right? 👍 / 👎 to inform future reviews.
dschwarz26
left a comment
There was a problem hiding this comment.
While we're here, can we copy over the font contentions from the delphos repo, and get the jetbrains-mono font (and lowercase "everyrow" in the top left) that we see at the top of everyrow.io?
|
I've added a ticket to track the remaining stuff mentioned above |
Summary
Chaining Operations highlights
Test plan
/getting-started,/chaining-operations,/installation🤖 Generated with Claude Code