BabyLoveGrowth

BabyLoveGrowth Integration adds a secure REST API endpoint to your WordPress site so BabyLoveGrowth.ai can publish or update posts remotely. It uses an API key you control in WordPress settings, and supports featured images and HTML/Markdown content.
<ul>
<li>Improved Authorization</li>
<li>Endpoints: <code>GET /wp-json/babylovegrowth/v1/ping</code>, <code>POST /wp-json/babylovegrowth/v1/publish</code></li>
<li>Accepts <code>title</code>, <code>slug</code>, <code>content_html</code> or <code>content_markdown</code>, optional <code>metaDescription</code>, <code>heroImageUrl</code>, <code>status</code></li>
<li>Sets/updates posts by slug; supports <code>publish</code>, <code>draft</code>, <code>pending</code></li>
</ul>

BabyLoveGrowth Integration

Secure REST endpoint to publish posts from BabyLoveGrowth.ai backend via API key.

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

BabyLoveGrowth Integration vs Redirect Front-end to Login | Headless WP