Add docusaurus

[TheJuanAndOnly99]

#133 This PR adds Docusaurus v3.

[netlify]

✅ Deploy Preview for lucky-concha-f3599f ready!

Name	Link
🔨 Latest commit	1eaae47
🔍 Latest deploy log	https://app.netlify.com/sites/lucky-concha-f3599f/deploys/663e1fa4682a450008dd4a37
😎 Deploy Preview	https://deploy-preview-138--lucky-concha-f3599f.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[psmulovics]

@mimiflynn, FYI

[linux-foundation-easycla]

• ✅ login: TheJuanAndOnly99 / name: Juan Estrella (1b3b303, 5ceb7fe, 2d5d63a, 6ca23ff, 8d2eda6, 1eaae47, b60e4fb)
• ❌ The email address for the commit (ed1c8a4) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[psmulovics]

@TheJuanAndOnly99 , we tried quite a few combination of this - and ended up just by using /bin/false . If you figure out a working setup (that works for the draft pages too and for normal, etc), I am super interested.

[TheJuanAndOnly99]

Hi @psmulovics not sure I understand what you mean by draft vs normal pages. The objective here is to only run Netlify on PRs that contain changes to the docs and website folders.

[maoo]

@DovOps @rocketstack-matt - could you please review this PR, so we can move forward with the merge?

[rocketstack-matt]

@DovOps @rocketstack-matt - could you please review this PR, so we can move forward with the merge?

Is the intent just to get the docs project in the build, as obviously the docs themselves are missing other than the front page? If so the setup looks fine to me, but I can't merge as I don't have write access to the repo. Which raises the question should we be adding CODEOWNERS into this repo and broadening the maintainer list? @maoo / @DovOps

[maoo]

@DovOps @rocketstack-matt - could you please review this PR, so we can move forward with the merge?

Is the intent just to get the docs project in the build, as obviously the docs themselves are missing other than the front page? If so the setup looks fine to me, but I can't merge as I don't have write access to the repo. Which raises the question should we be adding CODEOWNERS into this repo and broadening the maintainer list? @maoo / @DovOps

Good points. Here's my proposal:

1. Make Matt a TraderX Maintainer (@DovOps - please lmk if you agree and I'll go ahead with permission changes)
2. Matt raises Pull Request around CODEOWNERS
3. Matt raises an issue to port documentation from github READMEs to Docusaurus (and update links into other collaterals); this issue could be a Good First Issue

Thoughts?

[DovOps]

@maoo I suggest we merge this - good with perm changes. And we can make additional changes once this is properly in the build