Part of Content quality checker enhancements #125. We need a centrally-managed field that sets content quality expectations across multiple AI integrations. This is a natural evolution of the package’s existing feature set, in particular content checkers. As the number of AI integrations on a site grows from single to double digit, we don’t want to repeat tone of voice information everywhere.
In the future this might need to be configurable per site or per site section. For now, aligning with other settings is probably plenty good enough.
Part of Content quality checker enhancements #125. We need a centrally-managed field that sets content quality expectations across multiple AI integrations. This is a natural evolution of the package’s existing feature set, in particular content checkers. As the number of AI integrations on a site grows from single to double digit, we don’t want to repeat tone of voice information everywhere.
In the future this might need to be configurable per site or per site section. For now, aligning with other settings is probably plenty good enough.