jarednova

Simple ways to make admin customizations for WordPress. You know all that brain space you saved for <a href="http://wptavern.com/learn-three-wordpress-filters-a-day" rel="nofollow ugc">memorizing hooks</a>? Use it for something better. For example, you can…
<ul>
<li>On <a href="https://github.com/upstatement/jigsaw" rel="nofollow ugc">GitHub</a></li>
</ul>
<h3>Support</h3>
Please use the <a href="https://github.com/upstatement/jigsaw/issues?state=open" rel="nofollow ugc">GitHub repo</a> to file bugs or questions.

Jigsaw

An easy way to add (code) columns to the WordPress backend. You can even add sorting on meta keys.

Love it

Simple ways to customize your WordPress build.

Brad Parbs

Any <code>WPENV_</code> prefixed variables in the <code>.env</code> will be used to override the WordPress options. For example, if you’d like to set a specific environment to “Discourage search engines from indexing this site”, you can add <code>WPENV_BLOG_PUBLIC=0</code> to your <code>.env</code> file.
<ul>
<li>
Any option in the <code>wp_options</code> table or retrieved by <code>get_option()</code> can be set this way.
</li>
<li>
You can define keys either as <code>WPENV_BLOGDESCRIPTION</code> or as <code>WPENV_blogdescription</code>, both will work.
</li>
<li>
If you’d like to define the location of your <code>.env</code> file, rather than the plugin looking for it, you can filter <code>dotenv_location</code> to be a directory path.
</li>
<li>
You can also change the <code>WPENV_</code> prefix by filtering <code>dotev_key_prefix</code> to be a different prefix.
</li>
</ul>

dotenv

A WordPress plugin to set WordPress options from a .env file.

Jigsaw vs dotenv