Extension of the built-in Number field with a default value of null.

Ever have a client put 4 MB PNG files in their Redactor fields, failing to apply any of your meticulously crafted image transforms? Writers consistently using the <strong> tag for headers? Have you ever needed to implement lazy loading of images embedded in WYSIWYG content, responsive images or wanted to remove pesky inline styles without breaking a sweat? This is for you.

Retcon is a small Craft CMS plugin offering a series of easy-to-use Twig filters for manipulating HTML content.

CP Field Links is a tiny utility plugin making content modelling a little bit easier in Craft.

Did you forget a field handle? Mouse over the cogwheel next to the field title, and CP Field Links will tell you.

Need to adjust some field settings? Click the cogwheel; CP Field Links will redirect you to the relevant field's settings page – and back to the content when you're done.

Additionally, CP Field Links will add a link in your element edit forms to manage source settings (e.g. entry type, category group) in the same manner.

This plugin adds the following fieldtypes:

Checkboxes (dynamic)
Dropdown (dynamic)
Multi-select (dynamic)
Radio Buttons (dynamic)

You can populate the options for each fieldtype using JSON.

Field type that parses twig when an element is saved.

certainlyakey starred timkelty/craft-elementoptions

certainlyakey starred miranj/craft-router

certainlyakey starred mmikkel/CpSortableCustomColumns-Craft

certainlyakey starred benjamminf/craft-relabel

certainlyakey starred elivz/VzUrl-Craft

certainlyakey starred Pennebaker/craftcms-thearchitect

certainlyakey starred thomasthesecond/EntryInstructions

certainlyakey starred niceandserious/crafty-vagrant

Twig doesn’t refer to a key, value array as an array. It calls it a hash.

Anyway, this post isn't about how awesome Craft is (which it is), it's about a piece of auspiciously missing documents: how to create your own Twig filter inside of craft!

A Field Type plugin for CraftCMS that allows the management of relationships from both sides

SuperSort provides a Twig filter sorting an array of objects, either using one of PHP's built-in methods to sort the actual objects, or using a custom sort method to arrange the array based on the rendered results of running each object through a Twig object template.

Using SuperSort's custom "sort as" methods, you can sort an array of elements by any accessible object value — including values from Matrix blocks, related elements, math calculations, etc.

Why Twig documentation recommends to use extending rather than including? Symfony 2 documentation says because "In Symfony2, we like to think about this problem differently: a template can be decorated by another one." but nothing more. It's just author's whim or something more? Thanks for help.