Maintainers strive to actively monitor issues and respond in a timely manner.

fpp components

This is a repository of components or widgets that can be used inside panels. This was initially design to work with Panels as Field (paf) but it can be used in every manager using panels.

⋅ Categories: Actively maintained, Under active development, Developer tools

paf

This module provides a new type of field: the panel.

⋅ Categories: Actively maintained, Under active development, Content editing experience, Developer tools

Tracker 2 unsubscribe

This module provides the ability to unsubscribe from the tracking of individual nodes by providing the "Unsubscribe" link, which is shown in the node links area for users who have the proper permis

⋅ Categories: Actively maintained, Maintenance fixes only

Autoload benchmark

Note: This is meant to always remain a sandbox project.

"Autoload benchmark" is a tool to measure the performance of PSR-0 class loading on your site.
Especially, it measures how well the classloader solution scales with a high number of modules.

Typically you want to compare these two modules:
- http://drupal.org/project/xautoload - a rewrite of the D8 class loader with performance and flexibility in mind.
- http://drupal.org/project/classloader - a direct port of the D8 class loader.

The case that we test is
- 300 test modules with a "lib" folder for class loading
- 300 classes to be loaded, one from each of the 300 test modules.

Typical usage:
- Create an arbitrary Drupal 7 site.
- Install autoload_benchmark.
- Disable all modules/themes that have a dependency on xautoload or classloader.
- Install + enable "classloader" module. Make sure that xautoload is disabled
- Run "drush autoload-benchmark"
- Install + enable "xautoload" module. Optionally disable "classloader".
- Run "drush autoload-benchmark". Compare the numbers.
- Play with different settings for APC cache on classloader. I think on xautoload you need to hack around, to disable apc cache? I don't remember.
- Play with the "generate.php" script, to try numbers other than 300. But, be careful which modules are enabled or disabled!

Benchmark result

⋅ Categories: Actively maintained, Under active development

Checkpoint

Enterprise Web Content Management System

If you are publishing a lot of content from a number of authors, you should seriously consider a content management system (CMS). A quality CMS can help you streamline your publishing processes. It can allow you to develop an information architecture that is robust, yet flexible. It can allow you to manage your content efficiently and cost-effectively.

What are the benefits of a web content management system?

A CMS makes it easier for people to create, edit and publish content on a website. Historically, website publishing has required significant technical skills (HTML, programming). A good CMS allows non-technical authors and editors to easily and quickly publish their content.

At some point even a content management site will need to be upgraded with a new and fresh visual design. Whereas static sites require a complete rebuild in these cases, content-managed sites can have a new design applied to its templates. The entire site, including all archived content, will very quickly reflect the new look and feel. This means that future site redesign projects will usually be less expensive than previous development projects, not more expensive, which is the case with static web development.

⋅ Categories: Actively maintained, Under active development

Pages

Subscribe with RSS Subscribe to RSS - Actively maintained