* Add some initial structure for what is pages
* Add some dots
* Refinements to what is pages
* Make the linter happy
* Add why is python so popular topic page
* Add infrastrucutre as code internal links
* Add infrastructure as software internal links
* Fix link formatting
* Only show the top 40 blog tags
In https://github.com/pulumi/pulumi-hugo/pull/215, I had suggested
that instead of physically deleting tags we didn't want to show, we
compute it algorithmically, by only showing the "Top N" tags. This
commit introduces said functionality.
This has a few advantages:
* Preserves old metadata (the authors added the tags because they
felt they were meaningful and captured information about the posts).
* Enables us to surface those tags differently in the future (who
knows, maybe someday we'll want to run a "spinnaker" campaign).
* Notably, also keeps the tag index pages, which Google has indexed.
* Enables us to add a "View More ..." link at the bottom of the
page if folks want to see the entire list.
* Perhaps most importantly, protects against future bloat. For
example, since this tag cleanup happened, we have added top-level
tags for "aliases", "app-runner", "iam", "open-source", and
"refactoring", each of which has only a single post.
I chose 40 as the N in Top N, because that's how many we show today.
I could see an argument for filtering this based on post count
instead (e.g., only those with >3 posts).
* Add back some tags
Now that we filter out unpopular tags, we can add back some of the
ones previously removed.
This way, we'll get build-time errors if we've moved a page around and haven't fixed the link, and it ensures a trailing `/` is present in the generated URL, which avoids unnecessary redirect S3 redirect hops.
Instead, use `relref` links. That way, we can catch any issues if we
move a page to a different URL. Also, prefer `https` rather than `http`
for links to other Pulumi sites.
Note: This does not change any links to www.pulumi.com in autogenerated
content (such as API docs and tutorials).
* Add markdown linting script; fix markdown lint errors
* Add support for meta description and page title validation
* Add comments
* Fix lint errors; exclude autogenerated tutorials
* Address feedback; add more comments
* Add more checks for redirect pages; no index; and auto generated content
* More fixes for lint errors
* Allow duplicate headings in a page
* More lint error fixes
* Even more lint error fixes
* Getting started guide lint fixes
* Add custom h1 support to docs single pages
* Use custom h1 tags on cloud getting started guides
* Add custom h1 support to docs
* Add custom h1 support to docs lists.html
* Final round of intial lint fixes
* Add markdown linting to build script
* Update README
* Test build failure due to lint error
* Fix lint error so build will pass
* Readability fixes for lint script
* Add a blog post about EKS cluster features
* Add an image; react to CR feedback
* Make the flow a bit nicer
* Simplify some wording
* More wordsmithing
* Add a shoutout to Clare's keynote talk
* Change publication date on post to today
* Make one final pass over the post
* Fix the preview and a few typos
