I. Design
II. CMS



square (1:1) or natural


full-width and narrow-width layouts to be supported?
line 1 (secondary color) and line 2 (primary color).

Body field: This cannot simply just be a rich-text field.
A variety of designs/layouts need to be accommodated. And Strapi's rich-text field is:
a) Limited in what it can do, and
b) Is not extensible
Therefore, the field has to be a "container" to which various content blocks are inserted into. This is how it works presently.Horizontal rule: One of these will automatically be included after the section's content.
Hence, no need to add one manually like how it is done now.Image captions: Support for this can be added.
No design reference for this exists presently. But will whip up something basic and minimal.


These are the "1-column Layout" and "2-column Layout" components, which establish 1-column and 2-column layout contexts respectively.

This will be replaced with two new components — "Column (full-width)" and "Column (narrow-width)".
This depends on whether both these content widths need to be supported (see the "Content Area Widths" slide above).




layout: 2-column, 3-columnfeature_first_post: Makes the first post span the full-widthimagecontent: a rich-text field that supports any kind of text content — heading, byline, excerptThis component is a "dynamic content block".
Ones specifies the content-type, a category and how many "posts" are needed (ex. 2), and a list of posts that meet the specified criteria will be returned (on the frontend).




2-column bulleted list: This won't be possible unless the text content field is a generic content block container.
2-column layouts aren't possible within a rich-text field.