User engagement

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

Fortune has arrived for Drupal 6.

The Fortune module is a port of the venerable BSD Unix fortune cookie program created by Ken Arnold. It provides a block that displays a random fortune each time the page is reloaded.

Fortune is similar to Quotes, but was built to specifically support the huge library of "fortune cookie files" which often rely on an 80 column display, a monospaced font, and tabs set 8 spaces apart.

The "fortune cookie file" itself is a simple ASCII (ISO-Latin-1) Unix text file in which each fortune is followed by a percent symbol (%) on a line by itself. Fortune files usually come with a binary index file having the same name plus a ".dat" extension.

The Fortune module uses the "fortunes" folder in the files directory as storage for both fortune and index files. You can add new fortunes to that folder via FTP or by using the Upload field on the Fortune Settings Page (admin/settings/fortune). When using FTP you should include the .dat file, but in the Settings form you only have to upload the fortune file itself, and a .dat file will be created automatically.

There are lots of places on the web to get fortunes. Most fortune files are GPL or public domain and free for distribution. Some links to sources of fortune files are included on the module's settings page.

Converts ANSI colors into more web friendly equivalents.