This directory contains the portions of the Terraform website that pertain to the Terraform CDK.
The files in this directory are intended to be used in conjunction with
the terraform-website
repository, which brings all of the
different documentation sources together and contains the scripts for testing and building the site as
a whole.
You must update the sidebar navigation for the CDKTF documentation any time that you add or delete a documentation page. The website builds the sidebar navigation menu from the nav-data JSON file. For more details about how to update this file, refer to https://github.com/hashicorp/terraform-website#editing-navigation-sidebars.
You must add a redirect when you move, rename, or delete documentation pages. Refer to https://github.com/hashicorp/terraform-website#redirects for details.
You should preview your changes locally to ensure that the content is rendering properly before you create a pull request. The build includes content from this repository and the terraform-website
repository, allowing you to preview the entire Terraform documentation site.
To preview your content, complete the following steps:
Set Up Local Environment
- Install Docker.
- Restart your terminal or command line session.
Launch Site Locally
- Navigate into your local
terraform-cdk
top-level directory and runmake website
. - Open
http://localhost:3000
in your web browser. While the preview is running, you can edit pages and Next.js will automatically rebuild them. - When you're done with the preview, press
ctrl-C
in your terminal to stop the server.
Content changes are automatically validated against a set of rules as part of the pull request process. If you want to run these checks locally to validate your content before committing your changes, you can run the following command:
npm run content-check
If the validation fails, actionable error messages will be displayed to help you address detected issues.
The website reads content from release tags to generate documentation for previous versions of CDK for Terraform. Changes merged into main
will be included in the documentation for the next product release.
The website reads the latest version of documentation from the stable-website
branch. To immediately update the latest version of the documentation, cherry-pick your changes to stable-website
. Changes pushed to stable-website
will be reflected on terraform.io within an hour.
You cannot edit documentation for past versions of CDK for Terraform. Documentation is an artifact of a product release. We push docs fixes forward for the next release, rather than retroactively fixing older versions.
When adding new configuration code samples, use CodeTabs
to provide them for all supported languages. If you don't intend to support more languages than Typescript you should use the typescript
tag, if you use it within a CodeTabs
component you should use ts
instead. This is a convention to help us separately find these cases in the search. To translate a code sample across all languages you can use the jsii-workbench as a helper.