This uses eleventy, a simple static site generator to build the LiveCodeLab site and output it to the dist folder.
The development process for the project is exactly the same. Running npm run start will still bring up live code lab on port 8080 with hot reloading.
The main differences are that npm run build will build the site into the dist folder and then build LCL into the dist/play folder, which is where it needs to be to be linked from on the site.
There are now npm run build:site and npm run start:site commands as well that allow building and development of the site separate from lcl.
There are a few benefits with this approach.
The reference docs and wiki are currently built from the LCL repo and it would be good to have them hosted on the site.
github actions or switching to netlify would allow auto building and updating the site from tagged releases.
The site is simple enough that it doesn't really need to be a fully separate repo.
This uses eleventy, a simple static site generator to build the LiveCodeLab site and output it to the dist folder.
The development process for the project is exactly the same. Running
npm run startwill still bring up live code lab on port 8080 with hot reloading.The main differences are that
npm run buildwill build the site into the dist folder and then build LCL into the dist/play folder, which is where it needs to be to be linked from on the site. There are nownpm run build:siteandnpm run start:sitecommands as well that allow building and development of the site separate from lcl.There are a few benefits with this approach.
have a look and let me know what you think.