You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/interop/guest/overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Developers can experiment with the capabilities on multiple levels to evaluate,
33
33
34
34
You can create an identity and access token for Teams external users on Azure portal without a single line of code. [Here are steps how to do it](../../../quickstarts/identity/quick-create-identity.md).
35
35
36
-
With a valid identity, access token, and Teams meeting URL, you can use [Azure Communication Services UI Library](https://azure.github.io/communication-ui-library/?path=/story/composites-call-with-chat-jointeamsmeeting--join-teams-meeting) to join Teams meeting without any code.
36
+
With a valid identity, access token, and Teams meeting URL, you can use [Azure Communication Services UI Library](https://azure.github.io/communication-ui-library/?path=/story/composites-callwithchatcomposite-join-teams-meeting--join-teams-meeting) to join Teams meeting without any code.
@@ -49,7 +49,7 @@ The data flow for joining Teams meetings is available at the [client and server
49
49
50
50
High-level coding articles:
51
51
-[Authenticate as Teams external user](../../../quickstarts/identity/access-tokens.md)
52
-
-[Call with Chat Composite](https://azure.github.io/communication-ui-library/?path=/docs/composites-call-with-chat-basicexample--basic-example)
52
+
-[Call with Chat Composite](https://azure.github.io/communication-ui-library/?path=/story/composites-call-with-chat-basicexample-basic-example--basic-example)
53
53
54
54
Low-level coding articles:
55
55
-[Join Teams meeting audio and video as Teams external user](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/rooms/room-concept.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,7 +115,7 @@ Follow these steps to add a PSTN number to a room call using Call Automation SDK
115
115
116
116
Use the [Calling SDKs](../voice-video-calling/calling-sdk-features.md) to join the room call. Room calls can be joined using the Web, iOS, or Android Calling SDKs. You can find quick start samples for joining room calls [here](../../quickstarts/rooms/join-rooms-call.md).
117
117
118
-
Rooms can also be accessed using the [Azure Communication Services UI Library](https://azure.github.io/communication-ui-library/?path=/docs/rooms--page). The UI Library enables developers to add a call client that is Rooms-enabled into their application with only a couple lines of code.
118
+
Rooms can also be accessed using the [Azure Communication Services UI Library](https://azure.github.io/communication-ui-library/?path=/docs/concepts-rooms--docs). The UI Library enables developers to add a call client that is Rooms-enabled into their application with only a couple lines of code.
119
119
120
120
### Client initiated PSTN Dial-out using Calling client SDK
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/ui-library/includes/web-ui-library.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ These UI client libraries all use [Microsoft's Fluent design language](https://d
25
25
26
26
In conjunction to the UI components, the UI Library exposes a stateful client library for calling and chat.
27
27
This client is agnostic to any specific state management framework and can be integrated with common state managers like Redux or React Context.
28
-
This stateful client library can be used with the UI Components to pass props and methods for the UI Components to render data. For more information, see [Stateful Client Overview](https://azure.github.io/communication-ui-library/?path=/docs/statefulclient-overview--page).
28
+
This stateful client library can be used with the UI Components to pass props and methods for the UI Components to render data. For more information, see [Stateful Client Overview](https://azure.github.io/communication-ui-library/?path=/docs/stateful-client-overview--docs).
29
29
30
30
> [!NOTE]
31
31
> The same components and composites offered in the UI Library are available in the [Design Kit for Figma](https://www.figma.com/community/file/1095841357293210472), so you can quickly design and prototype your calling and chat experiences.
@@ -37,28 +37,28 @@ Developers can easily instantiate the Composite using an Azure Communication Ser
37
37
38
38
| Composite | Use Cases |
39
39
| ------------ | ---------- |
40
-
|[CallwithChatComposite](https://azure.github.io/communication-ui-library/?path=/docs/composites-call-with-chat-basicexample--basic-example)| Experience combining calling and chat features to allow users to start or join a call and chat thread. In the experience, the user has the ability to both communicate using voice and video, and access to a rich chat thread where messages can be exchanged between participants. It includes support for Teams Interop. |
41
-
|[CallComposite](https://azure.github.io/communication-ui-library/?path=/docs/composites-call-basicexample--basic-example)| Calling experience that allows users to start or join a call. Inside the experience users can configure their devices, participate in the call with video, and see other participants, including those participants with video turn-on. For Teams Interop, is included lobby functionality for user to wait to be admitted. |
42
-
|[ChatComposite](https://azure.github.io/communication-ui-library/?path=/docs/composites-chat-basicexample--basic-example)| Chat experience where user can send and receive messages. Thread events like typing, reads, participants entering and leaving are displayed to the user as part of the chat thread. |
40
+
|[CallwithChatComposite](https://azure.github.io/communication-ui-library/?path=/docs/composites-callwithchatcomposite--docs)| Experience combining calling and chat features to allow users to start or join a call and chat thread. In the experience, the user has the ability to both communicate using voice and video, and access to a rich chat thread where messages can be exchanged between participants. It includes support for Teams Interop. |
41
+
|[CallComposite](https://azure.github.io/communication-ui-library/?path=/docs/composites-callcomposite--docs)| Calling experience that allows users to start or join a call. Inside the experience users can configure their devices, participate in the call with video, and see other participants, including those participants with video turn-on. For Teams Interop, is included lobby functionality for user to wait to be admitted. |
42
+
|[ChatComposite](https://azure.github.io/communication-ui-library/?path=/docs/composites-chatcomposite--docs)| Chat experience where user can send and receive messages. Thread events like typing, reads, participants entering and leaving are displayed to the user as part of the chat thread. |
43
43
## UI Component overview
44
44
45
45
Pure UI Components can be used for the developers, to compose communication experiences, from stitching video tiles into a grid to showcase remote participants, to organizing components to fit your applications specifications.
46
46
UI Components support customization to give the components the right feel and look to match an applications branding and style.
47
47
48
48
| Area | Component | Description |
49
49
| ------- | ------------ | ----------------- |
50
-
| Calling |[Grid Layout](https://azure.github.io/communication-ui-library/?path=/story/ui-components-gridlayout--grid-layout)| Grid component to organize Video Tiles into an NxN grid |
51
-
||[Video Tile](https://azure.github.io/communication-ui-library/?path=/story/ui-components-videotile--video-tile)| Component that displays video stream when available and a default static component when not |
52
-
||[Control Bar](https://azure.github.io/communication-ui-library/?path=/story/ui-components-controlbar--control-bar)| Container to organize DefaultButtons to hook up to specific call actions like mute or share screen |
53
-
||[VideoGallery](https://azure.github.io/communication-ui-library/?path=/story/ui-components-video-gallery--video-gallery)| Turn-key video gallery component, which dynamically changes as participants are added |
54
-
||[Dialpad](https://azure.github.io/communication-ui-library/?path=/docs/ui-components-dialpad--dialpad)| Component to support phone number input and DTMF tones |
55
-
| Chat |[Message Thread](https://azure.github.io/communication-ui-library/?path=/story/ui-components-messagethread--message-thread)| Container that renders chat messages, system messages, and custom messages |
56
-
||[Send Box](https://azure.github.io/communication-ui-library/?path=/story/ui-components-sendbox--send-box)| Text input component with a discrete send button |
57
-
||[Rich Text Send Box](https://azure.github.io/communication-ui-library/?path=/docs/ui-components-richtextsendbox--rich-text-send-box)| Rich text input component with formatting options and a discrete send button |
58
-
||[Message Status Indicator](https://azure.github.io/communication-ui-library/?path=/story/ui-components-messagestatusindicator--message-status-indicator)| Multi-state read receipt component to show state of sent message |
59
-
||[Typing indicator](https://azure.github.io/communication-ui-library/?path=/story/ui-components-typingindicator--typing-indicator)| Text component to render the participants who are actively typing on a thread |
60
-
| Common |[Participant Item](https://azure.github.io/communication-ui-library/?path=/story/ui-components-participantitem--participant-item)| Common component to render a call or chat participant including avatar and display name |
61
-
||[Participant List](https://azure.github.io/communication-ui-library/?path=/story/ui-components-participantlist--participant-list)| Common component to render a call or chat participant list including avatar and display name |
50
+
| Calling |[Grid Layout](https://azure.github.io/communication-ui-library/?path=/docs/components-grid-layout--docs)| Grid component to organize Video Tiles into an NxN grid |
51
+
||[Video Tile](https://azure.github.io/communication-ui-library/?path=/docs/components-video-tile--docs)| Component that displays video stream when available and a default static component when not |
52
+
||[Control Bar](https://azure.github.io/communication-ui-library/?path=/docs/components-controlbar-control-bar--docs)| Container to organize DefaultButtons to hook up to specific call actions like mute or share screen |
53
+
||[VideoGallery](https://azure.github.io/communication-ui-library/?path=/docs/components-video-gallery--docs)| Turn-key video gallery component, which dynamically changes as participants are added |
54
+
||[Dialpad](https://azure.github.io/communication-ui-library/?path=/docs/components-dialpad--docs)| Component to support phone number input and DTMF tones |
55
+
| Chat |[Message Thread](https://azure.github.io/communication-ui-library/?path=/docs/components-message-thread--docs)| Container that renders chat messages, system messages, and custom messages |
56
+
||[Send Box](https://azure.github.io/communication-ui-library/?path=/docs/components-sendbox-send-box--docs)| Text input component with a discrete send button |
57
+
||[Rich Text Send Box](https://azure.github.io/communication-ui-library/?path=/docs/components-sendbox-rich-text-send-box--docs)| Rich text input component with formatting options and a discrete send button |
58
+
||[Message Status Indicator](https://azure.github.io/communication-ui-library/?path=/story/components-message-status-indicator--message-status-indicator)| Multi-state read receipt component to show state of sent message |
59
+
||[Typing indicator](https://azure.github.io/communication-ui-library/?path=/docs/components-typing-indicator--docs)| Text component to render the participants who are actively typing on a thread |
60
+
| Common |[Participant Item](https://azure.github.io/communication-ui-library/?path=/docs/components-participant-item--docs)| Common component to render a call or chat participant including avatar and display name |
61
+
||[Participant List](https://azure.github.io/communication-ui-library/?path=/docs/components-participant-list--docs)| Common component to render a call or chat participant list including avatar and display name |
62
62
63
63
## Installing Web UI Library
64
64
@@ -75,7 +75,7 @@ Understanding these requirements help you choose the right client library:
75
75
-**How much customization do you desire?** Azure Communication core client libraries don't have a UX and are designed so you can build whatever UX you want. UI Library components provide UI assets at the cost of reduced customization.
76
76
-**What platforms are you targeting?** Different platforms have different capabilities.
77
77
78
-
Details about feature availability in the [UI Library is available here](https://azure.github.io/communication-ui-library/?path=/story/use-cases--page), but key trade-offs are summarized in the next table.
78
+
Details about feature availability in the [UI Library is available here](https://azure.github.io/communication-ui-library/?path=/docs/use-cases--docs), but key trade-offs are summarized in the next table.
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/ui-library/includes/web-ui-use-cases.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,9 +70,9 @@ When you add both calling and chat to an application, remember that the chat cli
70
70
71
71
If you use UI components to deliver Teams interoperability experiences, begin by using UI Library examples to create key pieces of the experience:
72
72
73
-
-[Lobby example](https://azure.github.io/communication-ui-library/?path=/story/examples-teams-interop--lobby): A sample lobby where a participant can wait to be admitted to a call.
74
-
-[Compliance banner](https://azure.github.io/communication-ui-library/?path=/story/examples-teams-interop--compliance-banner): A sample banner that shows the user if the call is being recorded.
75
-
-[Teams theme](https://azure.github.io/communication-ui-library/?path=/story/examples-themes--teams): A sample theme that makes UI Library elements look like Microsoft Teams.
73
+
-[Lobby example](https://azure.github.io/communication-ui-library/?path=/docs/concepts-teams-interop-lobby--docs): A sample lobby where a participant can wait to be admitted to a call.
74
+
-[Compliance banner](https://azure.github.io/communication-ui-library/?path=/docs/concepts-teams-interop-compliance-banner--docs): A sample banner that shows the user if the call is being recorded.
75
+
-[Teams theme](https://azure.github.io/communication-ui-library/?path=/docs/examples-themes-teams--docs): A sample theme that makes UI Library elements look like Microsoft Teams.
76
76
-[Image sharing\*](../../../tutorials/inline-image-tutorial-interop-chat.md): A sample that shows how an Azure Communication Services user can receive images sent by the Teams user.
77
77
-[File sharing\*](../../../tutorials/file-sharing-tutorial-interop-chat.md): A sample that shows how an Azure Communication Services user can receive file attachments sent by the Teams user.
0 commit comments