Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate seasons-related code into extension #323

Open
carstingaxion opened this issue Nov 27, 2023 · 1 comment
Open

Separate seasons-related code into extension #323

carstingaxion opened this issue Nov 27, 2023 · 1 comment

Comments

@carstingaxion
Copy link

Proposed NEW data modell (maybe version 1.0.0)

taxonomy ➡️

post_type ⬇️
post_tag category NEW wp_theatre_season_shadow
wp_theatre_prod ✔️ ✔️ ✔️
wp_theatre_event 🪢 🪢 ✔️
wp_theatre_season 🔃

All this could also be done for Seasons, but I suggest separating all seasons-related code into an extension.

Everytime I created websites for theater-companies or solo-artists, without an own physical stage, seasons were not needed at all. For all houses with own and/or guest artists, seasons were a strict need. It's a 50:50 thing, if website-owners need seasons-handling.

When we have a working plan for how events relate to productions, we can go on here.

@carstingaxion carstingaxion changed the title Separatel seasons-related code into extension Separate seasons-related code into extension Nov 27, 2023
@slimndap
Copy link
Owner

Agreed. Seasons are hardly being used in my experience. Some theaters usesit to create a hidden page with all events for the next season. This allows them to preview all event contents, without publishing it on the website.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants