* 2.0 migration doc
* Fix tab
* Unparameterize the NodeJS text since the chooser lets us have both JS and TS
* Update content/docs/get-started/install/migrating-2.0.md
Co-Authored-By: Luke Hoban <luke@pulumi.com>
* PR feedback
* include beta.1 in the versions
* Update pulumi version on versions page
* Update to beta.2 for pulumi SDK
Co-authored-by: Lee-Ming Zen <lee@pulumi.com>
Co-authored-by: Luke Hoban <luke@pulumi.com>
The "Terraform Pulumi bridge" link references to the wrong repo (https://github.com/pulumi/pulumi-terraform). It now points to the right repo to reduce confusion on how to make pulumi work from current Terraform users.
* Rearrange existing User Guide ToC
* Rename "Tutorials and Guides" to "User Guides."
* Rename "Cloud Programming Tutorials" just to "Tutorials."
* Sort "Tutorials" at the top of this list.
* Make room for the new "Adopting Pulumi" user guide.
* Add the Adopting Pulumi index page
* Add an import guide
This is largely based on the existing import blog post.
* Add an initial, half completed, Terraform guide
* Add the empty AWS, Azure, and Kubernetes pages
* Fix a few broken links
* Add coverage of tf2pulumi in the adoption guide
* Use shorter titles
I had wanted to use the longer titles because they look better in
SEO. However, unfortunately the breadcrumbs use the title it seems,
and not the display H1 or menu name, which means the breadcrumbs
ended up looking ridiculously long and redundant.
* Add an AWS CloudFormation migration guide
* Add a guide for moving to Pulumi from ARM
* Add some logos to spruce things up
* Add a page for Kubernetes adoption
* Fix a typo in the copy button code
* Apply @lukehoban suggestions from code review
Co-Authored-By: Luke Hoban <luke@pulumi.com>
* Incorporate more code review feedback
Co-authored-by: Luke Hoban <luke@pulumi.com>
I noticed that the ordering on the left-hand navigation for the
cloud providers section got scrambled at some point. I suspect we
just weren't watching the "weight" specifiers closely as we added
some of them (if it is intentional, it wasn't apparent to me).
I've changed this to have two clumps of cloud providers:
* First, the "primary four" -- AWS, Azure, GCP, and Kubernetes --
that sorts at the very top (in alphabetical order).
* Second, the rest.
I gave them the same weights and let the ToC rendering logic
alphabetize rather than needing to maintain them by hand, which
would get quite tedious.
