-
Notifications
You must be signed in to change notification settings - Fork 23
add llms.txt file #182
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
base: main
Are you sure you want to change the base?
add llms.txt file #182
Conversation
✅ Deploy Preview for positron-posit-co ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| @@ -0,0 +1,56 @@ | |||
| # Positron | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AshleyHenry15 do you have any suggestions on best practices for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have one on the docs site that we are using already, and I was running it through evaluations to see if it was actually helping/successful or if it was actually making things worse.
This is something that I spoke with Joe C about a while back and since this type of thing is so new, it is hard to gauge the "right way" to write the txt file and measure its success. For example, I read that you actually have to tell the LLMs to look for the file for it it utilize the file. IDK if that is still the case but if it is, it is basically "useless" unless a user knows that it exists on the site.
I would recommend pausing this PR and look into running it through evals first.
Here is a link to our file: https://docs.posit.co/llms.txt
Do you want to have a quick meeting to chat about the evals?
(I actually have it on my backlog to test out what Stripe is doing with the button for "llm" and the markdown link to add on the docs site to see if it is beneficial enough to explore for product docs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TY for the reply I'll add this as the agenda for our next sync! Will put this back into draft for now
|
TODO: find some best practices to update using this guide https://llmstxt.org/ |
We have seen an increase in traffice from AI sources like chat gpt
Allow AI agents to easily crawl positron site to be more discoverable to llms following best practices defined here https://llmstxt.org/
TODO
[ ] Can we automate adding new pages to this file like a robots.txt file