fix: Allow Docusaurus and IDE co-existence

[cmumatt]

Description

This PR allows Docusaurus and IDE co-existence at CloudFlare by injecting the IDE build output into the Docusaurus build, which eliminates the need for two deployments and two URLs.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new ESLint warnings
• I have reviewed any generated changes to the diagrams/ folder

Open questions

Questions that require more discussion or to be addressed in future development:

• I temporarily commented out the live demo since it is just showing a circle; I figured that's still a work in progress.

[codecov]

Codecov Report

Merging #916 (2f6ee06) into main (36c0867) will not change coverage.
The diff coverage is n/a.

❗ Current head 2f6ee06 differs from pull request most recent head 3777fad. Consider uploading reports for the commit 3777fad to get more accurate results

@@           Coverage Diff           @@
##             main     #916   +/-   ##
=======================================
  Coverage   68.17%   68.17%           
=======================================
  Files          62       62           
  Lines        8117     8117           
  Branches     1768     1768           
=======================================
  Hits         5534     5534           
  Misses       2576     2576           
  Partials        7        7           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 36c0867...3777fad. Read the comment docs.

[cloudflare-pages]

Deploying with    Cloudflare Pages

Latest commit:	3777fad
Status:	✅  Deploy successful!
Preview URL:	https://10528a16.penrose-panes.pages.dev

View logs

[wodeni]

Thanks for doing this one! Still a little unclear to me how the deployment process look like. Are we using Cloudflare now? Looking at it now, it's still deploying panels. In my head I was thinking we were going to:

• Add a top-level script in package.json: yarn build:sites builds everything, right now just panels and docs-site
• This script should build @penrose/docs-site and @penrose/panels, and then collect build artifacts into a singular folder for deployment.

Lmk if I was just thinking about the wrong thing, and how deployment is done at the moment.

[wodeni]

Would be better to have a separate script for this. You could use a pre-hook (prebuild) for this purpose: https://docs.npmjs.com/cli/v8/using-npm/scripts#pre--post-scripts

[wodeni]

Also, rimraf is supposedly faster and platform independent for rm -rf

[cmumatt]

Awesome! Thanks for reviewing and for that suggestion; I also like the idea of a pre-hook better and created issue #917 to implement that. At the same time, I will check if there is a similar analog for cp if we aren't assuming a *ix-like script environment.

Cloudflare is temporarily still deploying penrose/main to the old penrose-panels project -- but all traffic to that project is redirected to the penrose-site project (penrose.cs.cmu.edu), which currently hosts this PR's build output. So, CD is currently broken on purpose. Once this PR is merged, I plan to re-point penrose/main's CD to penrose-site, which involves re-creating both projects due to repo associations being 1:1 and immutable at CF, as you pointed out previously, which is kind of a bummer -- but our current reality.