johnmmackey

This WordPress plugin is designed to be used when WP is deployed as a Headless CMS.
Using <a href="https://www.advancedcustomfields.com" rel="nofollow ugc">Advanced Custom Fields</a> provides fine-grained control for content modeling; 
this plugin disables the default ‘content’ field as well as excerpts, trackbacks, comments and other unneeded fields from 
the default page edit view.

Headless Pages

Disable the default Wordpress page editor when using custom fields.

Benjamin Intal

gambitph

Using WordPress entirely as a CMS (a <a href="https://medium.com/@jchiatt/headless-wordpress-with-react-d573bca02ee0" rel="nofollow ugc">Headless WordPress</a>) is a plausible option for people building web apps using technologies such as React JS or Angular JS to entirely build their front-end.
Doing this, the front-end (e.g. built with React) becomes decoupled from the back-end (e.g. WordPress). Since WordPress is being used strictly to manage and serve the content via REST API, the WP front-end becomes unusable and unnecessary – hence the term “headless WordPress”.
This plugin essentially removes the front-end of WordPress.
<blockquote>
Note that the REST API, and other non-front-end stuff should work as normal.
</blockquote>
<h4>Features</h4>
<ul>
<li>No settings page</li>
<li>Allows backend access</li>
<li>Allows REST API endpoints</li>
<li>Redirects (403 Forbidden) all front-end pages to the login page</li>
</ul>

Redirect Front-end to Login | Headless WP

Redirects all front-end pages to the login page, best for building a headless WP REST API backend

Headless Pages vs Redirect Front-end to Login | Headless WP