Make it clearer throughout our docs and websites that we support AWS CDK in addition to Terraform

Feature Spec

Anyone who skims through our docs doesn't get the impression that we are a Terraform shop only, especially when reading the getting started guild - https://www.winglang.io/docs/start-here/aws

Use Cases

We are losing potential users coming from the CDK that don't see we compile to the CDK.
It also creates concern that we have a risk related to the new TF licensing

Implementation Notes

We only give Terraform (or TF) as the compilation artifact throughout our docs. We should change this. Easiest thing would probably be to start by searching "Terraform" and "TF".
In the getting started guide, in the "Deploy to AWS" section, it also only shows how to deploy with TF (https://www.winglang.io/docs/start-here/aws).

We also give this impression on our websites.

Component

Documentation

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.

Start by searching for “Terraform” and “TF” across the documentation and websites, then inspect the getting started guide at /docs/start-here/aws, especially the “Deploy to AWS” section. Done means the docs and website clearly communicate AWS CDK support alongside Terraform and explain the available deployment paths.