Skip to content

Update access token tier and version info

Craig Norris requested to merge docs-access-token-tier-info into master

What does this MR do?

This MR updates the doc page to both ensure that the tier badge is added to the page title, and to remove now-outdated version references, now that we're at 14.1.

I selected **(FREE)** for the page based on it's content, but if it needs to be changed, feel free to do so.

I also removed the initial "Introduced in" line in the version section. To ensure that version formatting for the remaining info persisted, I revamped the info to keep the "Introduced in" wording in place, as the formatting uses a regex that looks for that wording to put the formatting in place. I also revised a table on the page to remove the version column, as there were only 2 lines that mentioned a version that's still referenced. For those lines, I just incorporated the information into the description. The hope is that with less information, it's easier for users to scan.

Author's checklist

To avoid having this MR be added to code verification QA issues, don't add these labels: feature, frontend, backend, ~"bug", or database

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.
Edited by Craig Norris

Merge request reports