With the Ctools Field module, any Ctools content can be attached to a field. The goal was to find a nice and simple way for editors to place custom code and views on the node detail page.
Luckily, the field isn't limited, so you can place any content you could place with Panels.
This is an example Feature that supplies a Polymer element. It supplies a custom Multifield, a field_formatter and template, and code to automatically download its upstream Web Component, <flip-card>
Here's the sample markup output by the template:
This module provides a simple field that can be used as a simple quiz or multiple choice questions. It provides a field with a textfield and a checkbox / radio selection combined. If added to any entity (node/content type, user, taxonomy term, ...) the editor of the entity can enter multiple answers in the textfields and determine which answers are correct.
This module is for everybody who does not want to use the whole complex system of the quiz module, but just a simple field for multiple choice questions.
What we are trying to build here is a fairly common design pattern that allows users to preview the metadata for a link before submitting it to their feed. If you have used Facebook, Google+, Yammer or any number of services you have seen this before.
The GeoNames Hierarchical Select module provides a field for selecting administrative divisions from geonames.org.
It uses the children web service to populate a series of select lists.
Users can select region, country, state/province, county, etc.
There are many field and display settings for fine-grain control.
Field Settings:
This module allows the site administrator fine-grained control over when a node's changed timestamp gets updated. A whitelist can be configured per content type, in which the administrator can specify which properties and Field API fields should cause the node to update its timestamp.
Progressbar based on the core field modules of Drupal
This module adds a widget and display formatter to the basic "integer" field to edit and display it as a decimal field. It is generally considered a best practice to store ecommerce prices as integers in the lowest denomination such as cents. This avoids a whole class of rounding and other calculation errors.
There are other modules for Drupal that support "price" fields, but they all have a limitation that makes them unsuitable for many use cases:
Unfeaturized Fields allows other modules to define fields (like Features), but still edit them and then maybe featurize them.
Contrib shouldn't featurize fields, because it doesn't know the site well enough: field labels, weights, other fields, field groups etc are unknown. A contrib module can however require fields necessary for its function. This module allows such fake feature fields. It will force creation and existence, but not check state or content. Featurizing is up to the site.
This module provides a hidden UNIX Timestamp field for Webform.
It may be usefull for tracking submissions with a mosly unique ID.
