Adjust contributor-page (first step in workflow)

[krokkie]

• heading field - remove from common, move to detailed section
• type field in detailed section = first field, most important.
• conditional fields: if type=exposition / technical - then show subverse widget
• conditional fields: if type=application, then show heading + tags, else hide them

[rudolfbyker]

• Heading and type fields are moved in commit 20da27d
• This depends on Issue Sub-verse widget for lwc's #7

[rudolfbyker]

Conditional fields require the "type"s to be defined by the module, and not in a Taxonomy... See issue #14

[rudolfbyker]

The type stays taxonomy_term_reference, but the taxonomy terms now have a field which determines the sort behaviour: "lw_listing_order". Pseduo-code for the last two TODOs:

x = the lw_listing_order field of the taxonomy term referenced by the 'position' (a.k.a. type) field
switch x
  case LIVING_WORD_LISTING_ORDER_SINGLE_SUB_VERSE
    show subverse widget
  case LIVING_WORD_LISTING_ORDER_APPLICATION_TAGS
    show heading field
    show tags field
  case LIVING_WORD_LISTING_ORDER_PREDOMINANT_MULTI_VERSE
    ???
  default
    show nothing extra

@krokkie Please verify if this makes sense...

[krokkie]

Lyk reg.

It does not only define the sort order, but also which fields are "required" in the editor, where it is presented in a list, etc.

[rudolfbyker]

Hmm... in that case, we need new names for the behaviours, and the field should be called lw_listing_behaviour and not lw_listing_order.

[rudolfbyker]

I propose that we name the possible values of lw_listing_behaviour as follows:

• LIVING_WORD_LISTING_BEHAVIOUR_BROAD
• LIVING_WORD_LISTING_BEHAVIOUR_NARROW
• LIVING_WORD_LISTING_BEHAVIOUR_TOPICAL

[rudolfbyker]

On the edit page for taxonomy terms in the position vocabulary, one can now select:

Since commit 1f28b6a, the heading field only appears when application (or any taxonomy term where the field lw_listing_behaviour == LIVING_WORD_LISTING_BEHAVIOUR_TOPICAL) is selected.

Issue #16 blocks this.