-
Notifications
You must be signed in to change notification settings - Fork 361
[Docs] Remove kapa AI button #2849
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
|
Do we need to update docusaurus while we’re disabling kapa ai? Also I don’t follow the description, e.g:
How does that improve clarity or extensibility? Is it the GitHub „summarize changes” feature? I’ve noticed these automated descriptions are mostly noise. The „files changed” tab already tells us which files changed and how, duplicating that information in the description doesn’t add much and it distracts from the problem this PR solves. The description is a form of documentation. We have all the context today, but in a few months we’ll forget. Or a new person will join who never had the context in the first place. Let’s spell out the obvious, explain design choices, and avoid merely rewriting the diff with words. The description here could be just:
It would answer the important question: what are we changing, why, and is it permanent. The AI won’t ever get that from the code. |
|
btw I don't see the error in the docs anymore – are we good? https://wordpress.github.io/wordpress-playground/blueprints/steps/#EnableMultisiteStep |
|
@adamziel, I can split into two different tasks. We need to check with the Kapa AI team if the tool is still available. |
|
@fellyph I've brushed up the description and merged. This seems like a good change, I was just confused by the description as I wasn't sure why we update Docusaurus—e.g. is something failing on the older version. It seems like an optional change that helps us without breaking other things so let's get it in. |
|
It seems like this PR did not fix the issue: https://wordpress.github.io/wordpress-playground/api/blueprints/interface/EnableMultisiteStep/#Index |
|
Yes, I was thinking that was cache. On my tests on Saturday, it was working. I will pull back the button and do more investigation |
Removes kapa AI button from the Playground doc site – it triggers a React error here:
This is a temporary measure to fix the documentation page until the error is figured out—assuming we continue with Kapa AI (it's a free trial).
This PR also updates the Docusaurus version from
3.8.1to3.9.2. It doesn't seem strictly necessary but was a low-hanging fruit to co-locate with this PR.Testing instructions
Build the doc site locally, confirm there's no error at
/wordpress-playground/api/blueprints/interface/EnableMultisiteStep/#Index