tree 44b7b44aef4878631abf71693b15d2344c933551
parent 11c073319878e14c2d8a985cd00eaca3de8e2b0d
parent 2bccccfb2a17e2e1b03dd28b5ba6cdf59497cab6
author Scott Todd <scotttodd@google.com> 1620233907 -0700
committer GitHub <noreply@github.com> 1620233907 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgks6zCRBK7hj4Ov3rIwAAYf0IAKwNZTaGmIa+WoCHRCV9d+Sv
 MxZ8xT7jl4muFN1CIfWkZmEfZOkkh9Wao6+zKZQ4k2yrg53CJmRpGH5L4GuIe1C7
 /vPEE7A4hzQVULTmL9e+QLj1nCJn6ontlSES0mteev8j35XudaFn+1Mqclq/7brB
 vPg9lVYfpWqJumgbH2rnZ/cOdf5YJaWZkmpsKRQQ7XN/nV1QLSmZz+9gggRV5chH
 Lm0MTFToswiOteb8n1Hzu6+CDvr6Yvy52hyypYz4VNVnyLyq1IhkP88MrdZBOfs4
 Z8od3KuZ0Wdi7XfzuLal6gNqbgJKnPo9RM0lNbzTxGus9LokabIzqFt4Th8cycE=
 =idP2
 -----END PGP SIGNATURE-----
 

Prep for new website: move existing docs and disable current publication. (#5733)

Progress on https://github.com/google/iree/issues/5460

* Move the existing `docs/` folder to `docs/developers/`. The new website will go next to that at `docs/website/`.
* Remove old doc generation and publication scripts.
  * Doc publication has been [failing for two weeks](https://github.com/google/iree/actions/workflows/publish_docs.yml) anyways, not worth fixing.
  * New generation/publication will use different scripts/commands. I have that working on my [`mkdocs-publish`](https://github.com/ScottTodd/iree/tree/mkdocs-publish) branch now. Landing this on `main` first will make the rollout easier.

The existing GitHub Pages website will stay up until we push changes to the [`gh-pages`](https://github.com/google/iree/tree/gh-pages) branch. I'm planning on first merging the [`staging-docs-rework`](https://github.com/google/iree/tree/staging-docs-rework) branch _then_ turning on new publishing automation that will push there.

The rollback plan (hopefully not needed) is to

1. Disable any newly enabled publishing automation
2. Restore the `gh-pages` branch manually
3. Revert this PR / restore old publishing scripts/workflows