oktanaut blog #1470
oktanaut blog #1470
Conversation
✅ Deploy Preview for okta-blog ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| {% img blog/okta-documentation-chatbot/api.jpeg alt:"api-image" height:"400" %}{: .center-image } | ||
| – Image source: <cite>[OpenAI APIs with Python — Complete Guide](https://medium.com/@marc.bolle/openai-apis-with-python-complete-guide-d933fb770f95)</cite> | ||
|
|
||
| The second version took a different approach. Using LLamaIndex, I crafted a custom chatbot exclusively trained on the Okta developer documentation. While this version's responses were more accurate due to its focused training, it needed to be more comprehensive in handling a diverse range of questions compared to the GPT-3.5-powered counterpart. |
There was a problem hiding this comment.
Please make sure to link LlamaIndex, and is the capitalization of Okta developer documentation correct for our brand? (idk)
There was a problem hiding this comment.
so you are suggesting changing Okta developer documentation to Okta Developer Documentation?
There was a problem hiding this comment.
I think the suggestion is to check the style guides linked from https://docs.google.com/document/d/1GjvQQoJJLy4bJIS9Yk5vyzy9tnxDcKcMJ1-yqc-Z-f8/edit. https://github.com/okta/okta-developer-docs/wiki/Style-Guide demonstrates that we do capitalize Dev Docs.
There was a problem hiding this comment.
(why yes i did just search our google drive for "style guide" and grab the first promising-looking link there lol)
Co-authored-by: Alisa <[email protected]>
Co-authored-by: Alisa <[email protected]>
|
Would you be ok with "how I built" instead of "how to build"? "how to" suggests a more comprehensive guide whereas this is a nice focused writeup on one of the many possible ways to solve the problem. |
Co-authored-by: Alisa <[email protected]>
Co-authored-by: E. Dunham <[email protected]>
Co-authored-by: E. Dunham <[email protected]>
…cumentation-chatbot.md
This blog post has the following features: