Skip to content

[codex] clean up OAuth 2.0 docs styling, anchors, and OIDC quickstart guidance#104

Merged
basit3407 merged 7 commits intomainfrom
codex/remove-oauth-guide-emojis
Apr 1, 2026
Merged

[codex] clean up OAuth 2.0 docs styling, anchors, and OIDC quickstart guidance#104
basit3407 merged 7 commits intomainfrom
codex/remove-oauth-guide-emojis

Conversation

@basit3407
Copy link
Copy Markdown
Collaborator

@basit3407 basit3407 commented Apr 1, 2026

Summary

This PR started as an emoji-styling cleanup for the OAuth 2.0 tutorial and then picked up a small set of related OIDC documentation follow-ups on the same branch.

The result is a documentation polish PR that now covers visual cleanup, anchor stability, and a small amount of wording and AI-handoff refinement in the nearby OIDC quickstart docs.

What changed

  • removed decorative emoji styling from docs/tutorials/oidc/getting-started-with-oauth2.mdx
  • updated heading-linked anchors affected by the heading cleanup, including inbound links from:
    • docs/tutorials/oidc/user-apis-quickstart.mdx
    • docs/tutorials/oidc/mobile-apps/_intro.mdx
  • added explicit stable heading IDs for the OAuth2 tutorial FAQ jump targets and the How to Link QF Users to Your Data section so in-page links continue to work after heading cleanup
  • updated the User APIs quickstart AI handoff block to the same structured style used in the newer Content APIs quickstart
  • simplified client-type wording in the OAuth2 tutorial and User APIs quickstart to use reader-facing public / confidential terminology instead of exposing internal token-endpoint auth-method labels directly in the main guidance

Why

The original emoji cleanup improved the tone of the OAuth2 guide, but it also changed some generated fragment IDs and surfaced a few nearby OIDC doc inconsistencies. Keeping these follow-up fixes on the same branch makes the docs internally consistent and prevents broken in-page or cross-page links.

User impact

  • the OAuth2 tutorial reads more cleanly and professionally
  • in-page FAQ and section links keep working after the heading cleanup
  • the User APIs quickstart now matches the newer structured AI handoff format used elsewhere in the docs
  • client-type guidance is phrased in the public-vs-confidential language readers actually use when choosing an integration pattern

Validation

  • NO_UPDATE_NOTIFIER=1 CI=1 yarn build was run earlier on this branch after the larger doc changes
  • git diff --check
  • verified the updated How to Link QF Users to Your Data anchor and its FAQ link target locally

Notes

This PR does not change OAuth2 or API behavior. It updates documentation presentation, link stability, and reader-facing wording in the affected OIDC docs.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented Apr 1, 2026

Deploying qf-api-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 6f91da8
Status: ✅  Deploy successful!
Preview URL: https://3f5a1b57.qf-api-docs.pages.dev
Branch Preview URL: https://codex-remove-oauth-guide-emo.qf-api-docs.pages.dev

View logs

@basit3407 basit3407 marked this pull request as ready for review April 1, 2026 16:39
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 17983e7daa

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/tutorials/oidc/getting-started-with-oauth2.mdx Outdated
@basit3407
Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR aims to remove decorative emoji styling from the OAuth 2.0 tutorial docs to improve readability/professional tone, while also updating affected anchor links in related OIDC tutorial pages.

Changes:

  • Removed emoji prefixes from headings/callouts and adjusted related autogenerated anchors in the OAuth 2.0 tutorial.
  • Updated inbound links to the renamed “Why Use…” anchor.
  • Updated/rewrote portions of the “public vs confidential client” wording and expanded the “AI handoff” prompt content in the User APIs quickstart.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
docs/tutorials/oidc/getting-started-with-oauth2.mdx Removes decorative emoji styling across the guide and updates internal anchors/links accordingly.
docs/tutorials/oidc/user-apis-quickstart.mdx Updates wording related to public/confidential clients and revises the AI handoff prompt section.
docs/tutorials/oidc/mobile-apps/_intro.mdx Updates link fragment to match the new “Why Use…” heading anchor in the OAuth2 tutorial.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/tutorials/oidc/user-apis-quickstart.mdx
Comment thread docs/tutorials/oidc/user-apis-quickstart.mdx
Comment thread docs/tutorials/oidc/getting-started-with-oauth2.mdx
@basit3407 basit3407 changed the title [codex] remove decorative emoji styling from the OAuth 2.0 guide Apr 1, 2026
@basit3407 basit3407 merged commit ac25b97 into main Apr 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants