Elementor

<p>Sticklight Connector provides a structured way to use the WordPress user system in external or React-based applications.</p>
<p>The plugin extends the WordPress REST API with additional endpoints that allow authenticated clients to retrieve user context and interact with WordPress data, while fully respecting core authentication methods, roles, and capability checks.</p>
<p>Sticklight does not replace WordPress authentication. It relies on <code>wp_authenticate</code> for credential validation and WordPress Application Passwords for API access, and follows standard permission checks (<code>current_user_can</code>) for all requests.</p>
<h4>Typical use cases</h4>
<ul>
<li>React applications connected to a WordPress site</li>
<li>Headless or hybrid WordPress setups</li>
<li>Admin or user dashboards built outside wp-admin</li>
<li>External tools that require authenticated access to WordPress data</li>
</ul>
<h4>Features</h4>
<ul>
<li>Authenticates via <code>wp_authenticate</code> and issues Application Passwords for API access</li>
<li>Adds REST endpoints for login, logout, and retrieving current user context</li>
<li>Enforces WordPress capability checks on all requests</li>
<li>Supports cross-origin headless setups</li>
<li>Extensible via WordPress hooks and filters</li>
</ul>
<h3>Usage</h3>
<h4>Login</h4>
<p>Authenticate with username (or email) and password:</p>
<pre><code>POST /wp-json/sticklight/v1/auth/login
</code></pre>
<p>On success the response includes an Application Password for subsequent API requests and the authenticated user:</p>
<pre><code>{
  "app_password": "XXXX XXXX XXXX XXXX XXXX XXXX",
  "user": {
    "user_id": 1,
    "username": "admin",
    "display_name": "Admin",
    "email": "admin@example.com",
    "roles": ["administrator"]
  }
}
</code></pre>
<p>Use the returned <code>app_password</code> with HTTP Basic Authentication for all further requests.</p>
<h4>Current user</h4>
<p>Retrieve the current authenticated user:</p>
<pre><code>GET /wp-json/sticklight/v1/auth/me
</code></pre>
<h4>Logout</h4>
<p>Revoke the current Application Password session:</p>
<pre><code>POST /wp-json/sticklight/v1/auth/logout
</code></pre>
<h4>User registration</h4>
<p>User creation is handled through the built-in WordPress REST API (<code>POST /wp-json/wp/v2/users</code>) and requires administrator authentication.</p>
<h4>Accessing protected data</h4>
<p>Requests to any endpoint must pass standard WordPress permission checks. Sticklight does not bypass or override these checks.</p>
<h3>Security</h3>
<p>Sticklight follows WordPress security practices:</p>
<ul>
<li>Authenticates via <code>wp_authenticate</code>, which respects all security plugin hooks (rate limiting, two-factor authentication, brute-force protection)</li>
<li>Issues Application Passwords scoped to individual sessions</li>
<li>Does not provide user registration — accounts must be created by an administrator</li>
<li>Applies capability checks (<code>current_user_can</code>) on all endpoints</li>
<li>Does not expose private data without proper permissions</li>
</ul>
<p>For external applications, it is recommended to:</p>
<ul>
<li>Use HTTPS</li>
<li>Restrict allowed origins</li>
<li>Avoid exposing sensitive endpoints unnecessarily</li>
</ul>


Sticklight

Use WordPress authentication and permissions in external React applications via secure REST API endpoints.

timothyolu

