I've put together below some research, learnings, explorations and quite possibly a solution to the table component creation. We now have a good mix of experience level with both Figma and principles of visual design, so this document is aimed to appeal to the broad range. Some of you will benefit from the detail while others might find some of steps mentioned too obvious. In either case, glancing through it might be useful so we all have a shared understanding of the challenges, the approach and the attempted solution.

1. What is a table

A table is a block of element that at least consists of a single row and a single column. The need for using a table component should at least satisfy this requirement.

2. Preqin's specific use-case for tables

A lot of what we do in design is perhaps incorporating a table. Although the use-case can vary the general need is to have a component that can readily be styled based on a existing data table created and passed on over to a designer by a product manager. So in the ideal most scenario a table component should help us copy content (as a whole) and paste in design.

3. Preqins' table's design needs and consideration

1. Our tables will have a table header and a table body
2. We might have horizontal banding
3. We will tables with both letters and numbers
4. We will have various variants for both the header and body
5. Our table as a whole will need to be rounded at the edges
6. The column and rows will need to show separation

4. What is the ideal table component solution

To achieve the above use-case the ideal solution would be to have a Figma Plugin that links to a Google Document and is able to design our table based on data in the table.