Developer

Experiments with extending styleguide.module in a few ways.

* Re-vamp the theme presentation of the styleguide page itself - to better separate the design components visually
* Look at introducing some nice layout/UI conventions (nicer table of contents, view-source) as seen in other styleguide tools like patternlabs

Not intended for full project release, just some experiments that may become patches back into the styleguide project.

English

Module amoCRM API is designed for developers. Install it only if you want to use dependent modules. The module provides amoCRM interaction interface with the help of simple functions and allows to extend the capabilities of integration.

For example, you can get a list of leads using filters or create new fields by any condition with the help of module. See the full list of features here: https://developers.amocrm.com/rest_api/

The Registration Code module is a rest resource that allows anonymous users to request for a code before create
a new account. The code will be received by email and you need to insert this code when creating the new user account using this resource https://www.drupal.org/node/2291055.

This is useful when you want to prevent fake registrations from a headless or native app and you don't want to use the link that redirects to the website.

Here is an example for the code request using json as format:

An API that allows the storage of AppXtender credentials in the database, and contains various utility functions for reading metadata and POSTing files.

This module allows post processing of render arrays just after them
being retrieved from cache. It allows you to apply small per-user modifications
on globally cached output, without having to resort to per-user caching.

Think of it as a poor man's ESI, or the same thing than #post_render callbacks,
except they will run at drupal_process_attached() time at initial rendering
and after drupal_render_cache_get().

* The Variable editor module provides a UI for editing, editing or deleting any
global variable.
* There is a one click submit for saving array as well as any other variable
type. There is a ctool popup that helps to add new variables
* The project provides root user to edit all kind of variables. Other users can
define their own variable and edit them.

Issue Page

Data spider.

This is a development tool that integrates the Emmet plugin for textareas into a Drupal development site. This module allows the Emmet Toolkit that you may already be using to be accessed in a web browser.
This is not currently intended to be used in a production environment, but is a development tool for speeding up the placement of HTML within Drupal text area fields.

Under Construction