Style blocks (part 1)

[dawnwages]

• Heading : https://github.com/djangonaut-space/wagtail-indymeet/blob/develop/indymeet/templates/blocks/heading.html
  This heading could be for stand alone or call out large text. It defaults to
  When using headings h1,h2,h3,h4, in Rich Text box, style all headings by h so it will be inherited and additional styles can be added to this default heading.
• Paragraph : https://github.com/djangonaut-space/wagtail-indymeet/blob/develop/indymeet/templates/blocks/paragraph.html
• Quote block : https://github.com/djangonaut-space/wagtail-indymeet/blob/develop/indymeet/templates/blocks/quote-block.html
• Video Embed : https://github.com/djangonaut-space/wagtail-indymeet/blob/develop/indymeet/templates/blocks/video-embed.html

[dawnwages]

TailwindCSS has a pretty aggressive normalize.css that doesn't allow for easy override. Currently tailwind is implemented in the unsafe temporary version using the cdn. #163 There's a ticket already to create a more production-ready implementation by adding tailwind in node.

I have two options: 1. tackle production tailwind set up now and hopefully the css inheritance allows me to style h1, h2, h3, h4 blocks and we can then use RichText Blocks. or 2. customize each element so we can add custom classes to each.

[dawnwages]

Went with option two and gutted the features of the RichText Block. It's still beneficial to keep RichText Block for underline, italicized, bold, strikethrough, superscript and subscript text.

The status of all elements can be seen on staging https://staging-djangonaut-space.azurewebsites.net/comms/elements/

[dawnwages]

Also need to make sure that all of these elements are responsive. Currently they are not.