@planningcenter/tapestry 4.13.0 → 4.14.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/componentRegistrars.d.ts +1 -0
- package/dist/componentRegistrars.d.ts.map +1 -1
- package/dist/componentRegistrars.js +7 -1
- package/dist/componentRegistrars.js.map +1 -1
- package/dist/components/DataTable/ActiveFilterInstance.d.ts +3 -3
- package/dist/components/DataTable/ActiveFilterInstance.d.ts.map +1 -1
- package/dist/components/DataTable/ActiveFilterInstance.js +5 -5
- package/dist/components/DataTable/ActiveFilterInstance.js.map +1 -1
- package/dist/components/DataTable/ActiveFilters.d.ts +3 -3
- package/dist/components/DataTable/ActiveFilters.d.ts.map +1 -1
- package/dist/components/DataTable/ActiveFilters.js +11 -6
- package/dist/components/DataTable/ActiveFilters.js.map +1 -1
- package/dist/components/DataTable/DataTable.d.ts +49 -28
- package/dist/components/DataTable/DataTable.d.ts.map +1 -1
- package/dist/components/DataTable/DataTable.js +80 -41
- package/dist/components/DataTable/DataTable.js.map +1 -1
- package/dist/components/DataTable/DataTableColumn.d.ts +29 -5
- package/dist/components/DataTable/DataTableColumn.d.ts.map +1 -1
- package/dist/components/DataTable/DataTableColumnTypes.d.ts +2 -2
- package/dist/components/DataTable/DataTableColumnTypes.d.ts.map +1 -1
- package/dist/components/DataTable/DataTableColumnTypes.js +15 -12
- package/dist/components/DataTable/DataTableColumnTypes.js.map +1 -1
- package/dist/components/DataTable/DeleteSavedViewAlertDialog.d.ts +1 -1
- package/dist/components/DataTable/DeleteSavedViewAlertDialog.d.ts.map +1 -1
- package/dist/components/DataTable/DeleteSavedViewAlertDialog.js.map +1 -1
- package/dist/components/DataTable/FilterTypes.d.ts +2 -0
- package/dist/components/DataTable/FilterTypes.d.ts.map +1 -1
- package/dist/components/DataTable/ManageViewsButton.d.ts +9 -0
- package/dist/components/DataTable/ManageViewsButton.d.ts.map +1 -0
- package/dist/components/DataTable/{ManageSavedViewsButton.js → ManageViewsButton.js} +5 -5
- package/dist/components/DataTable/ManageViewsButton.js.map +1 -0
- package/dist/components/DataTable/{ManageSavedViewsModal.d.ts → ManageViewsModal.d.ts} +7 -7
- package/dist/components/DataTable/ManageViewsModal.d.ts.map +1 -0
- package/dist/components/DataTable/{ManageSavedViewsModal.js → ManageViewsModal.js} +10 -10
- package/dist/components/DataTable/ManageViewsModal.js.map +1 -0
- package/dist/components/DataTable/ManageViewsModal.module.css.js +4 -0
- package/dist/components/DataTable/ManageViewsModal.module.css.js.map +1 -0
- package/dist/components/DataTable/NewSavedViewButton.js +1 -1
- package/dist/components/DataTable/NewSavedViewButton.js.map +1 -1
- package/dist/components/DataTable/OperatorSelect.js +4 -1
- package/dist/components/DataTable/OperatorSelect.js.map +1 -1
- package/dist/components/DataTable/RowActions.d.ts +11 -0
- package/dist/components/DataTable/RowActions.d.ts.map +1 -1
- package/dist/components/DataTable/RowActions.js +7 -4
- package/dist/components/DataTable/RowActions.js.map +1 -1
- package/dist/components/DataTable/TableActions.d.ts +5 -0
- package/dist/components/DataTable/TableActions.d.ts.map +1 -1
- package/dist/components/DataTable/TableActions.js +2 -1
- package/dist/components/DataTable/TableActions.js.map +1 -1
- package/dist/components/DataTable/ViewMenu.d.ts +18 -0
- package/dist/components/DataTable/ViewMenu.d.ts.map +1 -0
- package/dist/components/DataTable/{SavedViewMenu.js → ViewMenu.js} +5 -5
- package/dist/components/DataTable/ViewMenu.js.map +1 -0
- package/dist/components/DataTable/{SavedViewsBar.d.ts → ViewsBar.d.ts} +11 -11
- package/dist/components/DataTable/ViewsBar.d.ts.map +1 -0
- package/dist/components/DataTable/{SavedViewsBar.js → ViewsBar.js} +34 -28
- package/dist/components/DataTable/ViewsBar.js.map +1 -0
- package/dist/components/DataTable/dateFilter.d.ts +19 -3
- package/dist/components/DataTable/dateFilter.d.ts.map +1 -1
- package/dist/components/DataTable/dateFilter.js +36 -11
- package/dist/components/DataTable/dateFilter.js.map +1 -1
- package/dist/components/DataTable/dayFilter.d.ts.map +1 -1
- package/dist/components/DataTable/dayFilter.js +25 -22
- package/dist/components/DataTable/dayFilter.js.map +1 -1
- package/dist/components/DataTable/index.d.ts +3 -3
- package/dist/components/DataTable/index.d.ts.map +1 -1
- package/dist/components/DataTable/scopedFilter.d.ts +1 -1
- package/dist/components/DataTable/scopedFilter.d.ts.map +1 -1
- package/dist/components/DataTable/scopedFilter.js +56 -35
- package/dist/components/DataTable/scopedFilter.js.map +1 -1
- package/dist/components/DataTable/useActiveView.d.ts +7 -0
- package/dist/components/DataTable/useActiveView.d.ts.map +1 -0
- package/dist/components/DataTable/{useActiveSavedView.js → useActiveView.js} +5 -5
- package/dist/components/DataTable/useActiveView.js.map +1 -0
- package/dist/components/DataTable/useColumnVisibility.d.ts +12 -8
- package/dist/components/DataTable/useColumnVisibility.d.ts.map +1 -1
- package/dist/components/DataTable/useColumnVisibility.js +28 -16
- package/dist/components/DataTable/useColumnVisibility.js.map +1 -1
- package/dist/components/DataTable/useSaveStatus.d.ts +6 -6
- package/dist/components/DataTable/useSaveStatus.d.ts.map +1 -1
- package/dist/components/DataTable/useSaveStatus.js +7 -7
- package/dist/components/DataTable/useSaveStatus.js.map +1 -1
- package/dist/components/DataTable/useSavedViewNameModal.d.ts +2 -2
- package/dist/components/DataTable/useSavedViewNameModal.d.ts.map +1 -1
- package/dist/components/DataTable/useSavedViewNameModal.js +2 -2
- package/dist/components/DataTable/useSavedViewNameModal.js.map +1 -1
- package/dist/components/DataTable/useSavedViewsClient.d.ts +3 -3
- package/dist/components/DataTable/useSavedViewsClient.d.ts.map +1 -1
- package/dist/components/DataTable/useSavedViewsClient.js +1 -1
- package/dist/components/DataTable/useSavedViewsClient.js.map +1 -1
- package/dist/components/DataTable/useSavedViewsState.d.ts +7 -7
- package/dist/components/DataTable/useSavedViewsState.d.ts.map +1 -1
- package/dist/components/DataTable/useSavedViewsState.js +1 -1
- package/dist/components/DataTable/useSavedViewsState.js.map +1 -1
- package/dist/components/DataTable/useSearchFilter.d.ts.map +1 -1
- package/dist/components/DataTable/useSearchFilter.js +2 -1
- package/dist/components/DataTable/useSearchFilter.js.map +1 -1
- package/dist/components/DataTable/useUpdateSavedViewName.d.ts +1 -1
- package/dist/components/DataTable/useUpdateSavedViewName.d.ts.map +1 -1
- package/dist/components/DataTable/useUpdateSavedViewName.js.map +1 -1
- package/dist/components/DataTable/{useVisibleSavedViews.d.ts → useVisibleViews.d.ts} +2 -2
- package/dist/components/DataTable/useVisibleViews.d.ts.map +1 -0
- package/dist/components/DataTable/{useVisibleSavedViews.js → useVisibleViews.js} +6 -6
- package/dist/components/DataTable/useVisibleViews.js.map +1 -0
- package/dist/components/DataTable/views.d.ts +56 -0
- package/dist/components/DataTable/views.d.ts.map +1 -0
- package/dist/components/DataTable/{savedViews.js → views.js} +12 -11
- package/dist/components/DataTable/views.js.map +1 -0
- package/dist/components/button/ActionsDropdownIconButton.d.ts +2 -2
- package/dist/components/button/ActionsDropdownIconButton.d.ts.map +1 -1
- package/dist/components/button/ActionsDropdownIconButton.js.map +1 -1
- package/dist/components/button/IconButton.d.ts +2 -2
- package/dist/components/button/IconButton.d.ts.map +1 -1
- package/dist/components/button/IconButton.js.map +1 -1
- package/dist/components/checkbox-group/CheckboxGroup.d.ts +3 -1
- package/dist/components/checkbox-group/CheckboxGroup.d.ts.map +1 -1
- package/dist/components/checkbox-group/CheckboxGroup.js +2 -2
- package/dist/components/checkbox-group/CheckboxGroup.js.map +1 -1
- package/dist/components/date-picker/DatePicker.d.ts +7 -2
- package/dist/components/date-picker/DatePicker.d.ts.map +1 -1
- package/dist/components/date-picker/DatePicker.js +69 -14
- package/dist/components/date-picker/DatePicker.js.map +1 -1
- package/dist/components/dropdown/Dropdown.d.ts.map +1 -1
- package/dist/components/dropdown/Dropdown.js +10 -2
- package/dist/components/dropdown/Dropdown.js.map +1 -1
- package/dist/components/link/BaseLink.js +3 -3
- package/dist/components/link/BaseLink.js.map +1 -1
- package/dist/components/link/IconLink.js +4 -4
- package/dist/components/link/IconLink.js.map +1 -1
- package/dist/components/link/Link.js +2 -2
- package/dist/components/link/Link.js.map +1 -1
- package/dist/components/page-header/defineElements.js +1 -1
- package/dist/components/radio-group/RadioGroup.d.ts +7 -1
- package/dist/components/radio-group/RadioGroup.d.ts.map +1 -1
- package/dist/components/radio-group/RadioGroup.js +2 -2
- package/dist/components/radio-group/RadioGroup.js.map +1 -1
- package/dist/components/sidenav/defineElements.js +1 -1
- package/dist/index.css +107 -27
- package/dist/index.css.map +1 -1
- package/dist/index.d.ts +1 -0
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +1 -0
- package/dist/index.js.map +1 -1
- package/dist/packages/tapestry-wc/dist/components/{p-CBFtMIxJ.js → p-Bw5XJ46l.js} +2 -2
- package/dist/packages/tapestry-wc/dist/components/{p-CBFtMIxJ.js.map → p-Bw5XJ46l.js.map} +1 -1
- package/dist/packages/tapestry-wc/dist/components/{p-BbuNAv9q.js → p-C5B21uv6.js} +3 -3
- package/dist/packages/tapestry-wc/dist/components/{p-BbuNAv9q.js.map → p-C5B21uv6.js.map} +1 -1
- package/dist/packages/tapestry-wc/dist/components/{p-DNHgMtxw.js → p-D4oSihjy.js} +2 -2
- package/dist/packages/tapestry-wc/dist/components/{p-DNHgMtxw.js.map → p-D4oSihjy.js.map} +1 -1
- package/dist/packages/tapestry-wc/dist/components/{p-A1JK45WV.js → p-DZA99jMW.js} +3 -3
- package/dist/packages/tapestry-wc/dist/components/{p-A1JK45WV.js.map → p-DZA99jMW.js.map} +1 -1
- package/dist/packages/tapestry-wc/dist/components/{p-CY_DC4d_.js → p-Dt250a7E.js} +3 -3
- package/dist/packages/tapestry-wc/dist/components/{p-CY_DC4d_.js.map → p-Dt250a7E.js.map} +1 -1
- package/dist/packages/tapestry-wc/dist/components/tds-page-header-nav.js +2 -2
- package/dist/packages/tapestry-wc/dist/components/tds-page-header-nav.js.map +1 -1
- package/dist/packages/tapestry-wc/dist/components/tds-page-header.js +5 -5
- package/dist/packages/tapestry-wc/dist/components/tds-page-header.js.map +1 -1
- package/dist/packages/tapestry-wc/dist/components/tds-sidenav-item.js +3 -3
- package/dist/packages/tapestry-wc/dist/components/tds-sidenav-item.js.map +1 -1
- package/dist/packages/tapestry-wc/dist/components/tds-sidenav-responsive-header.js +2 -2
- package/dist/packages/tapestry-wc/dist/components/tds-sidenav-responsive-header.js.map +1 -1
- package/dist/packages/tapestry-wc/dist/components/tds-sidenav-section.js +3 -3
- package/dist/packages/tapestry-wc/dist/components/tds-sidenav-section.js.map +1 -1
- package/dist/packages/tapestry-wc/dist/components/tds-sidenav.js +5 -5
- package/dist/packages/tapestry-wc/dist/components/tds-sidenav.js.map +1 -1
- package/dist/reactRender.css +864 -765
- package/dist/reactRender.css.map +1 -1
- package/dist/reactRender.js +1 -1
- package/dist/reactRenderLegacy.css +864 -765
- package/dist/reactRenderLegacy.css.map +1 -1
- package/dist/reactRenderLegacy.js +1 -1
- package/dist/tapestryMount.css +864 -765
- package/dist/tapestryMount.css.map +1 -1
- package/dist/tapestryMount.js +1 -1
- package/dist/tapestryMountLegacy.css +864 -765
- package/dist/tapestryMountLegacy.css.map +1 -1
- package/dist/tapestryMountLegacy.js +1 -1
- package/dist/unstable.css +381 -282
- package/dist/unstable.css.map +1 -1
- package/dist/unstable.js +1 -0
- package/dist/unstable.js.map +1 -1
- package/dist/utilities/dataHooks.d.ts +8 -0
- package/dist/utilities/dataHooks.d.ts.map +1 -0
- package/dist/utilities/dataHooks.js +7 -0
- package/dist/utilities/dataHooks.js.map +1 -0
- package/dist/utilities/locale.d.ts +25 -0
- package/dist/utilities/locale.d.ts.map +1 -0
- package/dist/utilities/locale.js +48 -0
- package/dist/utilities/locale.js.map +1 -0
- package/docs/accessibility/accessibility.md +62 -0
- package/docs/components/button-group.md +44 -0
- package/docs/components/button.md +78 -0
- package/docs/components/checkbox-group.md +51 -0
- package/docs/components/checkbox.md +55 -0
- package/docs/components/combo-box.md +68 -0
- package/docs/components/currency-input.md +50 -0
- package/docs/components/date-picker.md +67 -0
- package/docs/components/dropdown.md +74 -0
- package/docs/components/field.md +44 -0
- package/docs/components/flex.md +66 -0
- package/docs/components/input.md +62 -0
- package/docs/components/link.md +46 -0
- package/docs/components/modal.md +59 -0
- package/docs/components/number-stepper.md +50 -0
- package/docs/components/page-header.md +48 -0
- package/docs/components/popover.md +45 -0
- package/docs/components/radio-group.md +47 -0
- package/docs/components/radio.md +62 -0
- package/docs/components/search-input.md +46 -0
- package/docs/components/segmented-control.md +60 -0
- package/docs/components/select.md +62 -0
- package/docs/components/sidenav.md +36 -0
- package/docs/components/text-area.md +65 -0
- package/docs/components/time-field.md +62 -0
- package/docs/components/toggle-switch.md +56 -0
- package/docs/content/addressing-users-in-products.md +153 -0
- package/docs/content/browser-tabs.md +59 -0
- package/docs/content/capitalization.md +69 -0
- package/docs/content/date-formatting.md +145 -0
- package/docs/content/displaying-names.md +139 -0
- package/docs/content/editing-and-saving.md +95 -0
- package/docs/content/file-size-formatting.md +44 -0
- package/docs/content/household-ordering.md +127 -0
- package/docs/content/micro-copy.md +135 -0
- package/docs/content/prompts.md +271 -0
- package/docs/content/punctuation.md +71 -0
- package/docs/content/sharing-nomenclature.md +67 -0
- package/docs/content/timezones.md +108 -0
- package/docs/content/tooltip-usage.md +49 -0
- package/docs/content/use-of-emoji.md +63 -0
- package/docs/content/voice-and-tone.md +251 -0
- package/docs/design/design-tokens.md +70 -0
- package/docs/design/iconography.md +60 -0
- package/docs/design/layout.md +237 -0
- package/docs/design/mobile-design-principles.md +109 -0
- package/docs/design/pca-design-language.md +78 -0
- package/docs/design/typography.md +94 -0
- package/docs/get-started/design-system-philosophy.md +33 -0
- package/docs/llms.txt +119 -0
- package/package.json +7 -5
- package/react-types/index.d.ts +5 -0
- package/dist/components/DataTable/ManageSavedViewsButton.d.ts +0 -9
- package/dist/components/DataTable/ManageSavedViewsButton.d.ts.map +0 -1
- package/dist/components/DataTable/ManageSavedViewsButton.js.map +0 -1
- package/dist/components/DataTable/ManageSavedViewsModal.d.ts.map +0 -1
- package/dist/components/DataTable/ManageSavedViewsModal.js.map +0 -1
- package/dist/components/DataTable/ManageSavedViewsModal.module.css.js +0 -4
- package/dist/components/DataTable/ManageSavedViewsModal.module.css.js.map +0 -1
- package/dist/components/DataTable/SavedViewMenu.d.ts +0 -18
- package/dist/components/DataTable/SavedViewMenu.d.ts.map +0 -1
- package/dist/components/DataTable/SavedViewMenu.js.map +0 -1
- package/dist/components/DataTable/SavedViewsBar.d.ts.map +0 -1
- package/dist/components/DataTable/SavedViewsBar.js.map +0 -1
- package/dist/components/DataTable/savedViews.d.ts +0 -45
- package/dist/components/DataTable/savedViews.d.ts.map +0 -1
- package/dist/components/DataTable/savedViews.js.map +0 -1
- package/dist/components/DataTable/useActiveSavedView.d.ts +0 -7
- package/dist/components/DataTable/useActiveSavedView.d.ts.map +0 -1
- package/dist/components/DataTable/useActiveSavedView.js.map +0 -1
- package/dist/components/DataTable/useVisibleSavedViews.d.ts.map +0 -1
- package/dist/components/DataTable/useVisibleSavedViews.js.map +0 -1
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Tooltip usage
|
|
3
|
+
description: When to use tooltips, how to write tooltip copy, and how tooltips time, behave, and position across Planning Center products.
|
|
4
|
+
order: 80
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Tooltip usage
|
|
8
|
+
|
|
9
|
+
## Rules
|
|
10
|
+
|
|
11
|
+
- **Do** use tooltips for icon-only buttons or controls when the UI can’t support a visible label.
|
|
12
|
+
- **Do** use tooltips to display names on avatars.
|
|
13
|
+
- **Do** keep tooltip text to 1–5 words, with no punctuation, and cap width at 240px.
|
|
14
|
+
- **Don’t** put interactive content like buttons or links inside tooltips.
|
|
15
|
+
- **Don’t** put instructional information users need to complete a task in a tooltip.
|
|
16
|
+
- **Don’t** repeat the label of the element the tooltip wraps.
|
|
17
|
+
- **Don’t** use tooltips in mobile contexts.
|
|
18
|
+
|
|
19
|
+
## Overview
|
|
20
|
+
|
|
21
|
+
Tooltips show a short hover or focus revealed hint next to a trigger element, most often an icon-only button that needs context beyond what its icon conveys. This page covers how and when to use them across Planning Center products.
|
|
22
|
+
|
|
23
|
+
## When to use a tooltip
|
|
24
|
+
|
|
25
|
+
::: tip Do
|
|
26
|
+
|
|
27
|
+
- Use tooltips for icon-only buttons or controls when the UI can’t support a visible label.
|
|
28
|
+
- Use tooltips to display names on avatars.
|
|
29
|
+
|
|
30
|
+
:::
|
|
31
|
+
|
|
32
|
+
::: danger Don’t
|
|
33
|
+
|
|
34
|
+
- Don’t use interactive content like buttons or links inside of tooltips. Although this shows up in some areas of Planning Center today; treat it as a pending cleanup item, not something to replicate.
|
|
35
|
+
- Don’t use tooltips for helper-type, instructional information. Tooltips should not contain information users need to complete a task.
|
|
36
|
+
- Don’t use tooltips for redundant text that repeats the label of the element it wraps.
|
|
37
|
+
- Don’t use tooltips in mobile contexts.
|
|
38
|
+
|
|
39
|
+
:::
|
|
40
|
+
|
|
41
|
+
## Writing tooltip copy
|
|
42
|
+
|
|
43
|
+
Keep tooltip text to 1–5 words; shorter is better. Skip punctuation entirely. Cap the tooltip’s width at 240px.
|
|
44
|
+
|
|
45
|
+
## Timing, interaction, and placement
|
|
46
|
+
|
|
47
|
+
Tooltips open when the cursor rests on the trigger for 1.5 seconds, or right away when the trigger gets keyboard focus. They close up to 0.5 seconds after the cursor leaves. An arrow points back at the trigger. Icon Button and Icon Link place the tooltip below the trigger, centered, by default; change it with `tooltipPlacement`.
|
|
48
|
+
|
|
49
|
+
Tooltips don’t open on disabled controls. Avoid disabled controls when you can. When you can’t, explain why the action is unavailable in visible text nearby.
|
|
@@ -0,0 +1,63 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Use of emoji
|
|
3
|
+
description: How and how much to use emoji in customer-facing communications like email subject lines and sign-offs.
|
|
4
|
+
order: 60
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Use of emoji
|
|
8
|
+
|
|
9
|
+
## Rules
|
|
10
|
+
|
|
11
|
+
- **Do** limit email subject lines to 1-2 emoji.
|
|
12
|
+
- **Do** limit email sign-offs to 1 emoji.
|
|
13
|
+
- **Do** use emoji to accentuate a message and add warmth.
|
|
14
|
+
- **Do** check that the message still makes sense with the emoji removed.
|
|
15
|
+
- **Don’t** replace words with emoji.
|
|
16
|
+
- **Don’t** overuse emoji throughout email body content.
|
|
17
|
+
- **Don’t** use emoji that don’t reinforce the message’s meaning.
|
|
18
|
+
|
|
19
|
+
## Overview
|
|
20
|
+
|
|
21
|
+
Emoji can add warmth and personality to customer communication when used thoughtfully. Planning Center limits emoji use in customer-facing communications to maintain professionalism while allowing strategic moments of personality in subject lines and sign-offs.
|
|
22
|
+
|
|
23
|
+
## Principles
|
|
24
|
+
|
|
25
|
+
- Use emoji sparingly in customer communications to prevent overuse
|
|
26
|
+
- Limit to 1-2 emoji in email subject lines
|
|
27
|
+
- Limit to 1 emoji in email sign-offs
|
|
28
|
+
- Emoji should accentuate messages, not replace words
|
|
29
|
+
|
|
30
|
+
## Usage
|
|
31
|
+
|
|
32
|
+
### Guidelines
|
|
33
|
+
|
|
34
|
+
#### Email subject lines
|
|
35
|
+
|
|
36
|
+
Emoji are acceptable in email subject lines to draw attention and add personality. Limit to 1 or 2 emoji maximum to maintain professionalism and scannability. Use emoji that reinforce the subject matter without being essential to understanding the message.
|
|
37
|
+
|
|
38
|
+
#### Email body sign-offs
|
|
39
|
+
|
|
40
|
+
Emoji can be used in sign-offs to add warmth to closing messages. Limit to 1 emoji. This creates a friendly ending without overwhelming the message content.
|
|
41
|
+
|
|
42
|
+
#### Accentuation, not replacement
|
|
43
|
+
|
|
44
|
+
Emoji should enhance the message, not replace words. Test by removing the emoji—if the sentence no longer makes sense or loses critical meaning, the emoji is being misused. Emoji work best as visual emphasis or emotional tone, not as substitutes for clear language.
|
|
45
|
+
|
|
46
|
+
::: tip Do
|
|
47
|
+
|
|
48
|
+
- Use 1-2 emoji in email subject lines for emphasis: “📣 Calling all volunteers”
|
|
49
|
+
- Use 1 emoji in email sign-offs: “💙 Love, The Planning Center Team”
|
|
50
|
+
- Use emoji to accentuate the message and add warmth
|
|
51
|
+
- Ensure messages remain clear and complete if emoji are removed
|
|
52
|
+
|
|
53
|
+
:::
|
|
54
|
+
|
|
55
|
+
::: danger Don’t
|
|
56
|
+
|
|
57
|
+
- Use more than 1-2 emoji in subject lines
|
|
58
|
+
- Use more than 1 emoji in sign-offs
|
|
59
|
+
- Replace words with emoji—messages should make sense without them
|
|
60
|
+
- Overuse emoji throughout email body content
|
|
61
|
+
- Use emoji that don’t reinforce the message meaning
|
|
62
|
+
|
|
63
|
+
:::
|
|
@@ -0,0 +1,251 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Voice & tone
|
|
3
|
+
description: A guide for applying Planning Center’s voice and tone to interface copy.
|
|
4
|
+
order: 10
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Voice & tone
|
|
8
|
+
|
|
9
|
+
## Rules
|
|
10
|
+
|
|
11
|
+
- **Do** put clarity first and friendliness second; never trade clarity for personality.
|
|
12
|
+
- **Do** match tone to the moment: calm for routine tasks, warm for first-time experiences, honest and calm for errors.
|
|
13
|
+
- **Do** explain what happened and what to do next in error messages.
|
|
14
|
+
- **Do** use contractions, active voice, and address the user directly.
|
|
15
|
+
- **Don’t** blame the user or open errors with “Oops!”, “Uh oh!”, or “Whoops!”.
|
|
16
|
+
- **Don’t** add wit or personality to destructive confirmations, errors, form labels, or data-dense views.
|
|
17
|
+
- **Don’t** use filler words like “just,” “simply,” “please,” or “in order to.”
|
|
18
|
+
- **Don’t** describe the same action with different words in different places.
|
|
19
|
+
|
|
20
|
+
## Overview
|
|
21
|
+
|
|
22
|
+
Product UI copy is different from other forms of writing. It’s read quickly, often mid-task, and sometimes under stress. People aren’t settling in to read it; they’re scanning for the next thing to do. That means our interface copy needs to feel like Planning Center while staying out of the way.
|
|
23
|
+
|
|
24
|
+
This guide is about how to make that happen. It covers the voice and tone decisions that come up when you’re writing buttons, errors, empty states, tooltips, and everything else that lives inside our products. The goal is copy that’s clear enough to act on, human enough to trust, and consistent enough to disappear into the experience.
|
|
25
|
+
|
|
26
|
+
## The short version
|
|
27
|
+
|
|
28
|
+
Write like a helpful coworker, not a machine. Be clear first, friendly second. Never sacrifice clarity for personality.
|
|
29
|
+
|
|
30
|
+
## How our voice shows up in product
|
|
31
|
+
|
|
32
|
+
Our brand personality is encouraging, knowledgeable, kind, friendly, fun, witty, humble, and delightful. In product UI, those traits are present but measured. The interface isn’t a blog post or a support email. It’s more like a well-organized workspace where everything is where you expect it, the labels make sense, and someone thoughtful set it all up.
|
|
33
|
+
|
|
34
|
+
**Encouraging** means we celebrate progress and frame actions positively. We say “You’re all set!” not “Process complete.” We acknowledge effort when someone finishes a multi-step task.
|
|
35
|
+
|
|
36
|
+
**Knowledgeable** means our copy anticipates questions. A well-written label or helper text prevents a support ticket. We don’t just tell people what to do; we help them understand why.
|
|
37
|
+
|
|
38
|
+
**Kind** means we never blame the user. When something goes wrong, we take responsibility and offer a path forward. “That person couldn’t be found” is better than “Invalid entry.”
|
|
39
|
+
|
|
40
|
+
**Friendly** means we use contractions, plain language, and a conversational register. But friendly in product UI is more restrained than friendly in a blog post. A button doesn’t need to be chatty.
|
|
41
|
+
|
|
42
|
+
**Humble** means we don’t draw attention to ourselves. The product should feel like a natural extension of the church’s work, not a piece of software demanding praise.
|
|
43
|
+
|
|
44
|
+
## Where personality lives (and where it doesn’t)
|
|
45
|
+
|
|
46
|
+
Personality earns its place in the interface. Not every screen needs warmth, and not every moment calls for restraint. Here’s how to calibrate.
|
|
47
|
+
|
|
48
|
+
### More personality is welcome in:
|
|
49
|
+
|
|
50
|
+
- Empty states (“No events yet. Create one to get started!”)
|
|
51
|
+
- Success confirmations (“Nice! Your changes are saved.”)
|
|
52
|
+
- Onboarding and first-run experiences
|
|
53
|
+
- Feature announcements and what’s-new moments
|
|
54
|
+
- Non-critical tooltips and helper text
|
|
55
|
+
|
|
56
|
+
### Keep it neutral and direct in:
|
|
57
|
+
|
|
58
|
+
- Error messages and warnings (clarity wins over charm)
|
|
59
|
+
- Destructive action confirmations (this is not the time for wit)
|
|
60
|
+
- Form labels and field placeholders
|
|
61
|
+
- Navigation and wayfinding
|
|
62
|
+
- Data-dense interfaces like tables, reports, and dashboards
|
|
63
|
+
|
|
64
|
+
## Tone shifts by context
|
|
65
|
+
|
|
66
|
+
Our voice stays the same, but our tone adjusts depending on what the user is experiencing. Think of it like adjusting your energy level to match the room.
|
|
67
|
+
|
|
68
|
+
### Routine tasks
|
|
69
|
+
|
|
70
|
+
**Tone: Calm, clear, minimal.** The user is in flow. Stay out of the way. Labels should be scannable. Actions should be obvious. Don’t add unnecessary warmth to a task someone does 50 times a week.
|
|
71
|
+
|
|
72
|
+
::: info
|
|
73
|
+
**Example:** “Add person” not “Go ahead and add a new person!”
|
|
74
|
+
:::
|
|
75
|
+
|
|
76
|
+
### First-time experiences
|
|
77
|
+
|
|
78
|
+
**Tone: Warm, encouraging, slightly more expressive.** The user is orienting themselves. A little extra friendliness helps them feel welcome and reduces anxiety about making mistakes.
|
|
79
|
+
|
|
80
|
+
::: info
|
|
81
|
+
**Example:** “Welcome to Groups! Start by creating your first group, or explore the ones already here.”
|
|
82
|
+
:::
|
|
83
|
+
|
|
84
|
+
### Errors and problems
|
|
85
|
+
|
|
86
|
+
**Tone: Honest, helpful, calm.** The user is frustrated or confused. Don’t be cute. Don’t blame them. State what happened, explain what it means, and offer a next step.
|
|
87
|
+
|
|
88
|
+
::: info
|
|
89
|
+
**Example:** “That email address is already in use. Try a different one, or log in with that address.” _Not:_ “Oops! Something went wrong with the email you entered.”
|
|
90
|
+
:::
|
|
91
|
+
|
|
92
|
+
### Destructive or irreversible actions
|
|
93
|
+
|
|
94
|
+
**Tone: Clear, direct, specific.** The user needs to understand exactly what’s about to happen. Use the object’s name. State the consequences. Make the buttons unambiguous. See **Prompts** for the full structural pattern.
|
|
95
|
+
|
|
96
|
+
::: info
|
|
97
|
+
**Example:** **Headline:** “Delete Cathy?” **Body:** “Deleting Cathy will remove her from People and all other Planning Center apps. Any related activity will also be deleted. You cannot un-delete Cathy.” **Buttons:** \[Cancel\] \[Yes, delete Cathy\]
|
|
98
|
+
:::
|
|
99
|
+
|
|
100
|
+
### Celebrations and success
|
|
101
|
+
|
|
102
|
+
**Tone: Warm, brief, genuine.** A well-placed moment of encouragement makes the product feel alive. But keep it proportional to the action. Don’t throw confetti for saving a form.
|
|
103
|
+
|
|
104
|
+
| Action weight | Example |
|
|
105
|
+
| --------------------------------- | -------------------------------------------- |
|
|
106
|
+
| Minor (saved a field) | “Saved.” or a brief checkmark animation |
|
|
107
|
+
| Medium (completed a form) | “Changes saved.” |
|
|
108
|
+
| Significant (finished onboarding) | “You’re all set! Your group is ready to go.” |
|
|
109
|
+
|
|
110
|
+
## Writing principles for product UI
|
|
111
|
+
|
|
112
|
+
These principles are ordered by priority. When they conflict, the one listed first wins.
|
|
113
|
+
|
|
114
|
+
### 1. Be clear
|
|
115
|
+
|
|
116
|
+
Clarity is the foundation. Every piece of UI copy should answer “What do I do here?” or “What just happened?” If the user has to pause and interpret, the copy needs work.
|
|
117
|
+
|
|
118
|
+
- Use familiar words. “Remove” not “disassociate.” “Send” not “dispatch.”
|
|
119
|
+
- Front-load the important information. In a list of actions, the verb comes first.
|
|
120
|
+
- Avoid double negatives. “Show inactive members” not “Don’t hide inactive members.”
|
|
121
|
+
|
|
122
|
+
### 2. Be concise
|
|
123
|
+
|
|
124
|
+
Interface copy competes for attention with everything else on screen. Every word needs to earn its place.
|
|
125
|
+
|
|
126
|
+
- Cut filler words: “just,” “simply,” “please,” “in order to.”
|
|
127
|
+
- Prefer short sentences. If a tooltip needs two sentences, question whether the feature is clear enough on its own.
|
|
128
|
+
- Use numerals for numbers in UI (even under 10) when space is tight. In longer body copy, follow the style guide and spell out numbers under 10.
|
|
129
|
+
|
|
130
|
+
### 3. Be consistent
|
|
131
|
+
|
|
132
|
+
Consistency builds trust. When the same action is described differently in two places, users lose confidence.
|
|
133
|
+
|
|
134
|
+
- Use the same word for the same action everywhere. If it’s “Remove” in one place, don’t call it “Delete” in another unless the underlying action is genuinely different.
|
|
135
|
+
- Follow Tapestry’s content foundations for specific formatting decisions. Those patterns exist to remove ambiguity.
|
|
136
|
+
- Refer to products, features, and UI elements using their established names. See **Capitalization** and **Micro copy** for specifics.
|
|
137
|
+
|
|
138
|
+
### 4. Be human
|
|
139
|
+
|
|
140
|
+
After you’ve nailed clarity, conciseness, and consistency, add the human touch. This is where Planning Center’s personality comes through.
|
|
141
|
+
|
|
142
|
+
- Use contractions. “You’ll” not “You will.” “Can’t” not “Cannot.”
|
|
143
|
+
- Write in active voice. “You created 3 events” not “3 events were created.”
|
|
144
|
+
- Address the user directly. See **Addressing users in products** for the full guidelines on “you,” “your,” and when to use (or avoid) “we.”
|
|
145
|
+
|
|
146
|
+
## UI copy patterns
|
|
147
|
+
|
|
148
|
+
The Tapestry content foundations cover many specific copy patterns in detail. This section focuses on patterns that aren’t fully covered elsewhere, or where the voice and tone application is the key consideration.
|
|
149
|
+
|
|
150
|
+
### Buttons and actions
|
|
151
|
+
|
|
152
|
+
Buttons should start with a verb and clearly describe what will happen when clicked. See **Prompts** for full button guidelines in confirmation dialogs.
|
|
153
|
+
|
|
154
|
+
### Placeholder text
|
|
155
|
+
|
|
156
|
+
Placeholders should hint at the expected format or give a brief example. Don’t restate the label.
|
|
157
|
+
|
|
158
|
+
| Do | Don’t |
|
|
159
|
+
| -------------------------------------------------------- | -------------------------------------------------------- |
|
|
160
|
+
| Label: “Email address” / Placeholder: “name@example.com” | Label: “Email” / Placeholder: “Enter your email address” |
|
|
161
|
+
| Label: “Search” / Placeholder: “Search by name or email” | Label: “Search” / Placeholder: “Search” |
|
|
162
|
+
|
|
163
|
+
### Empty states
|
|
164
|
+
|
|
165
|
+
Empty states are one of the best places for personality. They’re an opportunity to orient the user and motivate action.
|
|
166
|
+
|
|
167
|
+
**Structure:**
|
|
168
|
+
|
|
169
|
+
1. A brief, friendly headline that acknowledges the empty state
|
|
170
|
+
2. A one-sentence explanation of what will appear here
|
|
171
|
+
3. A clear call to action
|
|
172
|
+
|
|
173
|
+
::: info
|
|
174
|
+
**Example:** **No events yet** Events you create will show up here. Get started by adding your first one. \[Create event\]
|
|
175
|
+
:::
|
|
176
|
+
|
|
177
|
+
Avoid empty states that just say “No results” or “Nothing to see here.” Those are dead ends.
|
|
178
|
+
|
|
179
|
+
### Error messages
|
|
180
|
+
|
|
181
|
+
Errors should explain what happened and what the user can do about it. Never blame the user. Never use a generic message when a specific one is possible.
|
|
182
|
+
|
|
183
|
+
**Structure:**
|
|
184
|
+
|
|
185
|
+
1. What happened (in plain language)
|
|
186
|
+
2. Why it happened (if it helps and isn’t overly technical)
|
|
187
|
+
3. What to do next
|
|
188
|
+
|
|
189
|
+
| Do | Don’t |
|
|
190
|
+
| -------------------------------------------------------------------------- | ----------------------- |
|
|
191
|
+
| That email address is already in use. Try a different one. | Error: Duplicate entry |
|
|
192
|
+
| This person couldn’t be found. Check the spelling or try a different name. | Invalid input |
|
|
193
|
+
| Your session has expired. Log in again to continue. | Error 401: Unauthorized |
|
|
194
|
+
|
|
195
|
+
Avoid “Oops!”, “Uh oh!”, “Whoops!” and similar cutesy error intros. They feel dismissive when someone is trying to get something done.
|
|
196
|
+
|
|
197
|
+
### Tooltips and helper text
|
|
198
|
+
|
|
199
|
+
Tooltips answer “What is this?” Helper text answers “What should I do here?”
|
|
200
|
+
|
|
201
|
+
- Keep tooltips under 150 characters
|
|
202
|
+
- If a tooltip needs to be longer than one sentence, consider whether the UI itself needs to be clearer
|
|
203
|
+
- Follow **Punctuation** guidelines for terminal punctuation in fragments vs. full sentences
|
|
204
|
+
|
|
205
|
+
### Loading and progress states
|
|
206
|
+
|
|
207
|
+
Be honest about what’s happening. If something takes a while, say so. Vague messages like “Loading...” or “Please wait.” don’t help the user understand what’s going on or set expectations for how long it will take.
|
|
208
|
+
|
|
209
|
+
| Do | Don’t |
|
|
210
|
+
| ----------------------------------------------------- | ------------- |
|
|
211
|
+
| Generating your list. This can take up to 10 minutes. | Loading... |
|
|
212
|
+
| Importing 200 people... | Please wait. |
|
|
213
|
+
| Sending emails to 150 people... | Processing... |
|
|
214
|
+
|
|
215
|
+
## The “this, not that” for product UI
|
|
216
|
+
|
|
217
|
+
Adapted from our brand guide, here’s how our voice principles translate to interface copy specifically.
|
|
218
|
+
|
|
219
|
+
| We are... | Which means in UI... | Not... |
|
|
220
|
+
| ----------- | -------------------------------------------------- | ---------------------------------------------------- |
|
|
221
|
+
| Encouraging | We frame actions positively and celebrate progress | Authoritative (“You must configure settings”) |
|
|
222
|
+
| Empathetic | We acknowledge difficulty without being dramatic | Presumptuous (“We know this is confusing”) |
|
|
223
|
+
| Human | We use contractions and conversational language | Robotic (“The operation has been completed”) |
|
|
224
|
+
| Casual | We’re relaxed without being careless | Urgent (“WARNING: Action required immediately!”) |
|
|
225
|
+
| Direct | We say what we mean in few words | Curt (“Invalid.”) |
|
|
226
|
+
| Playful | We add moments of delight where appropriate | Silly (“Yee-haw! You deleted that record, partner!”) |
|
|
227
|
+
| Informed | We provide context when it helps | Arrogant (“As you should know, this feature...”) |
|
|
228
|
+
| Confident | We state things simply and clearly | Cocky (“Obviously, you’ll want to...”) |
|
|
229
|
+
| Honest | We’re transparent about what’s happening | Pressurizing (“Act now or lose your data!”) |
|
|
230
|
+
|
|
231
|
+
## Quick checklist for UI copy review
|
|
232
|
+
|
|
233
|
+
When reviewing interface copy, run through these questions:
|
|
234
|
+
|
|
235
|
+
1. **Is it clear?** Could someone unfamiliar with the feature understand what to do?
|
|
236
|
+
2. **Is it concise?** Can any words be cut without losing meaning?
|
|
237
|
+
3. **Is it consistent?** Does it match how the same concept is described elsewhere in the product?
|
|
238
|
+
4. **Is it human?** Does it sound like something a real person would say?
|
|
239
|
+
5. **Is the tone right for the moment?** Does it match the user’s likely emotional state?
|
|
240
|
+
6. **Does it follow Tapestry standards?** Cross-check against the relevant content foundations.
|
|
241
|
+
|
|
242
|
+
## Related content foundations
|
|
243
|
+
|
|
244
|
+
This guide is a companion to the existing Tapestry content foundations. When writing product UI copy, use this guide for voice and tone decisions, and use these foundations for formatting and structural patterns:
|
|
245
|
+
|
|
246
|
+
- [Addressing users in products](./addressing-users-in-products.md) for “you,” “your,” and “we” usage
|
|
247
|
+
- [Capitalization](./capitalization.md) for sentence case rules and product/feature naming
|
|
248
|
+
- [Micro copy](./micro-copy.md) for common terms (sign up, log in, to-do) and writing style
|
|
249
|
+
- [Prompts](./prompts.md) for confirmation dialog structure, button patterns, and destructive action copy
|
|
250
|
+
- [Punctuation](./punctuation.md) for when to use (and skip) periods, colons, and other marks
|
|
251
|
+
- [Use of emoji](./use-of-emoji.md) for emoji guidance in communications vs. product UI
|
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Design tokens
|
|
3
|
+
description: How Planning Center uses global and component-specific design tokens as a single source of truth for design decisions across platforms.
|
|
4
|
+
order: 10
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Design tokens
|
|
8
|
+
|
|
9
|
+
## Rules
|
|
10
|
+
|
|
11
|
+
- **Do** use tokens instead of hard-coded values such as hex colors or pixel spacing.
|
|
12
|
+
- **Do** reference component-specific tokens in a component’s styles.
|
|
13
|
+
- **Do** let component tokens reference global tokens, so a component can change without changing global values.
|
|
14
|
+
- **Don’t** apply a single global token directly across many components when each needs its own design decision.
|
|
15
|
+
- **Don’t** hard-code values for background color, text color, borders, padding, margin, font size, font weight, or border radius when a token exists.
|
|
16
|
+
|
|
17
|
+
## Overview
|
|
18
|
+
|
|
19
|
+
### What are design tokens?
|
|
20
|
+
|
|
21
|
+
Tokens serve as a single source of truth that represent small design decisions, and serve to provide repeatable design consistency across the ecosystem, even different environments/platforms (web, iOS, Android, etc). Rather than hard-coded values (such as hex values for color or pixel values for spacing), we use tokens in order to maintain scalability and consistency in our design implementation.
|
|
22
|
+
|
|
23
|
+
As a developer, working on design implementation, you will primarily interact with component tokens. Here’s a brief example to show how it works:
|
|
24
|
+
You want to apply a background color of `rgb(237, 179, 44)` to 3 elements/components: Topbar, Alert, and Button.
|
|
25
|
+
|
|
26
|
+
```css
|
|
27
|
+
/* Your tokens library provides a yellow-1 token */
|
|
28
|
+
:root {
|
|
29
|
+
--yellow-1: rgb(237, 179, 44);
|
|
30
|
+
}
|
|
31
|
+
|
|
32
|
+
/* Use the token for your 3 components */
|
|
33
|
+
.topbar,
|
|
34
|
+
alert,
|
|
35
|
+
button {
|
|
36
|
+
background: var(--yellow-1);
|
|
37
|
+
}
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
This works. If you want to change the color of all 3 components, you simply change the value of `--yellow-1`. However, your UX team eventually changes the colors and your 3 components no longer have the same background color. A more versatile approach, and the approach we will employ, is to create specific component tokens for each component:
|
|
41
|
+
|
|
42
|
+
```css
|
|
43
|
+
:root {
|
|
44
|
+
/* Your tokens library provides multiple "global" tokens */
|
|
45
|
+
--yellow-1: rgb(237, 179, 44);
|
|
46
|
+
--yellow-2: rgb(232, 129, 40);
|
|
47
|
+
--yellow-3: rgb(241, 161, 38);
|
|
48
|
+
|
|
49
|
+
/* the tokens library also provides you with component-specific tokens
|
|
50
|
+
which reference the "global" tokens */
|
|
51
|
+
--topbar-bg-color: var(--yellow-1);
|
|
52
|
+
--alert-bg-color: var(--yellow-2);
|
|
53
|
+
--button-bg-color: var(--yellow-3);
|
|
54
|
+
}
|
|
55
|
+
|
|
56
|
+
/* in your component style doc, you can reference only the tokens that pertain to your component */
|
|
57
|
+
.topbar {
|
|
58
|
+
background: var(--topbar-bg-color);
|
|
59
|
+
}
|
|
60
|
+
.alert {
|
|
61
|
+
background: var(--alert-bg-color);
|
|
62
|
+
}
|
|
63
|
+
.button {
|
|
64
|
+
background: var(--button-bg-color);
|
|
65
|
+
}
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
Now as you add components, your component tokens reference the global values. You don’t have to change the global values for everything in order to change it for your component.
|
|
69
|
+
|
|
70
|
+
These are simple examples. Component tokens become much more useful as you consider the many design decisions that are made for each one: `background-color`, text `color`, `border-color`, `border-width`, `padding`, `margin`, `font-size`, `font-weight`, `border-radius`, etc. All of those decisions are made in a design tool like Figma, and can all be represented with tokens.
|
|
@@ -0,0 +1,60 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Iconography
|
|
3
|
+
folder: Icons
|
|
4
|
+
description: How to use Planning Center’s centralized, one-color SVG icon system, including when to use info vs. help icons and carets vs. chevrons.
|
|
5
|
+
order: 30
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Iconography
|
|
9
|
+
|
|
10
|
+
## Rules
|
|
11
|
+
|
|
12
|
+
- **Do** use icons from the central Planning Center icon repository.
|
|
13
|
+
- **Do** use the i icon for brief, contextual information and the ? icon for Helpdesk entry points or extensive help.
|
|
14
|
+
- **Do** use carets for non-navigational dropdown menus and expandable content.
|
|
15
|
+
- **Do** use chevrons for left/right/back navigation.
|
|
16
|
+
- **Don’t** create custom icons outside the central repository without coordination.
|
|
17
|
+
- **Don’t** change icons away from one-color, scalable SVGs.
|
|
18
|
+
|
|
19
|
+
## Overview
|
|
20
|
+
|
|
21
|
+
Planning Center uses a centralized icon system to ensure visual consistency across all products. Icons are accessible, scalable, one-color SVGs distributed via NPM and managed in a central repository, making them easy to use across all supported platforms.
|
|
22
|
+
|
|
23
|
+
### Principles
|
|
24
|
+
|
|
25
|
+
- Use icons from the central repository for consistency
|
|
26
|
+
- Maintain one-color, scalable SVG format for accessibility
|
|
27
|
+
- Follow specific conventions for help indicators (i vs. ?)
|
|
28
|
+
- Use carets for dropdowns, chevrons for navigation
|
|
29
|
+
|
|
30
|
+
### Resources
|
|
31
|
+
|
|
32
|
+
_Central icon repository:_ All Planning Center icons [live in this Github repo](https://github.com/planningcenter/icons). It’s our central repository for icons.
|
|
33
|
+
|
|
34
|
+
_Icon catalog:_ View icons organized by product in the [Storybook catalog](https://planningcenter.github.io/icons/?path=/story/icons--accounts).
|
|
35
|
+
|
|
36
|
+
_Icon search:_ Search every icon and copy its symbol on the [Icon search](https://planningcenter.github.io/tapestry/?path=/docs/design-icons-icon-search--docs) page.
|
|
37
|
+
|
|
38
|
+
_Distribution:_ Icons are distributed as an [NPM package](https://www.npmjs.com/package/@planningcenter/icons) and exposed as standard SVGs that work with all supported platforms.
|
|
39
|
+
|
|
40
|
+
_Adding and updating:_ See the [icons Storybook](https://planningcenter.github.io/icons/) for instructions on adding and updating icons.
|
|
41
|
+
|
|
42
|
+
### Usage
|
|
43
|
+
|
|
44
|
+
#### Guidelines
|
|
45
|
+
|
|
46
|
+
##### Help indicators: i vs. ?
|
|
47
|
+
|
|
48
|
+
Use specific icons for different types of help to set clear user expectations:
|
|
49
|
+
|
|
50
|
+
_i (information icon):_ The UI is presenting useful information. Use when additional explanatory information is available but not an extensive help system. Think of this as analogous to an instruction plate mounted next to an operating control on a machine—brief, contextual guidance.
|
|
51
|
+
|
|
52
|
+
_? (question mark icon):_ The UI indicates a Helpdesk entry point. Use when extensive help is available or when providing an interface for users having problems. This implies a more sophisticated means of resolving issues, analogous to a link to the entire system’s operating manual already opened to the relevant page.
|
|
53
|
+
|
|
54
|
+
#### Carets vs. chevrons
|
|
55
|
+
|
|
56
|
+
Use different directional indicators based on the interaction type:
|
|
57
|
+
|
|
58
|
+
_Carets:_ Use for all non-navigational dropdown menus (ignoring topbar). Carets indicate expandable/collapsible content or menu options.
|
|
59
|
+
|
|
60
|
+
_Chevrons:_ Use as left/right/back navigation arrows. Chevrons indicate directional navigation between pages or views.
|