* break up large H3 in concepts/state docs
* move service architecture under backend heading
* reduce heading depth to place more items on sidebar nav
* Apply suggestions from code review
* merge logout with login, self-hosted service with service backend
* update links to state
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
* Add org tokens page
* Link to REST docs
* Add delete token img
* Lint
* Rm duplicated API endpoint in Service REST API docs
* Update _index.md
* Cropped photo
* Moved Access Tokens content to new page
* Moved org tokens stuff into one access tokens page
* Add access tokens to menu
* Streamlining content
* lint
* Add access tokens link to list
* Add links to access token page where appropriate
* PR: reworded org tokens section
* PR: Docs update to express that we support deleting stacks/teams
* Restored accounts page
* Moved Org tokens content back to owne page
* rm unused img
* Updated link ref to access tokens
* Add link to org tokens from standard access tokens links
* ref instead of relref
* Update themes/default/content/docs/intro/pulumi-service/organization-access-tokens.md
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
* replaced broken refs
Co-authored-by: susan evans <susan.ra.evans@gmail.com>
* 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"
* Move filter and CTA to right side of event listing page
* Add heading to event list showing number of events available when filtering
* Remove calendar embed and use button to bring up calendar modal
* Slightly prettify the event-listings page
* Slightly prettify the event-detail page
* Make the registration button orange
* Add ability to use filter query param to pre filter events
* Address feedback
* Remove excess console.log
* Update assets/js/event-filtering.js
Co-Authored-By: Justin Van Patten <jvp@justinvp.com>
Co-authored-by: Christian Nunciato <christian@pulumi.com>
Co-authored-by: Justin Van Patten <jvp@justinvp.com>
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 a 2019 year in review blog post
* Add a bullet on community in 2019
* Fix typos and lengthy meta description
* Incorporate PR feedback
* Add a new year photo
