Actively maintained

Signer module is an Electronic Signature tool for sign data, files or web forms.

jBart is a jQuery visual toolkit with which you can build rich search boxes, interactive product galleries, interactive data views, rich forms and more.

Imagine that you have a context for the pages under /news/* and you put some blocks for all that pages, but! imagine that you need to add a block specifically for one page(node) in the content region(or wherever).

Context By Node, creates a context for that page when you are creating the node, so after you save you dont need to do anything than just add your block.

So, the only way was doing all these:

[OLD WAY]

1. Create the Node.
2. Get the NID or the URL of that Node.
3. Create a Context that aplies those conditions.
4. Go back to the node view.
5. Edit the Context(inline ui), and add some blocks, etc... for your Node.

[NEW WAY]

1. Create a Node with the option of "Create a Context for this Node" checked. (default content type enabled is Page)
2. Now do the step 5 of the old way. ;)

... but theres more ...

Q: If iI create like 400 nodes and you check to create a context for that node you will be ending with a huge list of contexts?
A: No. The module filter the list in admin/build/context. And that is optionally.

Q: So, if it doesn't appear in the list, how can I edit it?

The consumer module is a framework for querying web services and theming the response.

This module has been adapted from the original Apture for Drupal 6. Currently it only supports the apture bar.