* Add TypeScript to the Pulumi Fundamentals pathway
* Address feedback
* Fix langfile references
* Address feedback
* Don't do that
* Add TypeScript output as well
* Little fixes
* Add update plans blog draft
* Add asciicasts of update plans
* Update date
* Update themes/default/content/blog/announcing-public-preview-update-plans/index.md
Co-authored-by: meagancojocar <50200557+meagancojocar@users.noreply.github.com>
* New meta image
* markup
* lint
* Update version
* Drop header
* Apply suggestions from code review
Co-authored-by: George Huang <george@pulumi.com>
* Rephrase example description a bit
* Update date for Wednesday publish
* Apply suggestions from code review
Co-authored-by: George Huang <george@pulumi.com>
Co-authored-by: Fraser Waters <fraser@pulumi.com>
Co-authored-by: meagancojocar <50200557+meagancojocar@users.noreply.github.com>
Co-authored-by: George Huang <george@pulumi.com>
We don't currently have any content on this page, and it's indexed, so we should probably send those who find it to our current Crosswalk for AWS docs.
* feat(pathway): add initial scaffolding for new pathway
* feat(intro): adding in the draft intro for the pathway
* feat(scaffold): add scaffolding of pathway
* feat(content): add more content
* feat(content): add more content to the pathway
* feat(components): adjust to work with component resources
* feat(abstraction): add diagram
* revert(accident): revert accidental commit
* fix(lint): patch trailing spaces
* fix(lint): another one
* fix(code): stop coding half-asleep on flights; fixing error
* fix(derp): remove leftover text
* feat(meta): add forgotten meta image
* Apply suggestions from code review
Accepting first round.
Co-authored-by: Josh Kodroff <jkodroff@users.noreply.github.com>
Co-authored-by: Christian Nunciato <c@nunciato.org>
* fix(review): update from review
* fix(review): update to match review
* fix(review): add more review responses
* fix(review): add more updates based on review; move around the components
* fix(review): add a bit more from review
* fix(lint): fix whitespace and missing transition line
* fix(handling): forgot to update error handling; fixing based on review
* fix(wording): patch from review
* fix(review): add the last of the review stuff
* fix(review): add final fixes from review
* Update themes/default/content/learn/abstraction-encapsulation/_index.md
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Apply suggestions from code review
Co-authored-by: Christian Nunciato <c@nunciato.org>
* fix(meta): update meta images
* fix(line): add empty line to make markdown happy
* fix(review): wording patch
* fix(review): add comments to code for better readability
* fix(review): add links and examples
Co-authored-by: Josh Kodroff <jkodroff@users.noreply.github.com>
Co-authored-by: Christian Nunciato <c@nunciato.org>
Per: https://www.pulumi.com/docs/intro/languages/go/
> Pulumi supports writing your infrastructure as code using the Go language. Go 1.16 or later is required.
The basic `pulumi new go` setup fails to preview when using Go < 1.16.x in the provided GitHub Actions templates.
* Update SSO configuration instructions for Okta
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
Co-authored-by: Christian Nunciato <christian@pulumi.com>
Even after breaking the Programming Model content down, this Resources page still contained a *lot* of core content. This made a lot of important features feel very "hidden", like resource options, components, dynamic providers, and more.
It also led to suboptimal search results, both in Google and in our own internal site search, because searches for specific concepts (like "pulumi aliases") would return the "Resources" page, which didn't even rank particularly well as it doesn't "feel" like definitive content for this specific topic.
This change breaks this page into 18 separate pages. It keeps the "Custom Resource" content in the main Resources page (since that content is nearly entirely actually not specific to Custom Resources anyway), pulls the Custom Resource, Resource Providers and Dynamic Providers content into separate top level items, and pulls the Resource Options content into it's own index with a separate page per resource option.
Some of the resulting pages are fairly light in content, but this actually offers room to flesh these out more fully now that they have room to breathe.
Reading through this content as part of the refactor, there is quite a bit of cleanup we could still do here. I took a few liberties to clean up some things as part of this, but mostly focused on the refactor instead of changes to prose.
This also introduces a set of client-side redirects to the resources page, so that each of the previous anchors which now lives elsewhere will get redirected in the client, following the same strategy used in the Programming Model page refactor.