-
Notifications
You must be signed in to change notification settings - Fork 276
DOC-5945 first attempt at some AI metadata #2397
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
Conversation
…iles (517 files)" This reverts commit e52e337.
dwdougherty
left a comment
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.
No idea what any of this does, but I'll approve anyway. 🤷🏻♂️
|
@dwdougherty Thanks! If you want to have a play with this, try directing Augie or ChatGPT specifically to the staging page for a command and then based on that, ask for some detail about the command (complexity or arguments, etc). You'll probably get a quick answer, or it sometimes even gives you a load of detail just from being directed to the page. Also, if you add the |
|
I just don't feel that ambitious. 🫠 |
|
@dwdougherty Yeah, Friday is not the time for adventure :-) |
|
Thanks @paoloredis and @dwdougherty ! |
AI can benefit from some of the metadata that we already have in the doc pages. Even the simple stuff like
categoriesis useful, but the command pages have really helpful stuff that makes the syntax of commands much easier to parse. This is just a first attempt based on what we've already got in the page sources, but once the system is in place, we might try adding some new metadata fields to the page Markdown.All feedback welcome! There's probably a lot more we can do to refine this.