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

Mojo

A starter theme geared towards advanced themers who want a solid starting point without extraneous Drupal markup. Check out the Mojo Handbook for more details.

The main goals of the Mojo theme are:

  • Be future friendly.
  • Improve accessibility.
  • Enhance the mobile experience.
  • Optimize front-end performance.
  • Use modern code: HTML5 and CSS3.
  • Prune the excessive markup Drupal spits out by default.

Boosthelper

A helper module for Boost. :o)

Boosthelper crawls the URL of a newly created/edited node immediately, instead of waiting for the next cron run. Also immediately recrawls the front page if Boost set to "Clear the front page cache when promoted". Also clears all (public only) organic groups cached pages that the node appears in and immediately recrawls them.

Works with or without Pathauto.
Respects node access permissions. (e.g. Private og posts will not be cached.)

Successfully tested on stand-alone Drupal 6.19 and 6.20 installations with Boost 6.x-1.18 and Boost 6.x-1.x-dev2011-Feb-25.

Also successfully tested on Aegir 1.0 rc7 managed Drupal 6.19 and 6.20 sites with boost 6.x-1.x-dev2011-Apr-12 and provision_boost 6.x-0.5.

Solrfield

This is a placeholder page for a new module that is intended to create nodereference style relationships between nodes and solr datasources.

A common use case for this would be the following:

Acme Brick Building has a list of products maintained by the Acme Product Management System. That system sends all of its products to a solr index. The Acme drupal website needs to relate various items, such as press releases with products in the product management system and display basic information about them.

This should be accomplished by implementing the solrfield module, adding a solrfield field to the article content type and configuring this field to query a designated solr instance. The key value of the selected results will be stored in the filed related to this item.

what this project will not be:
this project will not be an import system that imports data from other sources. this will merely query a solr index and present data it gets back based on a defined relationship.

future plans/goals
It would be great if this could be integrated into views3 in any of a few ways:
1) use views 3 to directly compose the solr query and have this filed use the same concept nodereference uses of "optional view to use".
2) with a way to join data across multiple sources.

If you are interested in helping with this project please feel free to contact me!

Local Baha'i Community Website Incubator

Overview

The Local Baha'i Community Website Incubator is an installation profile incorporating many features that might commonly be used on a website for a local Baha'i community or a group of communities.

  • Multi-user site: Give each member of the community his or her own account on the Incubator site. A role-based permission system will allow you to decide who can post which kinds of content. The entire community can contribute to the website!
  • WYSIWYG editing: Your writers and editors won't have to be fluent in html, css, or other web technologies in order to post basic pages; instead, they can write their stories directly on the site in a WYSIWYG editor that is like a simple word processor. The editor will allow users the flexibility to format individual stories as they see fit, while maintaining a consistent style throughout the site.
  • News and blogs: Designate some writers in the community as "reporters" and they can publish local news. Other users given the role of "bloggers" may write personal stories about community life. In the future, you can even submit your site's stories for inclusion in local news sources, like Google news.

Contentbrowser

As part of the project http://ndla.no we have created this module which makes it possible to insert any node into other nodes. ie) Inserting node of content type X into node 123. This is done via an easy to use interface (via WYSIWYG API) for the user where he/she searches for the node to insert (although you could go hardcore and write the tags manually).

Every content type has its own template, by default via Drupal's own templating system, this can (and should) be overridden.

Contentbrowser uses tags which means that no url's are hardcoded into the node's body.

Contentbrowser can be what you are looking for if:

  • You use any kinda of media-module (video, audio etc) and want to reuse those nodes in blog posts and articles
  • You have used imagebrowser / insertnode but need more control via hooks and templates
  • Your users simply can't live with the thought of having images (any content really) at the top of their nodes. They must have them anywhere of their pleasing within the contents of the node body
  • You don't feel like running complex regular expressions on your node content when the design changes
  • You know how to code PHP*

*) Contentbrowser will work without you knowing PHP. However you will not be able to customize the templates.

Bot autokick

Automatically kick a person out of IRC if they do something pre-configured.

Currently supports whitelisting irc nicks and kicking people who say blacklisted words.

Pages

Subscribe with RSS Subscribe to RSS - Actively maintained