Add react native tutorials

[Karolk99]

Description

Describe your changes in detail

[Copilot]

Pull request overview

This PR reorganizes and expands the Media over QUIC (MoQ) documentation by introducing a dedicated MoQ top-level navigation tab with its own sidebar, and by splitting/adding MoQ tutorials for both web and React Native.

Changes:

• Added a new moqSidebar and updated sidebar generation to prevent MoQ docs from appearing in the main Docs sidebar.
• Added a MoQ navbar entry (pointing at /next/...) and introduced redirects for legacy MoQ doc routes.
• Created/updated MoQ docs structure: Concepts + Tutorials categories, plus new Web Publishing and React Native Publishing/Subscribing tutorials, and refactored the existing web tutorial into “Web Subscribing”.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
sidebars/docs.ts	Adds a dedicated moqSidebar autogenerated from docs/moq.
redirects/index.ts	Adds redirect rules for older MoQ doc paths to the new MoQ section paths.
docusaurus.config.ts	Filters MoQ category out of the main docs sidebar and adds a MoQ navbar tab.
docs/moq/tutorials/web-subscribing.mdx	Refactors the existing MoQ tutorial into a focused web subscribing guide and updates links/structure.
docs/moq/tutorials/web-publishing.mdx	Adds a new web publishing tutorial.
docs/moq/tutorials/react-native-subscribing.mdx	Adds a new React Native subscribing tutorial using react-native-moq.
docs/moq/tutorials/react-native-publishing.mdx	Adds a new React Native publishing tutorial using react-native-moq.
docs/moq/tutorials/category.json	Adds Tutorials category metadata for MoQ docs.
docs/moq/concepts/moq-with-fishjam.mdx	Renames/repositions the MoQ concept doc and updates cross-links.
docs/moq/concepts/category.json	Adds Concepts category metadata for MoQ docs.
docs/moq/category.json	Adds MoQ root category metadata and customProps.topNavSection used for sidebar filtering.

---

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

[czerwiukk]

thought: the react native publishing/subscribing title is not self explanatory. i'd add the moq or stream keyword to that

[Karolk99]

I encourage you to start it locally, there is a separate tab called moq in which these tutorials are located

[czerwiukk]

Why not nest MoQ tutorials like web&mobile/backend in how to section? IMO creating a separate sidebar makes it harder to navigate in the docs. I'm not sure splitting our docs in half around the webrtc/moq distinction is a good idea.
also - "moq subscribing/publishing" seems like a diataxis "goal", so the moq articles could fit in the how to -> moq location.

[Karolk99]

Why not nest MoQ tutorials like web&mobile/backend in how to section? IMO creating a separate sidebar makes it harder to navigate in the docs. I'm not sure splitting our docs in half around the webrtc/moq distinction is a good idea.

In my opinion split is necessary, because non of the docs from WebRTC section relates to MoQ so it's misleading without this destinction

[PiotrWodecki]

@czerwiukk the issue is that many of our features do not work with moq which is not immediately obvious (agents, VAD, etc.), so the split is there to make that more obvious. Initially I was hoping we could keep it merged, but I don't see how it would make sense this way.

[czerwiukk]

split is there to make that more obvious

I'd put a big warning note in the MoQ concept article explicitly stating whats possible and what not. Putting everything in a separate tab doesn't suggest the features aren't interoperable. If we want to ship quick, let's make small changes and iterate, rather than introduce concepts on the fly that feel intuitive to us, not necessarily the end user.

[PiotrWodecki]

lgtm contentwise, but the separation needs slightly better execution

[PiotrWodecki]

issue (blocking): I really don't like the idea of calling this section WebRTC. The split seems necessary, for now, but we shouldn't drop the idea of someone not needing to know what WebRTC is.

I don't have a better suggestion for now, but we need it.

[PiotrWodecki]

nitpick: @moq misses a link

[PiotrWodecki]

split is there to make that more obvious

I'd put a big warning note in the MoQ concept article explicitly stating whats possible and what not. Putting everything in a separate tab doesn't suggest the features aren't interoperable. If we want to ship quick, let's make small changes and iterate, rather than introduce concepts on the fly that feel intuitive to us, not necessarily the end user.

I agree this could work, let's give it a try @Karolk99