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: docs/design/add-in-color.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Color guidelines for Office Add-ins
3
3
description: Learn how to use colors in the UI of an Office Add-in.
4
-
ms.date: 06/18/2024
4
+
ms.date: 10/28/2025
5
5
ms.topic: best-practice
6
6
ms.localizationpriority: medium
7
7
---
@@ -12,16 +12,18 @@ Color is often used to emphasize brand and reinforce visual hierarchy. It helps
12
12
13
13

14
14
15
+
## Use UI component libraries
15
16
[Fluent UI React](../quickstarts/fluent-react-quickstart.md) and [Fabric Core](fabric-core.md) include a set of default theme colors. When these libraries are applied to the components or layouts of an Office Add-in, the same goals apply. Color should communicate hierarchy, purposefully guiding customers to action without interfering with content. Theme colors from Fluent UI React or Fabric Core can introduce a new accent color to the overall interface. These accent colors can conflict with Office app branding and the hierarchy. Consider ways to avoid conflicts and interference. Use neutral accents or overwrite theme colors to match Office app branding or your own brand colors.
16
17
18
+
## Develop with theming APIs
17
19
In Office applications, customers personalize their interfaces by applying an [Office UI theme](https://support.microsoft.com/office/365-63e65e1c-08d4-4dea-820e-335f54672310). Customers choose between four UI themes to vary styling of backgrounds and buttons in Excel, Outlook, PowerPoint, Word, and other apps in the Office suite. To make your add-ins feel like a natural part of Office and respond to personalization, use our [Theming APIs](/javascript/api/office/office.officetheme). For example, task pane background colors switch to a dark gray in some themes. With the Theming APIs, follow suit and adjust foreground text to ensure [accessibility](../design/accessibility-guidelines.md).
18
20
19
21
> [!TIP]
20
22
>
21
23
> - To ensure that your add-in applies the correct color combinations in its UI, test it with all four Office themes, including the **Use system setting** option.
22
24
> - For guidance on how to dynamically match the design of your PowerPoint add-in with the current document or Office theme, see [Use document themes in your PowerPoint add-ins](../powerpoint/use-document-themes-in-your-powerpoint-add-ins.md).
23
25
24
-
Apply the following general guidelines for color.
26
+
## Apply best practices
25
27
26
28
- Use color sparingly to communicate hierarchy and reinforce brand.
27
29
- Overuse of a single accent color applied to both interactive and non-interactive elements can lead to confusion. For example, avoid using the same color for selected and unselected items in a navigation menu.
@@ -30,3 +32,10 @@ Apply the following general guidelines for color.
30
32
- Ensure that all text is [accessible](accessibility-guidelines.md). Be sure that there is a 4.5:1 contrast ratio between foreground text and background.
31
33
- Be aware of color blindness. Use more than just color to indicate interactivity and hierarchy.
32
34
- To learn more about designing add-in command icons with the Office icon color palette, see [icon guidelines](../design/add-in-icons.md).
title: Branding patterns design guidelines for Office Add-ins
3
3
description: Learn how to brand your Office Add-in while staying compatible with the visual design of Office.
4
-
ms.date: 05/18/2023
4
+
ms.date: 10/29/2025
5
5
ms.topic: best-practice
6
6
ms.localizationpriority: medium
7
7
---
8
8
9
9
# Branding patterns
10
10
11
-
These patterns provide brand visibility and context to your add-in users.
11
+
Implement recommended design patterns in your add-in to promote brand visibility while maintaining seamless integration with Office applications.
12
12
13
13
## Best practices
14
14
15
+
The following table outlines design best practices to enhance your add-in's brand recognition.
16
+
15
17
|Do |Don't|
16
18
|:---- |:----|
17
19
| Use familiar UI components with applied branding accents like typography and color. | Don't invent new UI components that contradict established Office UI. |
@@ -20,16 +22,26 @@ These patterns provide brand visibility and context to your add-in users.
20
22
| Make your solution recognizable and connect your screens together with consistent visual elements. | Don't hide your solution with unrecognizable and inconsistently applied visual elements. |
21
23
| Build connection with a parent service or business to ensure that customers know and trust your solution. | Don't make customers learn a new brand concept if there's a useful and understandable relationship that can be leveraged to build trust and value. |
22
24
23
-
Apply the following patterns and components as applicable to allow users to embrace the full utility of your add-in.
25
+
## Design patterns and components
26
+
27
+
Apply the following patterns and components to allow users to embrace the full utility of your add-in.
24
28
25
-
## Brand Bar
29
+
###Brand Bar
26
30
27
31
The brand bar is a space in the footer to include your brand name and logo. It also serves as a link to your brand's website and an optional access location.
28
32
29
33

30
34
31
-
## Splash Screen
35
+
###Splash Screen
32
36
33
37
Use this screen to display your branding while the add-in is loading or transitioning between UI states.
34
38
35
39

-[Fabric Core motion and animation patterns](https://developer.microsoft.com/fluentui#/styles/web/motion)
36
36
37
-
Use it to fit seamlessly in your add-in. It will help you create experiences that are more felt than observed. The animation CSS classes provide directionality, enter/exit, and duration specifics that reinforce Office mental models and provide opportunities for customers to learn how to interact with your add-in.
37
+
Use it to fit seamlessly in your add-in. It will help you create experiences that are more felt than observed. The animation CSS classes provide directionality, enter, exit, and duration specifics that reinforce Office mental models and provide opportunities for customers to learn how to interact with your add-in.
Copy file name to clipboardExpand all lines: docs/develop/dialog-video.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
---
2
2
title: Use the Office dialog box to play a video
3
3
description: Learn how to open and play a video in the Office dialog box to create engaging user experiences.
4
-
ms.date: 09/25/2025
4
+
ms.date: 10/29/2025
5
5
ms.topic: how-to
6
6
ms.localizationpriority: medium
7
7
---
8
8
9
9
# Use the Office dialog box to show a video
10
10
11
-
This article shows you how to play a video in an Office Add-in dialog box to create more engaging user experiences.
11
+
Play a video in an Office Add-in dialog box to create more engaging user experiences.
12
12
13
13
Videos in dialog boxes are perfect for:
14
14
@@ -23,7 +23,7 @@ To play a video in a dialog box with the Office dialog API, follow these steps.
23
23
24
24
1. Create a dedicated video page that contains an iframe and no other content. The page must be in the same domain as the host page. For a reminder of what a host page is, see [Open a dialog box from a host page](dialog-api-in-office-add-ins.md#open-a-dialog-box-from-a-host-page).
25
25
26
-
In the `src` attribute of the iframe, point to the URL of an online video. The protocol of the video's URL must be HTTPS. In this example, we'll call this page "video.dialogbox.html".
26
+
In the `src` attribute of the iframe, point to the URL of an online video. The protocol of the video's URL must be HTTPS. In this example, we'll call this page **video.dialogbox.html**.
27
27
28
28
Here's the markup:
29
29
@@ -34,12 +34,18 @@ To play a video in a dialog box with the Office dialog API, follow these steps.
34
34
</iframe>
35
35
```
36
36
37
-
1. Call `displayDialogAsync` in the host page to open "video.dialogbox.html".
37
+
1. Call `displayDialogAsync` in the host page to open **video.dialogbox.html**.
38
38
39
-
1. Handle dialog close events (optional). If your add-in needs to know when the user closes the dialog box, register a handler for the `DialogEventReceived` event and handle the 12006 event. For details, see [Errors and events in the Office dialog box](dialog-handle-errors-events.md).
39
+
1. (Optional) If your add-in needs to know when the user closes the dialog, handle dialog close events. Register a handler for the `DialogEventReceived` event and handle the 12006 event. For details, see [Errors and events in the Office dialog box](dialog-handle-errors-events.md).
40
40
41
41
## See it in action
42
42
43
43
For a sample of a video playing in a dialog box, see the [video placemat design pattern](../design/first-run-experience-patterns.md#video-placemat).
44
44
45
45

46
+
47
+
## See also
48
+
49
+
- [Use the Office dialog API in your Office Add-ins](dialog-api-in-office-add-ins.md)
50
+
- [Best practices and rules for the Office Dialog API](dialog-best-practices.md)
51
+
- [Handle errors and events in the Office dialog box](dialog-handle-errors-events.md)
0 commit comments