Chatbot: Right aligned user message variant
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- figma
- 领域
- design
调研方向
Start by reviewing the linked Aladdin Figma files and the four listed message-layout use cases, then check the linked Jira issue PF-3428 for context. Done means producing the requested high-fidelity mockups, redline margin and padding token specs, and responsive-container behavior documentation.
由索引模型根据 Issue 内容生成。
描述
Based on the results of the Compass/unified theme dev/design sync on Jan 14:
We are updating our existing Chat components to support a more modern "threaded" appearance. This issue focuses on defining the spacing and layout behavior when messages are right-aligned and when metadata is hidden.
- Standard Layout (Left-Aligned)
-
Case A (Full): Message is left-aligned; Avatar and Metadata (AI label, timestamp) are visible.
-
Case B (Minimal): Message is left-aligned; Avatar and Metadata are hidden. Ensure the message body aligns correctly with the container edge.
- User-Specific Layout (Right-Aligned)
-
Case C (Full): Message is right-aligned; Avatar and Metadata are visible.
-
Case D (Minimal): Message is right-aligned; Avatar and Metadata are hidden.
Specs Needed
-
Margin/Padding Tokens: Define the specific left-margin or padding value for right-aligned user messages to ensure they don't span the full width of the container (creating the "right-aligned" look).
-
Vertical Spacing: Double check if vertical spacing between messages changes when metadata/avatars are removed to ensure the "simplified" view doesn't look too cramped or spaced.
Alignment Logic: Ensure the design clarifies if the message "bubble" expands to fit content or remains a fixed width with a margin.
-
High-fidelity mockups for all 4 use cases listed above.
-
Redline specs showing token values for margins and padding.
-
Documentation on how the layout behaves in a responsive/narrow container.
Just so you have it handy, these are the aladdin figma files we were looking at during this discussion.
Jira Issue: PF-3428
- 主要语言
- 没有语言数据
- 星标
- 50
- 派生
- 40
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
patternfly/patternfly-design-kit 的其他 Issue
-
Patterns & Extensions Library Topology
难度 4/5 3-5 天 新手友好度 48/100
-
难度 2/5 1-3 小时 新手友好度 35/100
-
React component groups
难度 5/5 一周以上 新手友好度 25/100
-
PatternFly 6
难度 4/5 3-5 天 新手友好度 35/100
-
Component Library
难度 2/5 1-3 小时 新手友好度 48/100
查看 patternfly/patternfly-design-kit 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
Request: Bizum未关闭new icon permissions in review
难度 2/5 1-3 小时 新手友好度 72/100
simple-icons/simple-icons#15080 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
IBM/carbon-components-ember#1049 ·
维护者通常 1 天内回复
-
Bug Status: Needs Review Toolkit
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 74/100
yegor256/ppt-slides#105 ·
维护者通常 1 天内回复