Repository navigation
docs: add @heydeacon/docusaurus-plugin to community resources - #12755
AndrewCathcart wants to merge 1 commit into
Conversation
|
Hi @AndrewCathcart! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
✅ [V2]Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Filled out the CLA 👍🏻 |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
|
Just double checking if i need to do anything else here @slorber / @Josh-Cena ? Appreciate your time! Thanks |
Pre-flight checklist
Motivation
I'm one of Deacon's founders. We published a small MIT plugin, @heydeacon/docusaurus-plugin, that adds our chat widget to every docs page through
injectHtmlTags. This adds it to the AI / Agents list, next to the other support widget plugin there.Test Plan
Docs only: one line added to the end of the AI / Agents list in
website/community/2-resources.mdx, in the same format as the entries around it.The plugin has its own tests, and I checked it in a fresh Docusaurus 3.10 site: the build puts one script tag on every page, and the widget keeps working across client-side navigation.
Related issues/PRs
None.
Summary by CodeRabbit