Skip to content

Conversation

@matthew-beaty
Copy link
Contributor

@matthew-beaty matthew-beaty commented Dec 19, 2025

FOO-2877
Basic updates to support Card Embeds feature. This feature is feature gated for now, so we may want to add a coming soon label or something.


Note

Add documentation for Card Embeds (placement options, format settings) and related CSS selectors; update form-factor count to six and element selector guidance.

  • Guides & Surveys docs (content/collections/guides_and_surveys/en/form-factors.md):
    • New form factor: Card embed
      • Adds description, target selector requirement, placement options (Append/Prepend/Before/After/Replace), and format settings (Width, Alignment, Height, Content layout, Title/content alignment, Actions bar, Z-index, Text animation).
    • Global updates
      • Increase form-factor count from five to six.
      • Update Element selector section to include card embeds.
      • Properties → Position: add Card embed row; minor punctuation tweaks.
  • Custom CSS docs (content/collections/guides_and_surveys/en/custom-css.md):
    • Add .amplitude-engagement-card-container to form factor containers.
    • Add card-specific selectors: .amplitude-engagement-card, .amplitude-engagement-card-content.
    • Minor copy/formatting cleanup in Important considerations.

Written by Cursor Bugbot for commit d3b4f3f. This will update automatically on new commits. Configure here.

| After element | Places the card immediately after the target element. |
| Replace element | Replaces the target element with the card. |

Click the three dot menu to access format settings.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: UI element "three dot menu" missing bold formatting (Bugbot Rules)

The UI element "three dot menu" isn't bolded. According to the style guide, buttons, tabs, and fields require bold formatting. This text refers to a specific menu element in the interface and the style guide specifies using bold for such elements (for example, Save, Settings). The text "three dot menu" in line 159 needs to be formatted as three dot menu.

Fix in Cursor Fix in Web

| Pins | Controls position of the pin relative to the target element. Select the position and the alignment of the guide. For example, Position: `Bottom of target` and Alignment: `Left` places the guide below the target element, and aligns the guide's left side with the target's left side. |
| Tooltip | Specify the side of the target element that the info marker appears. Add additional vertical or horizontal offset as necessary. |
| Banner | Top or bottom of the page. Set the **Sticky** option to keep the banner visible while the user scrolls. Choose the Display style: **Inline** to display the banner within the contents of the page, or **Overlay** to float the banner on top of the page contents. |
| Card embed <br/> {.tag .web .zero} | Controls position relative to the target element. Select from Append, Prepend, Before, After, or Replace. Configure Width (Auto, Fixed, or Full), Alignment (Left, Center, Right) when width isn't Full, and Height (Auto, Fixed, or Full). |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Inconsistent bold formatting for UI option values (Bugbot Rules)

The Card embed row in the Position table uses plain text for option values like "Append, Prepend, Before, After, or Replace" and "(Auto, Fixed, or Full)", but lines 163-165 in the same document bold these same values as Auto, Fixed, Full, Left, Center, and Right. This creates an inconsistent formatting pattern within the same PR where identical option names are formatted differently.

Fix in Cursor Fix in Web

| Pins | Controls position of the pin relative to the target element. Select the position and the alignment of the guide. For example, Position: `Bottom of target` and Alignment: `Left` places the guide below the target element, and aligns the guide's left side with the target's left side. |
| Tooltip | Specify the side of the target element that the info marker appears. Add additional vertical or horizontal offset as necessary. |
| Banner | Top or bottom of the page. Set the **Sticky** option to keep the banner visible while the user scrolls. Choose the Display style: **Inline** to display the banner within the contents of the page, or **Overlay** to float the banner on top of the page contents. |
| Card embed <br/> {.tag .web .zero} | Controls position relative to the target element. Select from Append, Prepend, Before, After, or Replace. Configure Width (Auto, Fixed, or Full), Alignment (Left, Center, Right) when width isn't Full, and Height (Auto, Fixed, or Full). |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Missing conjunction "or" in list of options (Bugbot Rules)

The list "(Left, Center, Right)" is missing the conjunction "or" before the final item. According to the style guide's grammar rules for lists of three or more items, this needs to include the conjunction with an Oxford comma. Compare with line 164 in the same document which correctly uses "Left, Center, or Right". The text in line 237 is inconsistent and grammatically incomplete.

Fix in Cursor Fix in Web

@matthew-beaty matthew-beaty changed the title Basic Card Embed updates FOO-2877 Basic Card Embed updates Dec 19, 2025
@JeffScattini-amplitude
Copy link
Collaborator

As mentioned in the slack comments, we should catagorically not be including content that isn't accessible for customers and should not be using the tech docs for marketing content. I think we should work with Brand management to create a blog post for the corpsite for this content and then, when the feature is ready for GA, bring this back into the documentation.

@lchoward lchoward marked this pull request as draft December 19, 2025 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants