Skip to content
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

Merged
merged 10 commits into from
Dec 18, 2024

Conversation

yhyakuna
Copy link
Contributor

@yhyakuna yhyakuna commented Dec 6, 2024

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 Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    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.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@yhyakuna yhyakuna self-assigned this Dec 6, 2024
@yhyakuna yhyakuna requested review from a team as code owners December 6, 2024 00:21
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Dec 6, 2024
Copy link

github-actions bot commented Dec 6, 2024

CI Results:
All Go tests succeeded! ✅

Copy link

github-actions bot commented Dec 6, 2024

Build Results:
All builds succeeded! ✅

@@ -1,7 +1,7 @@
---
layout: docs
page_title: KMIP - Profiles Support
description: |-
page_title: KMIP profiles version 1.4
Copy link
Collaborator

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 ?

Copy link
Contributor

@victorr victorr Dec 6, 2024

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").

Copy link
Contributor Author

@yhyakuna yhyakuna Dec 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is a hidden file, I can revert it back.

Ideally, we want the page_title and the H1 header to match.

@victorr Do you want to keep the H1 header as-is though? Right now, the H1 header is: # KMIP profiles version 1.4

image

Copy link
Contributor

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.

schavis
schavis previously approved these changes Dec 6, 2024
Copy link
Contributor

@schavis schavis left a 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

website/content/docs/secrets/aws.mdx Outdated Show resolved Hide resolved
Copy link
Contributor

@victorr victorr left a 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.
Copy link
Contributor

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"?

@schavis schavis merged commit f975259 into main Dec 18, 2024
33 of 34 checks passed
@schavis schavis deleted the docs/secrets-seo-updates-1 branch December 18, 2024 23:37
Monkeychip pushed a commit that referenced this pull request Dec 20, 2024
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants