Member area

Registration, email confirmation, sign-in, and members-only content — the platform's per-tenant auth, surfaced by one widget. Accounts created here belong to the blueprint tenant only; every tenant has its own isolated member base.

Live demo — sign in or create an account

Live demo — gated content

🔒 You are signed out. The members-only block is hidden — sign in above and it appears without a page reload.

🎉 Members-only content. You can see this because you are signed in. Sign out and it vanishes.

1 · Once per site

<script async src="https://api.mypixelforge.io/embed/v1/mpf.js" data-site="blueprint-site"></script>

2 · The sign-in / register widget

<div data-mpf="auth"></div>

3 · Gate any markup

<div data-mpf-gate>
  Visible to signed-in members only.
</div>

<div data-mpf-gate="guest">
  Visible to signed-out visitors only.
</div>

Optional · react to sign-in from your own code

<script>
  window.mpf = window.mpf || function(){(window.mpf.q=window.mpf.q||[]).push(arguments)};
  mpf('on', 'auth:change', function (user) {
    console.log(user ? 'signed in as ' + user.email : 'signed out');
  });
</script>

Gating hides markup; it does not protect it — the HTML still ships to every browser. Anything genuinely private (downloads, account data) must come from an authenticated API call, not sit hidden in the page. The gate is the UX layer; the Bearer-token session is the security layer.