Under active development

Floats tasks and actions (e.g. the view and edit tabs on nodes), to avoid the need to accomodate them when building a theme.

This module is the extended version of the Node import module that has the following extra functionalities that are not support by

My first Drupal 7 module.

Broken

Note: recent big changes to the Ledger module have broken this module.

This module provides a convenient API to create sub-pages for entity urls.
E.g. node/%/about, or taxonomy/term/%/related.

Sub-page definitions can be specific to an entity bundle or any other subset of entities.
Different modules can independently define sub-pages on the same route, e.g. node/%/about, each with their own logic for page title, access check, tab and navigation settings, and page delivery.

This is a proof-of-concept module for a pattern to replace some overly verbose info hooks for a better DX, and a better ratio of verbosity vs expressiveness/readability.

The module wraps around 3 well-known info hooks, to provide an alternative API based on the "InjectedAPI" pattern.

With injapi, hook implementations should be
- less verbose
- less boilerplate
- more semantic
- more informative to read
- more pleasant to work with overall.

Results:
- hook_image_default_styles(): Awesome!
- hook_schema(): Nice.
- hook_menu(): Debatable.

Explanation: hook_menu() already has a pretty good information density, while hook_image_default_styles() has not. hook_schema() is somewhere in the middle.

Why should I install this?

If you intend to manage your image styles in code instead of the database, then hook_injapi_image_default_styles() is enough reason to install this module.

All the rest (menu and schema) can be seen as case studies, which you are free to use or not. At least, they won't be in the way.