Skip to content

Conversation

@manovotny
Copy link
Contributor

@manovotny manovotny commented Jan 21, 2026

Warning

Depends on https://github.com/clerk/clerk/pull/2018, which must be merged first.

Previews

What does this solve?

  • Fixes a copy-paste error in the manifest where Android User Management incorrectly linked to the iOS documentation path
  • Improves SDK scoping logic to properly handle cases where groups have explicit SDK restrictions (e.g., Mobile Navigation should only appear for ios/android)
  • Adds support for manifest headings with optional SDK scoping via the new ManifestHeading type

What changed?

  • docs/manifest.json: Fixed Android link and added Mobile Navigation section for iOS/Android with new heading-based structure
  • scripts/build-docs.ts: Refined SDK computation to include frontmatter SDK variants and clarified SDK precedence logic
  • scripts/lib/manifest.ts: Added ManifestHeading type to support section headings with SDK scoping
  • Docs content: Removed Android-specific passkey references and updated Apple sign-in SDK conditionals to reflect mobile navigation restructure

manovotny and others added 2 commits January 20, 2026 16:42
Adds a new ManifestHeading type to support items with `heading: true`
that act as section headers without an href. Also fixes SDK filtering
errors by removing android/ios conditionals from pages under the Guides
section which doesn't include those SDKs.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
- Fix copy-paste error: Android User Management now correctly links to /docs/reference/android/user instead of iOS path
- Add frontmatter SDK to SDK computation for manifest items to better reflect document capabilities
- Clarify SDK scoping precedence: explicit group SDK restrictions are now preserved even if children support more SDKs
- Update comments to explain SDK logic for cases like Mobile Navigation section
@vercel
Copy link

vercel bot commented Jan 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clerk-docs Ready Ready Preview Feb 3, 2026 6:02pm

Request Review

- Add iOS reference docs from mike/ios-v1-docs branch: auth, clerk, configuration, installation, organizations, user
- Add Android auth.mdx from sam/android-v1-auth-reference branch
- Create docs/reference/android/todo.mdx placeholder for missing Android docs
- Update manifest to point missing Android docs to the todo placeholder
- Add iOS quickstart guide
- Update 12 custom flow guides with iOS support
- Update reference view docs (auth-view, user-button, user-profile-view)
- Update iOS overview and remove deprecated get-token.mdx
- Update manifest: remove iOS getToken entry, point Android auth to todo placeholder
- Add installation.mdx with Gradle setup instructions
- Add configuration.mdx with Clerk.initialize() pattern
- Add clerk.mdx with reactive state flows (Clerk.userFlow, Clerk.isInitialized)
- Add user.mdx for user management methods
- Add organizations.mdx for organization management
- Update auth.mdx to use Clerk.auth (uppercase) consistently
- Update manifest.json to point to new Android reference pages

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@SarahSoutoul
Copy link
Contributor

SarahSoutoul commented Feb 1, 2026

@mikepitre @swolfand

Have pushed a final docs review after reviewing more closely the content. That review mostly focuses on consistency when comparing the different variants (iOS vs Android).

One thing I did notice is that for the auth docs, there are inconsistencies around these two sections (android vs iOS). I wanted to double check with you both on whether that is intentional or should be fixed.

Screenshot 2026-01-31 at 1 24 23 pm Screenshot 2026-01-31 at 1 24 17 pm

Also left a separate comment for you @swolfand here: #2992 (comment).

Tagging you @manovotny @alexisintech for visibility.


**Users can only create passkeys after signing up**, so you'll need to enable another authentication strategy for the sign-up process. After signing in, users can create a passkey.

<If sdk="android">
Copy link
Contributor

Choose a reason for hiding this comment

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


**Users can only create passkeys after signing up**, so you'll need to enable another authentication strategy for the sign-up process. After signing in, users can create a passkey.

<If sdk="android">
Copy link
Contributor

Choose a reason for hiding this comment

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

And did the same for the social connections apple guide: Refinements

Comment on lines 13 to 20
```kotlin
dependencies {
// For prebuilt UI components (includes API)
implementation("com.clerk:clerk-android-ui:1.0.0")

// Or for API only (no UI)
implementation("com.clerk:clerk-android-api:1.0.0")
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Two things on this @swolfand:

  1. In the quickstart, we also import the Lifecycle ViewModel Compose Library: implementation("androidx.lifecycle:lifecycle-viewmodel-compose:2.9.2"). Is it needed here too?

  2. The version for both of these imports is 1.0.0, but that might change no? Do we want to have <latest-version> instead like we do in the Quickstart?

Copy link
Contributor

Choose a reason for hiding this comment

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

  • for the first I think this is just installation of the clerk sdks, not doing the quickstart,
  • Yes! will change

Copy link
Contributor

Choose a reason for hiding this comment

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

For the dependencies change @swolfand, I meant to change the dependency to latest-version on the installation guide. And on the upgrade guide, leave it as 1.0.0 as we're on the v1 upgrade guide. Made a commit to make those changes.

@mikepitre
Copy link
Contributor

@mikepitre @swolfand

Have pushed a final docs review after reviewing more closely the content. That review mostly focuses on consistency when comparing the different variants (iOS vs Android).

One thing I did notice is that for the auth docs, there are inconsistencies around these two sections (android vs iOS). I wanted to double check with you both on whether that is intentional or should be fixed.

Screenshot 2026-01-31 at 1 24 23 pm Screenshot 2026-01-31 at 1 24 17 pm
Also left a separate comment for you @swolfand here: #2992 (comment).

Tagging you @manovotny @alexisintech for visibility.

Ah good catch @SarahSoutoul! Sam's is correct here. I'll get iOS updated to match.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants