Identify boundary of Calypso without custom content-types

[mmmavis]

We should utilize WordPress' default content type and features. This will help standardize creation flow for the sites we are going to build & restrict site admins to making content updates only (vs layout, theme changes etc).

Let's identify boundary of Calypso without custom content-types and discuss if we can solely rely on WordPress built-in features.

Possible issues (to be updated)

• editing multi-section pages
• editing multi-field sections
• updating hero images / banners
• updating CTAs
• formatting and CSS classes mapping (e.g,. pre-assign CSS class .subhead to subheaders so they get styled properly)

Next steps

• continue identifying possible boundary without custom content types
• explore alternative approach / workaround using WordPress's built-in features only

Some useful resources

• Post Types: https://en.support.wordpress.com/posts/post-formats/

[mmmavis]

/cc @simonwex @gvn @vazquez

[mmmavis]

Editing multi-section pages

This can be done by breaking each section into a WordPress subpage.

:exclamation: Potential issues:

• hard to preview the content in context of its parent page
• we need to remove buttons and controls other than the basic "text decoration" ones from the WYSIWYG editor to keep resulting HTML clean and well structured.
• depends on the number of pages we have on the site, we might end up creating numerous subpages using this approach.

Editing multi-field sections

Example use case: a section contains an image thumbnail positioned at left & a header, a subhead, and a description positioned at right & a CTA button positioned somewhere.

:bangbang: Issues:

• Can't really achieve this without custom field support and without asking site admins to touch HTML code.
• Issue with previewing as well.

Updating CTAs

:bangbang: Similar to what's in "Editing multi-field sections" mentioned above.

Updating hero images / banners

We can just make use of the "featured image" that's set in the WordPress page.

[mmmavis]

:exclamation: This ticket is now locked. Please continue the discussion on https://github.com/mozilla/wp-calypso instead. For more info see README.