preserve casing in generated docs page slugs

[bcherry]

right now these get lowercased which makes the links less readable

[changeset-bot]

🦋 Changeset detected

Latest commit: ade62d4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@livekit/api-documenter	Patch
@livekit/components-docs-gen	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

size-limit report 📦

Path	Size
LiveKitRoom only	6.05 KB (0%)
LiveKitRoom with VideoConference	29.82 KB (0%)
All exports	36.51 KB (0%)

[Ocupe]

I can understand the motivation, but I don't think the gain is worth the cost (on the docs site) of the change.
This is of course a discussion about tased, but I don't particularly like case sensitive urls and would rather change it to kebab-case if we have to change it at all.

[bcherry]

@Ocupe next.js URLs are already case sensitive (see https://docs.livekit.io/reference/components/react/component/audiotrack/ which works, but https://docs.livekit.io/reference/components/react/component/AUDIOTRACK/ is a 404), this just applies a more appropriate casing.

From what I see, most reference docs maintain casing exactly as is in the original language:

React's own docs keep original casing: https://react.dev/reference/react/useDeferredValue
Python generated docs also keep casing, but its more of a mess anyways: https://docs.livekit.io/python/livekit/agents/stt/fallback_adapter.html#livekit.agents.stt.fallback_adapter.AvailabilityChangedEvent
and typedoc keeps casing too https://docs.livekit.io/client-sdk-js/enums/KeyProviderEvent.html

two exceptions I found are swift/apple, which are all lowercase: https://developer.apple.com/documentation/avfoundation/avplayer/init(playeritem:)

and kotlin/android, which are indeed kebab-case https://docs.livekit.io/components-android/livekit-compose-components/io.livekit.android.compose.state.transcriptions/remember-participant-transcriptions.html

I'm fine with going to kebab case here if that's what people prefer, but I don't love the current all lowercase...

[Ocupe]

@Ocupe next.js URLs are already case sensitive (see https://docs.livekit.io/reference/components/react/component/audiotrack/ which works, but https://docs.livekit.io/reference/components/react/component/AUDIOTRACK/ is a 404), this just applies a more appropriate casing.

@bcherry I see my mistake now. I meant to say that I don't like the look of urls with non-uppercase characters. But as I said, that is just my taste.

From what I see, most reference docs maintain casing exactly as is in the original language:

React's own docs keep original casing: https://react.dev/reference/react/useDeferredValue Python generated docs also keep casing, but its more of a mess anyways: https://docs.livekit.io/python/livekit/agents/stt/fallback_adapter.html#livekit.agents.stt.fallback_adapter.AvailabilityChangedEvent and typedoc keeps casing too https://docs.livekit.io/client-sdk-js/enums/KeyProviderEvent.html

two exceptions I found are swift/apple, which are all lowercase: https://developer.apple.com/documentation/avfoundation/avplayer/init(playeritem:)

and kotlin/android, which are indeed kebab-case https://docs.livekit.io/components-android/livekit-compose-components/io.livekit.android.compose.state.transcriptions/remember-participant-transcriptions.html

I'm fine with going to kebab case here if that's what people prefer, but I don't love the current all lowercase...

Thanks for listing some examples from other docs, I appreciate the overview!
My feeling is that most people don't really care about this, so why change it when we have the burden of backwards compatibility on the docs site?
That being said, and because I don't have a strong opinion (just a slight dislike :P), I'll leave the decision up to you.