Skip to content

docs: wrap package names in backticks instead of bold formatting #1245

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 20, 2025

Conversation

christian-bromann
Copy link
Contributor

🐛 Problem Solved

The documentation system was incorrectly interpreting the bold-formatted package names as markdown links, attempting to navigate to non-existent pages. This created broken links and a poor user experience when users clicked on what appeared to be clickable package names.

Screenshot 2025-05-30 at 4 00 12 PM

🔧 Changes Made

  • Updated package name formatting in examples/quickstart.ipynb
  • Changed bold formatting (**package**) to inline code formatting (**package**) for:
    • @langchain/langgraph
    • @langchain/openai
    • @langchain/community

Solution

By wrapping the package names in backticks within the bold formatting (**package**), we:

  • Maintain the visual emphasis of the package names
  • Prevent them from being interpreted as links
  • Follow proper markdown conventions for code/package references
  • Improve the overall documentation experience

📍 Files Changed

  • examples/quickstart.ipynb - Updated package name formatting in the dependencies section

- Changed **@langchain/langgraph** to **`@langchain/langgraph`**
- Changed **@langchain/openai** to **`@langchain/openai`**
- Changed **@langchain/community** to **`@langchain/community`**

This prevents the documentation system from interpreting these package
names as links to non-existent pages while maintaining proper code
formatting for package references.
@dqbd dqbd merged commit 62a383d into langchain-ai:main Jun 20, 2025
@christian-bromann christian-bromann deleted the cb/quickstart-fix branch June 20, 2025 16:21
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.

2 participants