* Merging existing content with rproposed rewrites in this PR, fixed broken links, etc.
* Add redirect to concepts overview page as stop-gap to handle auto-gened ref content links
* Apply suggestions from code review
Co-authored-by: Luke Hoban <luke@pulumi.com>
* Fix broken links
* Incorporating TR feedback
* Fixed broken links
* Incorporating remaining feedback, renamed and refactored content, updated links
* Add client-side redirect logic to map old anchors to new
* Incorporated more feedback, refactored runtime function content, fixed broken links
* Minor typo fix
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Copy edit
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Update content/docs/intro/concepts/project.md
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Incorporated TR feedback
* Trimmed left nav link title
Co-authored-by: David Wrede <dave@pulumi.com>
Co-authored-by: David Wrede <d_wrede@yahoo.com>
Co-authored-by: Luke Hoban <luke@pulumi.com>
Co-authored-by: Christian Nunciato <c@nunciato.org>
* Eliminate "real languages" from our website
We know that this terminology is unfriendly and can be seen as
gatekeeping. We've moved away from it over time, but there are many
traces of it in our documentation -- most notably, even on our
homepage. Instead of "real languages", let's use "familiar languages",
and in places where deeper explanation makes sense in context, we
can say "familiar, general-purpose languages."
The current 2nd-level blurb on the homepage isn't very good right now
anyhow, so this is a convenient change. As we make progress on various
marketing efforts, we will likely make more extensive changes, but
for now this at least fixes this problem. We recently A/B tested
updates without much of an impact, so let's move ahead with this change
and then if we want to test alternatives to "familiar", we can do that.
For instance, we considered "popular", etc.
* Also eliminate "real code"
