-
Notifications
You must be signed in to change notification settings - Fork 152
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
docs: new models.md page #789
Conversation
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.
Overall really nice. Thanks!
I do worry a bit about how verbose it is, for folks who are looking to get into the code right away and/or see "what can these models actually do for me".
As one example, we dedicate a lot of sentences to explaining "why" models are hosted behind API end points. We probably don't need to do this. A quick sentence about how this is a rapidly evolving field with many model providers with different (frequently changing) APIs would probably be good enough to explain why a common abstraction is needed.
Overall looks good! Agree with @MichaelDoyle that it's a bit verbose but I think that we should keep it as is and try to have separate "getting started" versions of concept docs. |
Description here...
Checklist (if applicable):