Re-run mktutorial.sh to regenerate tutorial content from the Examples repo.
It's not immediately clear to me we *want* to keep all the newly added tutorials here, as the examples are of a varying level of quality/completeness. We could alternatively only accept the "modifications" here and leave out the new tutorials for now. But broadly speaking the additions help flesh out multi-language coverage for a number of areas. I'm inclined to just keep everything here for now, until we decide on a different strategy for tutorials overall.
* Clean up EC2 webserver tutorial
Add shortcode for multi-language prerequisites
Add shortcode for GitHub buttons for multi-language examples
Signed-off-by: bermudezmt <bermudez.mt@gmail.com>
* Pull in tutorial title updates
Signed-off-by: bermudezmt <bermudez.mt@gmail.com>
* Clean up EC2 webserver tutorial
Signed-off-by: bermudezmt <bermudez.mt@gmail.com>
* Fix broken link
- Use ungreedy matches for links.
- Don't attempt to fix-up links that start with "../"
- Fix left alignment of "Edit on this Page" and "Request a Change"
- Remove "Edit on this Page" for generated pages
- Add "WARNING: this was generated by a tool" comment to generated pages
- Use Tailwind for styles
* Add a new property in the tutorial template to set the correct URL for the Deploy With Pulumi button.
* Regenerate tutorials.
* Detect Deploy With Pulumi button links and use its destination as the PulumiTemplateURL.
This change adds auto-generated tutorials, using our [examples repo](https://github.com/pulumi/examples) as its source. Namely, we scrape the README.mds. We do some on-the-fly rewriting of certain content to make it work on the docs website -- including adding appropriate links back to the GitHub source code -- however, for the most part, the content is taken as-is. There are plenty of examples that need to be tidied up for consistency, to make the titles better, and so on, but this seems like a significant overall improvement so we plan to land roughly as-is.
* Add auto-generated tutorials and indexes
* Update URLs to use new post-ToC update structure
* Add a Featured Tutorials section to AWS
* Add curated "Featured Tutorials" sections
* Remove numbers from tutorial titles
* Add links to the tutorials source code
* Remove "all tutorials" index
* Don't link to AKS from GCP tutorials page
* Add a VIEW CODE button
And also wordsmith some of the "get source code first" note.
* Use linktitle for shorter titles
This ensures that the navigation name and the breadcrumb match.
* Update text for requesting a new tutorial
* Add mktutorial to `make gen`
* Add a nicer tutorials landing page
* Simplify the VIEW CODE button
* Rewrite relative Markdown links
This change automatically rewrites Markdown links that are
relative to our GitHub repo, so that we don't end up with broken
links in the resulting documentation website.
* Fix some broken links
* Ignore some example links
Our examples contain a lot of illustrative links that are either
synthetic or not meant to be publicly accessed. Ignore them during
broken link checking.
