Move OpenAPI mention and link to doc first

What does this MR do?

• Move the OpenAPI link under REST API heading to clarify it's not another type of API, but it's the REST API in another format.
• Link instead to the doc page that explains OpenAPI. You can get there from that page.

Related issues

• !74461 (comment 748338728)
• #348292 (moved)

Author's checklist

• Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• Ensure that the product tier badge is added to topic's h1.
• Request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

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 reviews above. Maintainer's review can occur before or after a technical writer review.
• Ensure a release milestone is set.

changed milestone to %14.6

added Technical Writing docsimprovement documentation groupintegrations [DEPRECATED] twdoing typemaintenance + 1 deleted label

assigned to @msedlakjakubowski

@kpaizee @.luke This MR might improve the clarity of the API page intro, and address one point of confusion as highlighted by @kballon in !74461 (comment 772617887).

requested review from @kpaizee and @.luke

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/api/index.md

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

approved this merge request

added sectiondev label

approved this merge request

removed review request for @.luke

resolved all threads

enabled an automatic merge when the pipeline for c63cbcea succeeds

merged

mentioned in commit 1486aa2c

added workflowstaging label

added workflowcanary label and removed workflowstaging label

added workflowproduction label and removed workflowcanary label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label

added devopsmanage label and removed 1 deleted label

added groupimport and integrate label and removed groupintegrations [DEPRECATED] label