"Defines a field type Block reference which allows the block to be displayed as the content of the field." Alternately, if the bean module is enabled, blocks can be referenced using the entity reference module instead.

This module, in a basic sense, allows the title to be an actual Drupal field. This comes in especially handy when doing translations, as titles are not translatable in core.

This module provides site builders with a way of 'attaching' blocks within the content of any fieldable entity in Drupal. The same block is shown on any entity of that type/bundle.

Maintained by Dave Reid, Earl Miles, Damien McKenna and Derek Wright

Smart Trim implements a new field formatter for textfields (text, text_long, and text_with_summary, if you want to get technical) that improves upon the "Summary or Trimmed" formatter built into Drupal 7

With the Field Conditional State module you can change the state of any supported fields form element depending on the content of other fields. This is done by providing an UI for Drupal's States API. All the changes made to a form by FCS (Field Conditional States) utilize only the States API and therefore are clientside only.

By using the version of Geshi found at https://github.com/easybook/geshi , Sass and Twig syntax highlighting can be added to text fields in Drupal.

Here are some common settings for HTMLawed that can be used as a more lenient 'filtered html' format for trusted editors that need a simple WYSIWYG. This configuration allows images, which can be a security risk. If you don't understand the risk, then leave Drupal's defaults the way they are and perhaps try to work with the Full HTML format or use CSS classes and stylesheets.

The htmLawed module enables the use of the htmLawed(X)HTML filter/purifier with text/input formats.

This module lets you use very fine grained html filtering.

See /docs/common-htmlawed-settings for common settings.

Omega 4.x Demonstration w/Sebastian aka fubhy, by Joel Moore