Skip to content

FEE-823 Make BRAT repository URLs copyable on installation docs page#1122

Open
jsmorabito wants to merge 3 commits into
mainfrom
update-brat-url-copyable
Open

FEE-823 Make BRAT repository URLs copyable on installation docs page#1122
jsmorabito wants to merge 3 commits into
mainfrom
update-brat-url-copyable

Conversation

@jsmorabito

@jsmorabito jsmorabito commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Wraps both BRAT repository URLs in fenced code blocks so Nextra renders a copy button on hover
  • Enables defaultShowCopyCode: true in the Nextra config (applies site-wide to all docs code blocks)
  • Updates step text to "Enter the repository URL below and choose 'Latest version'"

Test plan

  • Visit /docs/obsidian/welcome/installation and hover over both repository URL code blocks — copy button should appear
  • Verify steps 5 and 6 still render correctly after each code block
  • Spot-check other docs pages to confirm copy buttons appear on existing code blocks

🤖 Generated with Claude Code


Open in Devin Review

jsmorabito and others added 3 commits June 10, 2026 13:24
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Wrap both repo URLs in fenced code blocks so Nextra renders a copy button
- Enable defaultShowCopyCode site-wide in nextra config
- Update step text to "Enter the repository URL below and choose Latest version"

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

You don't have permission to create a Preview Deployment for this Vercel project: discourse-graph.

View Documentation: https://vercel.com/docs/accounts/team-members-and-roles

@supabase

supabase Bot commented Jun 10, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project zytfjzqyijgagqxrzbmz because there are no changes detected in packages/database/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@jsmorabito jsmorabito changed the title Make BRAT repository URLs copyable on installation docs page FEE-823 Make BRAT repository URLs copyable on installation docs page Jun 10, 2026
@linear-code

linear-code Bot commented Jun 10, 2026

Copy link
Copy Markdown

FEE-823

@devin-ai-integration devin-ai-integration Bot left a comment

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.

Devin Review found 2 potential issues.

View 1 additional finding in Devin Review.

Open in Devin Review

<footer className="mt-12 border-t border-neutral-light/10 bg-neutral-dark px-6 py-6">
<div className="mx-auto flex max-w-6xl items-center justify-between">
<p className="text-secondary">
<p className="text-orange-500">

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.

🟡 Hardcoded text-orange-500 bypasses the design system color tokens

The footer copyright text was changed from text-secondary (#5F57C0) to text-orange-500 (#f97316), a raw Tailwind utility color. The shared tailwind config (packages/tailwind-config/tailwind.config.ts) defines design tokens (primary: #FF8C4B, secondary: #5F57C0), and the entire codebase consistently uses these tokens (e.g., text-primary, text-secondary). This is the only usage of text-orange-500 in the website app, violating the AGENTS.md rule to "Maintain visual consistency with the host application's design system." If the intent was to use an orange color, text-primary should be used instead.

Suggested change
<p className="text-orange-500">
<p className="text-primary">
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Comment on lines +26 to +28
```
https://github.com/blacksmithgu/datacore
```

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.

🚩 Markdown list continuity broken by unindented code blocks

The refactored installation instructions place the code blocks (lines 26-28 and 43-45) at the root indentation level rather than indented under list item 4. In CommonMark, this breaks the ordered list into two separate lists (items 1-4, then a new list starting at 5). Visually the numbers still render as 5 and 6 because CommonMark respects the starting number, so the user-facing impact is minimal. However, the list semantics are broken, and some renderers may add extra spacing between the two lists. Indenting the code blocks by 4 spaces (or 3 to match the list prefix width) would keep them as part of list item 4 and maintain a single continuous list.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

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