zbigiman

What this plugin does:
<ul>
<li>Adds independent of Appearance Menu Editor to WordPress Admin Panel</li>
<li>Adds menus to WP REST API v2.</li>
<li>Adds menus API viewer to WordPress Admin Panel</li>
</ul>
WP Headless Menu Editor REST API endpoints:
<ul>
<li>/wp-json/hme/v1/menus/</li>
<li>/wp-json/hme/v1/menus/{id}</li>
</ul>

WP Headless Menu Editor

Menu editor for headless WordPress  - independent of Appearance. Adds menus to WP REST API v2.

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

WP Headless Menu Editor vs Redirect Front-end to Login | Headless WP