chore(docs): remove documentation that has been moved to hashicorp/web-unified-docs

Back in May, all the contents of the website/ directory which powers our documentation on developer.hashicorp.com were migrated to the centralized hashicorp/web-unified-docs repository. At the time, we left the docs here just in case something happened and we needed to revert the migration.

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.

Author: xiehan

.github/CODEOWNERS

@@ -1,33 +1,5 @@
-# We use this for automatic PR review assignment within Github.
-# If individual users are specified in this file, this is mainly to
-# inform them of certain PRs and we don't require a review from them
-# to be able to merge PRs.
-
 # These owners will be the default owners for everything in
 # the repo. Unless a later match takes precedence, 
 # they will be requested for review when someone opens a 
 # pull request.
 *       @hashicorp/cdktf
-
-# Engineering and web presence get notified of, and can approve changes to web tooling, but not content.
-
-/website/           @hashicorp/web-presence @hashicorp/cdktf
-/website/data/
-/website/public/
-/website/content/
-
-# Education and engineering get notified of, and can approve changes to web content.
-
-/website/data/      @hashicorp/team-docs-packer-and-terraform @hashicorp/cdktf
-/website/public/    @hashicorp/team-docs-packer-and-terraform @hashicorp/cdktf
-/website/content/   @hashicorp/team-docs-packer-and-terraform @hashicorp/cdktf
-/website/docs/      @hashicorp/team-docs-packer-and-terraform @hashicorp/cdktf
-/website/README.md  @hashicorp/team-docs-packer-and-terraform @hashicorp/cdktf
-
-# No codeowners for these files, as they are generated.
-# This way, Education does not get notified if only these files changed.
-website/docs/cdktf/api-reference/typescript.mdx
-website/docs/cdktf/api-reference/python.mdx
-website/docs/cdktf/api-reference/java.mdx
-website/docs/cdktf/api-reference/csharp.mdx
-website/docs/cdktf/api-reference/go.mdx

.github/ISSUE_TEMPLATE/config.yml

@@ -3,6 +3,9 @@
 
 blank_issues_enabled: false
 contact_links:
+  - name: 📕 Documentation Issue
+    url: https://github.com/hashicorp/web-unified-docs
+    about: Documentation has its own repository for all HashiCorp products and related issues or questions should be directed there
   - name: ❓ Question
     url: https://discuss.hashicorp.com/c/terraform-core/cdk-for-terraform/47
     about: 🙋 For usage questions that may not require a core maintainer to answer, post in our community forum

.github/ISSUE_TEMPLATE/documentation.yml

@@ -20,7 +20,7 @@ In plain English, describe your approach to addressing the issue linked above. F
 - [ ] I have run the linter on my code locally
 - [ ] I have performed a self-review of my code
 - [ ] I have commented my code, particularly in hard-to-understand areas
-- [ ] I have made corresponding changes to the documentation if applicable
+- [ ] I have made corresponding changes to the [documentation](https://github.com/hashicorp/web-unified-docs/tree/main/content/terraform-cdk) if applicable
 - [ ] My changes generate no new warnings
 - [ ] I have added tests that prove my fix is effective or that my feature works if applicable
 - [ ] New and existing unit tests pass locally with my changes

.github/pull_request_template.md

@@ -13,7 +13,6 @@ node_modules
 .cdk.staging
 cdktf.out
 
-
 **/.DS_Store
 **/.gen
 **/*.log
@@ -41,3 +40,6 @@ examples/java/gradle-shared-module/.gradle/
 .nx/
 .yarn
 test/.yarn
+
+website/*
+!website/README.md

.github/workflows/check-legacy-links-format.yml

@@ -17,11 +17,9 @@ test/edge-provider-bindings
 !tools/update-github-project-board/index.ts
 **/go.mod
 **/go.sum
-website/website-preview
 *.py
 *.java
 *.go
 *.cs
 packages/cdktf-cli/src/lib/ambient.d.ts
 packages/cdktf-cli/ambient.d.ts
-

.github/workflows/website-release.yml

@@ -89,7 +89,7 @@ Ensuring your PR titles follow this format helps us quickly identify the purpose
 
 To build and install `terraform-cdk` locally you need to install:
 
-- Node version 14.0+
+- Node version 20.0+
 - Go 1.18
 - dotnet (v6.0)
 - mvn
@@ -365,14 +365,17 @@ Most of our tests are automated but there are some workflows we need to manually
 1. Create a new branch (e.g. `prepare-release-0.9.0`)
 2. Update the [CHANGELOG](./CHANGELOG.md): `./tools/create-changelog.sh` should get you a good start
 3. Update the version in the root `package.json`
-4. Write an [upgrade guide](website/docs/cdktf/release/) (for major releases)
-5. Run `yarn generate-docs` to bring our api documentation up to date
-6. Create a PR to merge the new branch into `main`
-7. Merge the PR, a new release will be build and published because the version changed
+4. Create a PR to merge the new branch into `main`
+5. Merge the PR, a new release will be build and published because the version changed
+6. For major releases:
+
+- Write an [upgrade guide](https://github.com/hashicorp/web-unified-docs/tree/main/content/terraform-cdk/v0.21.x/docs/cdktf/release)
+- Run `yarn generate-docs` to bring our api documentation up to date
+- Make a PR with the changes over in the [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs) repository
 
 #### After the release
 
-- Update the prebuilt provider repository [like this](https://github.com/hashicorp/cdktf-repository-manager/pull/48) (If the release contains breaking changes the commit message needs to have a `!` after the scope so that the minor version is bumped. Example: `chore!: update cdktf version`) and run the [prebuilt provider upgrade workflow](https://github.com/hashicorp/cdktf-repository-manager/actions/workflows/upgrade-repositories.yml)
+- Updates in our other repos should largely be automated, but some of the updates require manual approval before they'll be auto-merged
 - Update the learn examples and the end to end examples
 - Check if there are PRs left behind on our [triage board](https://github.com/orgs/hashicorp/projects/125/views/4)
 
@@ -473,4 +476,4 @@ A good way to tackle windows related things is to use an AWS EC2 instance runnin
 
 ## Documentation
 
-The markdown files containing the documentation for CDK for Terraform are in the [`/website`](./website) directory. Refer to the [website README](./website/README.md) for more information.
+Product documentation previously located in `/website` has moved to the [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs) repository, where all product documentation is now centralized. Please make contributions directly to the [`terraform-cdk`](https://github.com/hashicorp/web-unified-docs/tree/main/content/terraform-cdk) directory under `web-unified-docs`, since changes to `/website` in this repository will not appear on [developer.hashicorp.com](https://developer.hashicorp.com).