Normal convention for Jenkins plugins which contribute a JobProperty to a jobs configuration page is to use an optionalBlock as the top level jelly tag. This is presented to the user as a checkbox, allowing users to hide configuration from plugins they are not using which helps keep a jobs configuration page clean.

The delivery-pipeline-plugin breaks this convention by using a section as it's top level jelly tag, which presents itself as a new header section.
The biggest problem with this is, the delivery-pipeline-plugin seems to get rendered in the middle of all the other jobs properties therefore breaking up the page and making the jobs configuration look messy.

I feel the delivery-pipeline-plugin would look feel/look better if it used the conventional optionalBlock.