David Matthew

<p>Guillotheme chops the front-end (i.e. the head) right off your theme by restricting access to the front-end (specifically, the WordPress-generated front-end permalinks). These are unnecessary in the case of a headless or decoupled set-up, and could potentially confuse non-technical users or other content editors when WordPress is being used headlessly (i.e. purely for its CMS capabilities).</p>
<h3>Features</h3>
<ul>
<li>Designed to complement a headless setup.</li>
<li>Activate the plugin to automatically prevent access to WordPress-generated front-end permalinks.</li>
<li>For logged-in users, redirect back to the source page if the front-end is accessed (e.g. a post preview link within the editor will redirect back to the editor).</li>
<li>Non-logged in users are redirected to the login page.</li>
<li>Optionally use your own custom url for the redirect destination for both logged-in and logged-out users.</li>
</ul>
<h3>Development</h3>
<ul>
<li>Namespaced and object-oriented code.</li>
<li>Adheres to <a href="https://github.com/WordPress/WordPress-Coding-Standards" rel="nofollow ugc">WordPress Coding Standards</a>.</li>
</ul>


Guillotheme

Guillotheme chops the front-end (i.e. the head) right off your theme by restricting access to the front-end (specifically, the WordPress-generated fro …

Headless eCommerce API for Developers – CoCart vs Guillotheme