<p><strong>Overedge Connector</strong> is the bridge between your WordPress content and your React frontend.</p>
<p>Whether you built your site with Lovable, Vite, Next.js, or plain React — Overedge Connector turns your WordPress installation into a fully configured headless CMS that your React app can fetch from instantly.</p>
<h4>External Services</h4>
<p>This plugin optionally connects to the Overedge platform (https://overedge.dev) to automate the connection setup between your React frontend and WordPress. This connection is initiated manually by the site administrator and can be used without the platform entirely.</p>
<p>The Overedge platform stores only site URLs and plugin health status. No content or personal data is transmitted.</p>
<p>Privacy policy: https://overedge.dev/privacy<br />
Terms of service: https://overedge.dev</p>
<h4>What It Does</h4>
<p>Once activated, Overedge Connector automatically:</p>
<ul>
<li>Registers <strong>custom post types</strong> — Testimonials, Team Members, and FAQs — all exposed via the REST API</li>
<li>Configures <strong>Advanced Custom Fields</strong> field groups for each post type</li>
<li>Enables and configures the <strong>WordPress REST API</strong> for headless use</li>
<li>Handles <strong>CORS headers</strong> so your React frontend can fetch content cross-origin</li>
<li>Creates a <strong>site-wide options panel</strong> for managing global settings (hero text, stats, CTAs, contact details)</li>
<li>Exposes a <strong>health endpoint</strong> at <code>/wp-json/overedge/v1/health</code> so your frontend can monitor the connection</li>
<li>Generates a <strong>secret key</strong> for secure webhook verification</li>
</ul>
<h4>Who Is It For?</h4>
<ul>
<li><strong>Vibe coders</strong> building client sites on Lovable who need their clients to manage content independently</li>
<li><strong>Freelance developers</strong> tired of rewriting WordPress REST API integrations on every project</li>
<li><strong>Agencies</strong> delivering consistent, client-friendly handovers at scale</li>
</ul>
<h4>Works With Any React Frontend</h4>
<ul>
<li>Lovable subdomain (e.g. yoursite.lovable.app)</li>
<li>Custom domain (e.g. yoursite.com)</li>
<li>Next.js, Vite, Create React App — anything React</li>
</ul>
<h4>Works With Any WordPress Setup</h4>
<ul>
<li>Subdomain (e.g. cms.yoursite.com)</li>
<li>Main domain (e.g. yoursite.com)</li>
<li>Subfolder (e.g. yoursite.com/cms)</li>
<li>Shared hosting, VPS, managed WordPress — all supported</li>
</ul>
<h4>Overedge Platform</h4>
<p>This plugin works standalone, but connects seamlessly with the <strong>Overedge platform</strong> (overedge.dev) which provides:</p>
<ul>
<li>Browser-based connection wizard — no terminal, no VS Code</li>
<li>Auto-generated React integration files (wordpress.ts, useWordPress.ts, cmsData.ts)</li>
<li>Dashboard to manage all connected sites</li>
<li>Health monitoring across all your client sites</li>
<li>Phase 2: Visual customisation — clients control colours, layout, and components from wp-admin</li>
<li>Phase 2: Shortcode <span aria-hidden="true" class="wp-exclude-emoji">→</span> React props mapping — <code>[overedge_hero headline="..."]</code> updates your React component automatically</li>
</ul>
<h4>REST API Endpoints Added</h4>
<ul>
<li><code>GET /wp-json/overedge/v1/health</code> — Plugin health and site status</li>
<li><code>POST /wp-json/overedge/v1/configure</code> — Update CORS allowed origin</li>
<li><code>GET /wp-json/overedge/v1/settings</code> — Site-wide CMS settings</li>
</ul>
<h4>Custom Post Types Registered</h4>
<ul>
<li><code>overedge_testimonial</code> — with fields: quote, author_name, author_country, destination, avatar</li>
<li><code>overedge_team_member</code> — with fields: full_name, job_title, bio, photo, destination_focus, linkedin_url</li>
<li><code>overedge_faqs</code> — with fields: answer, destination, order</li>
</ul>
<p>All custom post types are exposed via the WordPress REST API and include ACF field support.</p>
<h4>Privacy</h4>
<p>This plugin does not collect or transmit any personal data. The optional Overedge platform connection only stores site URLs and connection status — never content or user data.</p>


Overedge Connector

Connect your WordPress site to any React or Lovable-built frontend as a headless CMS — in minutes.

Sticklight vs Overedge Connector