Because our language chooser doesn't show/hide language
elements for pages without tabs, some Go steps are hidden.
We tried to make that logic apply even when tabs aren't present,
but that had unintented consequences for regular content like
blogs. So, just move those steps to pages with tabs on them.
* Do an editorial pass over programming model docs
This is an editorial pass over the programming model docs, as part
of #1618. This includes rearranging ordering to minimize forward
references, getting rid of anything that smells "TypeScript-only",
restructuring headers so the ToC is a bit more structured,
wordsmithing, fleshing out examples, and trying to simplify the
presentation of content -- while also embellishing where it helps.
This is not done. The Go and TypeScript pages are empty. There is
still quite a number of TypeScript-only hyperlinks and terminology.
* Add Vim swp files to gitignore
* Use shortcodes to cut down on language-specific text/links
This change adds some shortcodes for common language-specific
text and associated links.
For instance, outputs are Output in JS, Output<T> in TS,
Output[T] in Python, Output in Go, and Output<T> in C#, and go
to very different places hyperlink-wise.
Because of the way our language switcher JavaScript works, we
display the JS version by default until it kicks in and picks
up the user's choice. This avoids awkward flashes in which all
or none of the options are available or missing.
I'm not done applying this to all possible codes, but at least
it lays the foundation to start paying down this debt.
* Fix a couple hygiene issues
* Clarify conditional execution of apply
* Fix input shortcode
* Add shortcodes for most language-specific things
This eliminates most (all?) of the language-specific texts and
links in the programming model document, replaced with shortcodes.
* Fix up some loose ends
* Add Go language page and Get Started guides
* Fix linter errors
* Apply suggestions from code review
Co-Authored-By: Christian Nunciato <c@nunciato.org>
* Apply additional code review feedback
* Use spaces, not tabs.
* Use tailwind styles, not inline CSS.
Co-authored-by: Christian Nunciato <christian@pulumi.com>
* Makes SEO changes reccomended by 97th floor
* Fix extra space
Co-Authored-By: Eric Rudder <ericrudder@users.noreply.github.com>
* Fix capitalization
Co-Authored-By: Justin Van Patten <jvp@justinvp.com>
Co-authored-by: Eric Rudder <ericrudder@users.noreply.github.com>
Co-authored-by: Justin Van Patten <jvp@justinvp.com>
* Add initial framework for event landing page
* Clean up event one pager and add new CTA
* Replace image with code block; update cta copy
* Update desktop cta and deploy block copy
* Update address to have google maps link
* Remove unused block and content
* Update naming convention for blocking crawlers from indexing a page
* Rename variable for excluding page from internal search
* Do not add pages blocked from external search to the site map
* Add follow to robots meta tag
* Update contributing doc with new front matter variable
* Remove external search blocking from docs index
* Rename event to show
* Move meta desc so pulumify can rebuild the preview
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).
This changes the structure of the nav slightly: instead of showing
"Overview" pages for each sub-section as an independent entry, which
consumes vertical space, hyperlink the section header itself. This
feels more intuitive to me, matches the way the breadcrumbs work,
and saves us on a bit of vertical real estate (which is getting fairly
scarce on our site now-a-days, as we continue to add more sections).
Changes usage of `ref` (fully qualified URL) to `relref` (relative URL), as there's no need for these to be fully qualified and we generally use `relref` throughout.
* 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
