SSWConsulting / SSWConsulting/SSW.Rules
🦙 TinaCMS Dependency - Table Alignment - Allow centering emojis and text within table cells
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
Requested by: @suiyangqiu via YakShaver.ai 🦬
cc: @suiyangqiu, @Marxoz, @PothieuG, @Freego1783
Hi Team!
🟥 Watch the video (1 min 4 sec)
Url from screen share: https://ssw.com.au/rules/admin#/rules/mcp-servers-for-context
Pain
As a content author working in Rules V3 (TinaCMS), I want the ability to center emojis or text within table cells so that tables with single icons (e.g., green check emojis) are visually aligned and easier to read. Currently, emojis cannot be centered, even with manual spacing. This feature should either allow users to choose text alignment per table cell/column or automatically center content when a cell contains a single emoji. Please CC Michael Q on updates.
Acceptance Criteria
- Users can control horizontal alignment (left, center, right) for table cell content, or
- Table cells containing only a single emoji are centered by default without manual spacing
- Centered alignment is visually consistent across different screen sizes and editors
- Existing tables are not negatively impacted by the change
- The solution works within Rules V3 (TinaCMS) tables
Screenshot

Figure: Table cells with single emoji cannot be centered
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Rules V3 TinaCMS table editor and reproduce the single-emoji alignment problem shown in the linked screenshot. Compare the two proposed approaches—per-cell or column alignment versus automatic centering—and verify behavior across screen sizes and existing tables. The issue names no files or tests, so the relevant entry points and regression checks must first be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100