Open mvantellingen opened 7 years ago
A neat way might be to let developers choose between using the mixin and using the PersonalisablePage class that already includes the mixin. With good documentation a developer can decide between the two and the implications that may arise with the selected option.
Jeah I agree. I've implemented such before when using Aws Machine Learning to predict Page objects based on 'segments'. In this case a Panel 'Segments' was shown on the edit Page were the user can fill in their tags.
That's pretty much what I had in mind. Using this method we won't have to complicate the "tag rule" and can always assume the tags are in the same field.
This requires to have tags to be attached to a Page, which currently isn't the case. Would it be feasible to have a e.g.
SegmentedPersonalisablePage
which has a panel for adding tags?