Pajamas documentation > follow-up to AI CTA guidelines

Context

This issue documented the additional documentation required for AI CTAs in design.gitlab.com. This issue is a follow-up to !3954 (merged).

Potential additional documentation

Not all of the below documentation may be necessary. Each table row needs to be considered and it's possible that it will be marked as WONT DO with rationale.

Potential documentation	Rough draft content	MR link	Status
AI CTAs can disappear because AI can be turned off. How does that work when the AI CTA was the primary action? What becomes the primary action then? (started from this discussion)		!4022 (merged)	done
Consider using “GitLab Duo” outside of the CTA	Consider incorporating "GitLab Duo" into feature onboarding and supplemental UI copy, provided it does not negatively impact usability. This approach will help users associate "GitLab Duo" with the AI tanuki icon and AI-powered features.	!4005 (merged)	done
Consider using “AI” outside of the CTA to give additional context	It’s acceptable to use “AI” outside of the CTA to give additional context and better explain what the feature does. Try to use “AI” in conjunction with “GitLab Duo” to help the user associate GitLab Duo with AI-powered features.		Not started
Make sure the CTA is consistent with the documentation and marketing material	Inconsistencies in how we refer to AI-powered features can lead to confusion. Make sure users encounter the same language in marketing material, documentation, and the product.In cases where the feature naming is inconsistent, work with relevant stakeholders to determine the appropriate feature name and get it consistent across marketing, product, and documentation.		Not started

Definition of done

This issue will be closed when all items from the above table have merged or are marked as WON'T DO with rationale.