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

Multi Author / Co-Author Behaviour #221

Open
alexander-schranz opened this issue May 25, 2022 · 0 comments
Open

Multi Author / Co-Author Behaviour #221

alexander-schranz opened this issue May 25, 2022 · 0 comments
Labels
To Discuss The core team has to decide if this will be implemented UX Only affecting the end user

Comments

@alexander-schranz
Copy link
Member

alexander-schranz commented May 25, 2022

In some cases there it is maybe required that instead of one main author there are additional authors. There are 2 ways to achieve this.

  1. Deprecate the author and always make it possible to use use multiple authors

This make it uncontrolable to show a main author in a smart content overview and would add to many rrelation problem to this kind of things. But would make the author work the same way as tags and categories.

  1. Have the possibility for mainAuthor but allow to add additional authors / co-authors

This handle author same way as we handles mainWebspace and additionalWebspace it make filtering by author a little bit more complex but the content manager can so control maybe which author is the main one and should be shown on overview pages.

Why an own behaviour would be required?

I think sulu should out of the box in future support that smart contents could also be filtered by author. Why it is easy to add co authors via the content bundle, it is not easy change the behaviour of a author based filter.

So if we have additional author and co author in the core it is already possible that a author overview can display all articles from that author where he is the main author and additonal author out of the box.

@alexander-schranz alexander-schranz added this to the Stable Release milestone May 25, 2022
@alexander-schranz alexander-schranz added To Discuss The core team has to decide if this will be implemented UX Only affecting the end user labels May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
To Discuss The core team has to decide if this will be implemented UX Only affecting the end user
Projects
None yet
Development

No branches or pull requests

1 participant