Path Documentation

Component type

module

Categories

Maintenance status

Development status

Component created

Component changed

All too often, as Drupal developers and site builders, we toil away building the perfect site, only to hand it over to a client who struggles to understand how to utilize our great system. Often we pair our site delivery, with some form of documentation, Microsoft Word, maybe a pdf. Of course the client gets lost trying to toggle between a static page of documentation, and a dynamic, fluid content management system.

Inline Manual

Component type

module

Maintenance status

Development status

Downloads

5440

Component created

Component changed

Inline manual is an online tool, making it easy for everyone to create, update and re-use documentation as well as create product/site tours. Documentation is interactive (step by step guides) that can be played and used by any web site/ web application.

The Drupal module allows to fetch data from InlineManual.com and store them locally. The data can be played using the player afterwards.

Requirements

No need to have jQuery Update anymore, player works without jQuery

Versions API

Component type

module

Maintenance status

Development status

Component created

Component changed

Don't you hate it to manually check every drupal site you maintain for updates. Of course there are these update notification mails, but they only tell you, that you should check for updates on a single site. Wouldn't it be great to have a control center where you can check & download the updates for all of your sites at once.

Toolkit

Component type

module

Maintenance status

Development status

Component created

Component changed

This modules provides an api and set of tools for creating flexible content types, taxonomy terms, and their respective fields and field groups. Although the base functionality is similar to what is offered by Features, these tools are entirely maintained in simple to create/edit/update yaml files with only as much information as is needed; there is no need to alter fields or content types in the UI and then recompile; just alter or add a setting in the code, rebuild the content type or taxonomy vocabulary, and you're done.