User engagement

The Priorities module helps on choosing the best and prioritizing alternatives among a set of various proposals. The scoring is based on users' participative contribution through rating each and every alternative with a level of priority.

Provides integration with the Spotify Metadata API and a field to display artist, album and track information with a link that opens the Spotify client.

The Eval API module provides an API for other modules to utilize that facilitates the adding of arbitrary criteria to content types and nodes that can be evaluated as seen fit by the implementing m

A Questions and Answers feature for Open Atrium, with User Reputations.

QA Checklist provides a list of Quality Assurance (QA) best practices for Drupal and tracks your team's progress against it.

QA Checklist helps you

• Get ready to go live
• Review site for quality assurance

For support and/or help launching your site please contact WebOzy.

D8

The 8.x-1.x branch will contain a 1to1 backport of the content_moderation module in Drupal core, but for Drupal 8.1.x.

D7

User reviews can be found here

Iam looking for Co-Maintainers helping to deal with the bugs and features. Just contact me - thank you in advance

In Short

This module does what a lot of people know under staging. While you have a live version for all visitors, you can work on a new revision (or revisions). To set a newer revision live, you have to approve it in a workflow.

You can have a look at this video podcast. The module and its usecase is explained there.

Usecases

You want a lot of people edit your nodes or documents, but they should not change the "visible" version just right away. Lets say for some quality assurance, process description or sensible content in your company.

1. Some selected group should first review those changes (based one a specific revision marked for "approval). In the meantime others should be able to edit and create new revisions (which are not part of this approval process)
2. Later some group can approve that revision and make it the new live-version
3. Every state change (review, approval..) should get logged in a history. You always want to know, who reviewed / approved what, when and what revisions