Venturit works together with Alfa Jango and Nick Gorton (Co-founder, Carcode.me) at all stages of the design and development of carcode.me application. Venturit team helped to turn the business idea into a fully operational application in 2 months and continues to enhance the application using agile development process, applying design patterns and best practices to architecture a scalable enterprise application, and to develop a deployment and a hosting strategy that supports exponential growth over a short period of time.

Download From WordPress Plugins Site

It uses short code, hence it is very simple to use, Just include this short code with your address, desired width and height of the map. [gmap a=”505 East Michigan Avenue,Lansing, MI 48912-1148″ w=”400″ h=”400″].
a = the complete address
h = height
w = width.

Above short code generates the following gmap.

We also set up a demo site here for you to play and see whether it is something that you would like to use in your projects.

Here is some a quick “howto”

1. Install the plugin using:

script/plugin install git://github.com/prabode/acts_as_publishable

2. Run the generator to create the plugin components.

./script/generate publishing

The above step will create the routes, views, controllers and tests.

3. Run the plugin tests using rake

cd RAILS_ROOT/vendor/plugins/acts_as_publishable
rake test

We have 34 tests and 104 assertions to cover all the functionality of the plugin.

4. Include acts_as_publishable in your model
Here is an example from our demo app:
class Document < ActiveRecord::Base
acts_as_publishable :status_column => "stage", :required_fields_for_publishing => ["name", "description"]
end

5. Optionally integrate i18n
Here is an example again from our demo app.
en.yml
en:
publishable:
document_name: "Name is required for publishing."
document_description: "Description is required for publishing."

6. Include “publishing_status_tag” tag in your views where you need the status and controls to appear.
Here is an example again from our demo app.

documents/show.html.erb

<%= publishing_actions_tag(@document)%>

Published At:

<%=h format_time(@document.published_at) %>

Archived At:

<%=h format_time(@document.archived_at) %>

Name:

<%=h @document.name %>

Description:

<%=h @document.description %>

<%= link_to ‘Edit’, edit_document_path(@document) %> |
<%= link_to ‘Back’, documents_path %>


documents/index.html.erb
<h1>Listing documents</h1>
<table border=”0″>
<tbody>
<tr>
<th>Status</th>
<th>Name</th>
<th>Published At</th>
<th>Archived At</th>
</tr>
<% @documents.each do |document| %>
<tr>
<td><%= publishing_status_tag(document, form_authenticity_token)%></td>
<td><%=h document.name %></td>
<td><%=h format_time(document.published_at) %></td>
<td><%=h format_time(document.archived_at) %></td>
<td><%= link_to ‘Show’, document %></td>
<td><%= link_to ‘Edit’, edit_document_path(document) %></td>
</tr>
<% end %>

</tbody></table>
<%= link_to ‘New document’, new_document_path %>

Ok now some pictures to explain the rest of the story:

1. Not Ready, Readiness messages generated by the plugin, click on not ready image to see messages.

2. Ready, if the document is ready, it will show the publish button
During publishing actions, acts_as_publishable will set the status, published_at or archived_at and update your model.

3. Published, if the document is published, it will show the unpublish and archive buttons.

4. Archived, if the document is archived, it will show the reset button to resurrect.

We think we have a pretty good plugin, of course we are biased. Try it out and let us know what you think.