apiary
Component type
Categories
Maintenance status
Development status
Component created
Component changed
API module for the site's content and custom module db tables.
API module for the site's content and custom module db tables.
Adds the save/submit form button on top of the page for node edit / node add / any page you want.
IT uses jquery to duplicate it.
This is a very important and needed Usability Enhancement to drupal.
Sponsored by : rsvelko2
Events as fieldable entities, or eventities as I like to call them. The module's name is actually Event, and I plan on eventually submitting this as a patch for a Drupal 7.x version of Event, but since it's fundamentally different, and the issue queue for Event is the scariest thing I have ever seen, it lives here for now, until it can be feature-matched/completed to the old event.
Content Access via a URL API.
This module allows you to bypass the default data storage location for fields and entities and instead load the data from a web service.
This is useful when your primary data source is in another system but you want to display/use this data in your Drupal site without the hassle of syncing or importing data.
Stores information about your web services. This information is used to allow Drupal to make the appropriate CRUD operations on requested data.
This module defines a new field type Spotify Play Button, allowing you to embed spotify tracks.
See https://developer.spotify.com/technologies/spotify-play-button/ for more info on the play button.
Module developed for richseam.com
This module provides a contenteditable form element.
Display suite add on to output taxonomy terms with all parents, for each taxonomy field you'll find a new field called "Term with parents: vocabulary".
Supported options:
A Simple module with will render US State Map via Fonts and CSS.
This module allows the content for a site to be kept in a separate staging repository. This will typically be a Subversion or Git repository where the content has been committed and is being maintained.
The module checks out the content directly into the nodes of the site from whatever branch of the repository it is associated with. It is possible to have multiple sites associated with different branches so that future or experimental versions of content can be previewed and tested before being committed to live.