figuren-theater / ft-theater

All you need, if you run a theater or a WordPress Multisite network for puppeteers
https://figuren.theater
GNU General Public License v3.0
0 stars 0 forks source link

Team / Ensemble data #4

Open carstingaxion opened 10 months ago

carstingaxion commented 10 months ago

Problem

In the context of Theaters you almost everywhere have teams, sometimes called ensemble. This is true for big houses, where you might find multiple continuous teams, as well as for solo freelancers with maybe different teams per project or task. In WordPress editing we need a way to assign singular persons (or even teams) to singular content, like art-direction for productions or musician for events.

(working) solutions of the past

Idea:

### Architecture 
- [ ] have a shadow taxonomy on regular users
- [ ] Of a particular, new role, maybe *team*
- [ ] Assign the taxonomy to all public post_types
- [ ] Could use a modified *authors* rewrite tag, like ‚team‘ globally, including even the regular editors and administrators (which could be a problem)
- [ ] Allows to transform existing tags or categories into a shadow-user-taxonomy-term
- [ ] Needs automated user-creation, when a new shadow-user term is created via the editor
- [ ] new shadow-users should be created with a gibberish email address to pass registration, which should be deleted immediately after the user is registered 
- [ ] can a wp-user have no email assigned?
- [ ] how to make sure, the user gets a working email address appended, when an additional role is assigned
### UI
- [ ] use all the default stuff for authors, like a bio-block etc. to be used with our shadow-users, probably using ‚block-variations‘
- [ ] Could show a new section on the profile.php with all data, that has the own shadow taxonomy term assigned, would be a simple, standard wp_query
- [ ] Instead of a regular terms.php, visible via show_in_menu argument of register_taxonomy, we should provide a modified users.php view, labeled as Team under Users
- [ ] As long as the profiles are not taken over, as long as the user has only the *team* role assigned, they should be hidden from the regular users.php screen
- [ ] WordPress‘ default UI only allows to manage one role per user, which is contradictory 

Pro

Contra

carstingaxion commented 5 months ago

Simpler idea:

We have a simple hierachical taxonomy, called "network".

And a block, that is strictly tied to a term of that taxonomy. If one of such blocks gets saved into post_content, the corresponding term is attached to the post immediately. If the block is removed, also the term is removed from that post.

This particular block should allow the editors to pick one term out of this taxonomy. Now the simplest, would be to just render out the term title.

But, it would be nice to allow for some customisation at this point. Even the block stays somehow connected to the chosen term, the (human) editor should be able to overwrite the term title or whatever data is aggregated from the term, may it the term description or any kind of term_meta. This overriding happens only within that post, where the block is used. Nothing should be changed on the term itself.

Imagine an ingredients taxonomy, where the editor could choose from. The chosen terms could be apples and oranges, but the publishing editor could instead overwrite it to: green apples and blood oranges, while still keeping the post-term-relation.

The desired block would in best be a block-variation of the group block, which gets pre-populated with a paragraph block of the term-title and another paragraph-block with the term description. Those blocks don't need any special connection, because we can expect, nobody would rename the term of "Oranges" to something different than "Oranges", so if the editor stays with the suggested default, it'll be fine.

To come back to my introduced "network" taxonomy. My users are artists and theaters and they should be able to easily select ensemble members of a "production" post_type or the partners and sponsors of an "event" post_type. Members, partners and sponsors could be three parent-terms within that "network" taxonomy.

I want to prevent the content-editor from having to select the taxonomy-term from the settings-panel and the need of adding a term-link block to the content and so on.