Skip to content

docs: fix recipe and study links#29

Open
tianrking wants to merge 1 commit into
Nutlope:mainfrom
tianrking:agent/fix-docs-relative-links
Open

docs: fix recipe and study links#29
tianrking wants to merge 1 commit into
Nutlope:mainfrom
tianrking:agent/fix-docs-relative-links

Conversation

@tianrking

Copy link
Copy Markdown

Summary

Fix repository-relative links in the Hallmark recipes and study examples.

Root cause

The documentation files live under docs/, but their links still used paths
from their former location. As a result, the recipes index, eight live examples,
the skill references, and the study protocol link resolved outside the repository
or to a nonexistent file.

Validation

  • Ran a relative-link check across docs/; all local Markdown targets resolve.
  • Ran git diff --check.

@vercel

vercel Bot commented Jul 16, 2026

Copy link
Copy Markdown

@tianrking is attempting to deploy a commit to the Together AI Team on Vercel.

A member of the Team first needs to authorize it.

@riju568

riju568 commented Jul 16, 2026

Copy link
Copy Markdown
  1. PR Description - Scroll up to the first comment box. In general, the person opening the pull request (Nutlope, in this case) has a description of what the issue is, what solution is being offered, and usually a "Why" or "Context" section.

  2. Files changed Tab : Click on the "Files changed" tab. By looking at the code changes (the diffs), you can usually tell what exactly is being refactored, fixed or added.

  3. Conversation / Comments Below the description you can see the conversation of the PR. If the PR was created to close/fix an issue you will also see something like "Closes #..." or "Fixes #..." - which links to the corresponding issue report where the problem is described.

  4. Commits : Visit the “Commits” tab to check the commit messages of each of them. You will see a chronological sequence on the problem-solving path.

@tianrking
tianrking marked this pull request as ready for review July 16, 2026 04:55

@rajpratham1 rajpratham1 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thanks for the contribution! The updated relative links look consistent and improve the documentation by ensuring references point to the correct locations after the project structure changes.

The changes are documentation-only, easy to verify, and improve the user experience without affecting functionality.

Looks good to me. Thanks!

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.

3 participants