-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS] Update the title & description for SEO improvement #29115
Conversation
CI Results: |
Build Results: |
@@ -1,7 +1,7 @@ | |||
--- | |||
layout: docs | |||
page_title: KMIP - Profiles Support | |||
description: |- | |||
page_title: KMIP profiles version 1.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this change is accurate. @victorr ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with Scott, I think the original title is better (without "version 1.4").
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is fine to change the H1 header to match the title. The second paragraph informs of the KMIP version, so it is fine for the header to drop it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One suggestion to remove the duplicate use of "dynamically". Otherwise lgtm
Co-authored-by: Sarah Chavis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a comment/question about the use of "secrets engine plugin", but I am marking the PR as approved in case that intended.
IAM policies. | ||
page_title: AWS secrets engine | ||
description: >- | ||
Dynamically generate access keys based on IAM policies with the AWS secrets engine plugin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe remove plugin and use "...the AWS secrets engine"?
* Update the title & description for SEO improvement * Minor updates for style consistency * Revert back the change * Update website/content/docs/secrets/aws.mdx Co-authored-by: Sarah Chavis <[email protected]> --------- Co-authored-by: Sarah Chavis <[email protected]>
Description
This PR updates the secrets engine docs title & description for style consistency, as well as SEO improvement.
secrets/alicloud.mdx
secrets/aws.mdx
secrets/azure.mdx
secrets/consul.mdx
secrets/cubbyhole.mdx
secrets/gcp.mdx
secrets/gcpkms.mdx
secrets/index.mdx
secrets/kmip-profiles.mdx
secrets/kmip.mdx
secrets/kubernetes.mdx
secrets/ldap.mdx
secrets/mongodbatlas.mdx
secrets/nomad.mdx
secrets/rabbitmq.mdx
secrets/terraform.mdx
updates "Terraform Cloud" to say "HCP Terraform"secrets/totp.mdx
secrets/venafi.mdx
TODO only if you're a HashiCorp employee
backport/
label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x
, but older release branches will bebackport/ent/x.x.x+ent
.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.