chore(docs): remove documentation that has been moved to hashicorp/web-unified-docs #3921
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Back in May, all the contents of the
website/
directory which powers our documentation on developer.hashicorp.com were migrated to the centralizedhashicorp/web-unified-docs
repository. At the time, we left the docs here just in case something happened and we needed to revert the migration, but we added a comment to every single docs page redirecting users to the new location in #3863.Now that a couple of months have passed, we can confirm the migration was completed successfully and there's no reason to revert it, so it's time to completely delete all the contents of the old
website/
directory, which can be a potential source of confusion for users.Kudos to Radek for allowing me to copy your homework in hashicorp/terraform#37417.
Open questions/concerns
vercel.json
file refers to the dev docs and the one in thecdk.tf/
directory powers the redirects, but if anyone thinks the top-level file isn't safe to delete, let me know.generate-docs:api
script working; it'll still generate the docs in an ignored folder, and then you'll have to manually copy-paste the contents in a PR on theweb-unified-docs
repo. I don't think it's possible to do a similar "minimum viable implementation" of thegenerate-docs:translations
script, as that one relies on the old docs being present in the repo. While we might be able to do something with git submodules or symlinks, I don't have the bandwidth to figure that out, so I think it makes the most sense to just delete this tooling; anyone opposed to doing that?