FP-1414: More Classnames for Django CMS Style Plugin

[wesleyboar]

Overview

Add more class names¹ for UI patterns via

• quick, simple UI²
• low-maintenance code

Issues

• FP-1414

Screenshots

FP-1318.Section.Pattern.via.Style.Plugin.mov

Testing

local: instructions
remote: https://dev.cep.tacc.utexas.edu/ (build, deploy)

On a test page:

1. Create Style plugin.
2. Create Text plugin, nest under Style plugin.
3. Set "CLASS NAME" to some of the available values.
4. Confirm Style plugin instance has classnames from each choice.

Notes

Comparison of Solutions

Plugin	Entry Method	Input Method	Pros	Cons
Style	"Class Name"	one dropdown field	quick to find, min. maintenance	assumes CSS knowledge
Style	"Adv. Settings" → "Additional Classes"	comma-delimited list	zero maintenance	assumes CSS knowledge, slow to find
others	"Adv. Settings" → "Attributes" + class	space delimited list	zero maintenance, consistent	assumes CSS knowledge, slow to find
custom	plugin field choices	one or more dropdown fields	easy to find, could be most intuitive	high maintenance, initial attempts unintuitive

Related PRs

• Add Tags & Only Section Classes:
  FP-1318: Create Section Pattern via Style Plugin #430
• Using Container Instead:
  FP-1318: Create Section Pattern via Bootstrap Container Plugin #431

Footnotes

1. Not all class name combinations would be provided, because that would create too long a list. To support other combinations, a skilled CMS editor can add a comma-delimited list to Style plugin instance at "Adv. Settings" → "Additional Classes".³ ↩

2. The UI is approved by our primary CMS Admin/Editor. The UI is not too complex for a regular CMS editor. ↩

3. This is the second solution/entry of the table in "Notes" → "Comparison of Solutions" (in this PR description). ↩

[wesleyboar]

Merging based on approval of #430 which demo'd and suggested this code also.