Deno: //website is dead code

[ry]

Since https://github.com/denoland/deno_website2 the code in //website is dead. We need to figure out what to do with it.

Should website2 be merged into the main repo? Having netlify CI run for unrelated changes seems undesirable.

Maybe denoland/deno should be a submodule of website? Then we can maintain manual.md and style_guide.md in the main repo...

[nayeemrmn]

+1 for the second option.

[lucacasonato]

+1 for the second option.

I like this approach but afaik Netlify wont trigger on updates to the submodule. We would still have to manually update the submodule version in the website repo.

[chrmoritz]

Also the benchmark results are currently still published from within this repo. This could possibly be moved to be published to the new deno_website2 repo via Netlify too.

[Janpot]

If I understand correctly you can run github actions only when certain paths have changed. Maybe that could solve your problem of CI?

[ry]

We've decided to keep deno_website2 as a separate repository. And rather than having deno be a submodule of website2, I'm going to simply move the manual.md and style_guide.md into //std so they can be accessed like other markdown files. Then there is no need for special handling of them.

@Janpot that's good to know - but we also have Netlify and Cloudflare workers involved. It seems it will be easier to just keep the website separate.