* Restore the website workflow to the AWS getting-started guide
* Update code and output based on getting-started reop scripts
* Restore the actual website deployment
* Update themes/default/content/docs/get-started/aws/deploy-changes.md
Co-authored-by: Scott S. Lowe <slowe@pulumi.com>
* Update themes/default/content/docs/get-started/aws/destroy-stack.md
Co-authored-by: Scott S. Lowe <slowe@pulumi.com>
---------
Co-authored-by: Scott S. Lowe <slowe@pulumi.com>
Addressing two issues I discovered while going through the GCP Golang Get Started guide:
1. On the Modify Program step of the guide, `bucketEndpoint` is assigned but never used and therefore cannot compile. If a User wanted to run this program before proceeding to the Deploy Changes step, they would get an error like this: `./main.go:47:3: bucketEndpoint declared and not used`.
2. At the Deploy Changes step, `bucketEndpoint` is assigned before error handling for the previous call, which means it may proceed to attempt to access attributes from a `nil` value during interpolation when it should be providing the error from the `NewBucketObject` call.
Co-authored-by: Abhinav Gupta <abhinav@pulumi.com>
In the Get Started documentation,
when we tell users to Create a New Project with `pulumi new`,
we include a handful of short paragraphs next to each other
with instructions.
This is not very skimmable:
- keywords like project name/description/stack name
are hidden in the text
- the actual instruction of what to do is also just hidden
in the text
For someone following along, it's better to have keywords
related to prompts they're seeing highlighted,
and to include a sample output they can follow along to.
This changes the create-project sections
of all four Get Started with Pulumi pages
in the following way:
- project name and project description are bold
- change "name of a stack" to "a stack name", and bold "stack name"
- add the output of `pulumi new` after each step;
I've altered the output slightly to not be language-specific
Before this change, only the k8s tutorial included a sample prompt,
but that was at the top of the text rather than interspersed with it.
* Improve download discoverability
We know users have trouble simply downloading Pulumi. This used to be
very easy, but over time, as we optimized the Getting Started flows, it
got pushed further and further away from the core user experience.
I don't know about you, but the first thing I care about when I'm
trying out a new open source tool is downloading it!
This change aims to do two things:
1. Make downloading a more prominent CTA.
2. Improve the download page so it's less noisy and more focused.
This entails:
* Adding a DOWNLOAD secondary CTA on the homepage.
* Summarizing the recommended download options at the top of the
download page, very clearly, and without any preamble. This
hopefully tells you instantly what you wanted for the 80% case.
* I exerted some artistic freedom which I'd love feedback on. The
recommended options were our Official Brew Tap for macOS, curl
command for Linux, and MSI Installer for Windows. Peers to those
are simple download links for the binaries, as that's the simplest
possible thing, which today is actually the hardest thing to find.
Notably for Windows, I thought of using Chocolatey or Winget, but
I don't perceive that either is "the default" for Windows users.
Winget is the future but it isn't supported pre-Win11, which I have
to assume most users aren't on yet. MSI has been around since the
dinosaurs, so it seems like the safest choice to promote.
* Moving the list of download options for each operating system
underneath a collapsable accordion list, which is collapsed by
default, and clearly labeling it as "Other"; as in, if the heading
didn't work for you, here are some other options.
* A few other wordsmithing tweaks to make the page a little more
streamlined and to flow better.
This is absolutely NOT the final destination for any of this,
however, I am hopeful it will be a simple incremental improvement
that moves the needle on key metrics. We'll watch it in the weeks
to come and course correct as needed -- as well as continuing to
think about ways we can improve all of this overall!
One note: This depends on a new secondary hero button style that
isn't yet merged in the upstream Hugo component library. Assuming
I did that correctly (a big if!) I'll need to rev the go.mod file
after it merges. See: https://github.com/pulumi/theme/pull/159.
* Apply suggestions from code review
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
* Fix up some styling
* Update themes/default/layouts/index.html
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
* Use new theme/style
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
Co-authored-by: zchase <zachary@pulumi.com>
* A handful of updates
Here are some updates based on recent conversations and feedback:
* Update the homepage subheading to be a bit clearer about what
Pulumi is and what it does.
* Change the Cloud Engineering menu item to Why Pulumi, and sort
it to the right of Product. This more clearly speaks to what
this navigation item represents as well as its importance
relative to learning about Pulumi's Product offerings.
* Change the Pulumi Product landing page to say Pulumi Overview,
not Cloud Engineering Platform, since that's what you click to
get there and it currently feels very disconnected from all of
the surrounding marketing which speaks in terms of IaC.
* Add a paragraph to that overview page speaking simply to what
Pulumi is, and making sure to mention open source.
* Add a sentence to the Get Started page about open source.
* Add more customer logos -- we should be updating this much more
often!! Also change the logos to scroll horizontally so that
we aren't afraid to continue adding new ones from time to time.
* Add recent news stories -- we should be updating this much
more often too!! Apparently it's been over a year, despite having
tons of news coverage to share.
* Run prettier to format things
* Sort the case studies
* crop tfir logo
Signed-off-by: susanev <susan.ra.evans@gmail.com>
Co-authored-by: susanev <susan.ra.evans@gmail.com>
* Update getting started guides for dotnet 6 using newer templates
* lint
* update ec2-webserver how-to guide for csharp
* Fix inconsistencies found by Mikhail 🙏
* Add installation sections on Windows for winget and standalone
* make linter happy
* use an article when addressing winget-cli
Co-authored-by: Christian Nunciato <c@nunciato.org>
Co-authored-by: Christian Nunciato <c@nunciato.org>