piftoworks

<p>PFT – Widget Spacing Control adds margin-top / margin-bottom inputs (desktop and mobile, separately) to every widget’s settings form. Negative values are supported, so you can both expand and tighten the space between widgets without adding empty spacer widgets.</p>
<h4>Features</h4>
<ul>
<li>Per-widget top and bottom margin (px) for desktop and mobile</li>
<li>Negative values supported (e.g. <code>-10</code> to tighten the gap)</li>
<li>Empty value falls back to the theme default</li>
<li>No settings page — inputs appear directly inside each widget’s form</li>
<li>Works with any theme (sidebar / widget area)</li>
<li>No external CSS file. No JavaScript. Single PHP file</li>
<li>No tracking. No external requests</li>
</ul>
<h4>How priority is guaranteed</h4>
<p>To make sure your margin settings always win over theme and other plugin CSS:</p>
<ol>
<li>A triple-ID selector (<code>#id#id#id</code>) raises specificity to 0-3-0-0, beating typical theme selectors.</li>
<li><code>!important</code> is added on every declaration as a second line of defense.</li>
<li>Styles are output via <code>wp_footer</code> at priority 9999, so they load after all other styles.</li>
</ol>
<p>Media queries are used to switch between desktop and mobile values cleanly (inline styles are intentionally avoided because inline <code>!important</code> would override <code>@media</code> rules).</p>
<h4>Responsive breakpoints</h4>
<ul>
<li>Desktop: 769px and above</li>
<li>Mobile: 768px and below</li>
</ul>
<h3>Privacy</h3>
<p>This plugin does not collect, store, or transmit any personal data. It only stores numeric margin values inside each widget’s settings.</p>


PFT – Widget Spacing Control

Set per-widget top and bottom margins separately for desktop and mobile. Supports negative values.

MarcusPope

<p>The current admin WYSIWYG editor will expand to the size of your monitor.  On modern monitors that can be very wide and as a result your content will stretch out beyond the normal bounds.  The current solution is to minimize your window until the editor is about the right size.  But depending on the width of other elements and sections this can create an unusable workspace in the admin section.</p>
<p>This plugin adds the ability to enforce a maximum page width in the WYSIWYG editor for a more realistic content window that matches your blog/site layout. Widths, in pixels, are configurable per each custom post type that supports an editor. So you can define a max width for blog posts, pages, content molecules (see: https://wordpress.org/extend/plugins/content-molecules/) along with any other registered custom post type from any other plugin. Or you can leave them blank to have a full width editor in the admin interface.</p>
<p>This gives you or your content creators a realistic view of how the text will wrap on the front end of your website. This improves the readability of your content by ensuring your paragraphs are not giant blocks of text.</p>
<p>This plugin will only affect the WYSIWYG Visual Tab. Your HTML source code will always use the full available screen real estate. It also uses proper CSS inclusion for page width styles for plugins that enable multiple stylesheet joining and compression meaning your server won’t make another costly request just for this resource.</p>
<h3>Arbitrary section</h3>


Customized WYSIWYG Editor Page Widths

Enforces a maximum page width per post type in the WYSIWYG Visual editor so content will wrap according to the design of the front end.

PFT – Widget Spacing Control vs Customized WYSIWYG Editor Page Widths