Skip to content
February 15, 2026

SociaBlend Development Recap

Timeframe: ~Last 2 Weeks
Project Area: Account Linking + Public Landing + Trending + Creator Foundation


1️⃣ AdSense Integration (Initial Phase)

What We Implemented

  • Loaded AdSense script once via WordPress enqueue (sb-adsense)
  • Injected <ins class="adsbygoogle"> blocks into:
    • Sidebar (public shell)
    • Feed (in-feed ad card format)
  • Added logic to:
    • Avoid double rendering
    • Trigger adsbygoogle.push() after DOM insertion
  • Confirmed ad elements rendering via console inspection

What We Discovered

  • Google flagged: “Google-served ads on screens without publisher content”

What We Did to Address It

  • Built Public Landing Page
  • Added:
    • Trending content
    • Sociablend Updates
    • Sidebar trending
    • Sidebar ad card
  • Removed login-only redirect for public landing
  • Ensured real content exists alongside ads

Status:
AdSense partially integrated. Will revisit after more content depth is added.


2️⃣ Public Landing Page Architecture

Created:

  • Public Landing template
  • Trending panel
  • Updates panel
  • Panel swap animation
  • Sidebar trending mini-feed
  • Sidebar AdSense card
  • Mobile compatibility

Implemented:

  • REST endpoint: /load-trending
  • REST endpoint: /load-updates
  • Inline JS swap system
  • Rotation of trending posts (1 post per cycle)
  • Automatic page cycling

Current Behavior:

  • Trending rotates every X seconds
  • Updates load via REST
  • Sidebar displays trending card + ad
  • Navbar simplified for public users

Status:
Working and stable.


3️⃣ Header Refactor (Shell Separation)

We split shell behavior into:

A) App Shell (Logged In + Verified)

  • Full navbar
  • Sidebar
  • Notifications
  • Messages
  • User menu
  • User dashboard behavior

B) Public Shell (Landing + Trending)

  • Minimal navbar (Sign In / Create Account)
  • Sidebar:
    • Trending card
    • Advertisement card
  • No personal dashboard elements

Result:
Clean separation between:

  • Public marketing mode
  • Logged-in app mode

4️⃣ Trending System Refactor

Changes:

  • Converted trending to REST-based endpoint
  • Allowed:
    • Single post rotation mode
    • Page-based pagination fallback
  • Disabled “Load More” on landing (rotation-only mode)

Status:
Working correctly.


5️⃣ Registration Page Review & Refactor

Improvements:

  • Cleaned password validation
  • Added canonical account type support
  • Introduced: sb_account_type
  • Preserved backward compatibility:
    • user_type_person
    • user_type_business
    • user_type_influencer

Current Flow:

  1. User registers
  2. Role = editor
  3. Redirect → /profile-completion/

6️⃣ Login Page Refactor

Fixed:

  • Empty redirect edge cases
  • Added nonce protection
  • Added account-type-aware routing
  • Removed inline AdSense (policy-safe)
  • Added fallback redirect safety

Logic Now:

  1. Login
  2. If profile not complete → profile-completion
  3. If complete:
    • personal → user_redirect_page
    • business/influencer → temporary fallback (trending)

Status:
Stable, secure, forward-compatible.


7️⃣ Profile Completion Refactor

Added:

  • Nonce protection
  • Account-type branching
  • Creator placeholder logic
  • Secure folder creation
  • Avatar handling
  • Tag assignment
  • Verification code system

Critical New Behavior:

After profile completion:

If:

sb_account_type = personal

→ Create personal dashboard page via:

sociablend_ensure_user_page_setup()

If:

sb_account_type = business OR influencer

→ Mark:

sb_creator_needs_setup = 1

→ Temporary redirect = trending

This sets the stage for creator-specific dashboards.


8️⃣ Public Content + Google Policy Compliance Strategy

We:

  • Stopped redirecting entire site to login
  • Created real public content
  • Added updates feed
  • Added trending content
  • Added sidebar content
  • Reduced login-wall footprint

This improves:

  • AdSense approval likelihood
  • Crawlability
  • SEO footprint
  • Business presentation

9️⃣ Where We Left Off

We are at the Creator Expansion Architecture Stage.

We have:

  • Account type stored
  • Login routing aware of account type
  • Profile completion branching by account type
  • Placeholder flag for creator setup

🔟 Next Step (Critical)

We now need to build:

Creator System Foundation

1️⃣ Create Custom Post Type:

sb_creator

For:

  • Businesses
  • Influencers

2️⃣ On profile completion (business/influencer):

Automatically:

  • Create sb_creator post
  • Assign post_author = user_id
  • Store creator meta
  • Generate slug
  • Set:
user_redirect_page = creator-dashboard-slug

3️⃣ Build:

  • Creator Dashboard Template
  • Creator Content Manager
  • Creator Profile Public View
  • Linking personal ↔ creator accounts

🚀 Strategic Direction Forward

We are transitioning from:

User Feed Platform

→ To:

Multi-Account Social Infrastructure

  • Personal accounts
  • Business accounts
  • Influencer accounts
  • Cross-linking between them
  • Content-first creator dashboards

📌 Official Current Status

Public Landing: ✔
Trending REST: ✔
Updates REST: ✔
AdSense (partial): ✔
Registration flow refactored: ✔
Login flow secured: ✔
Profile completion branching: ✔
Creator foundation: 🚧 (next build phase)


🔜 Next Step

I recommend we now:

  1. Build register_post_type('sb_creator')
  2. Auto-create creator profile for business/influencer
  3. Generate creator dashboard template
  4. Wire redirect to creator dashboard

Subscribe to get the latest tech updates!

We don’t spam! Read our privacy policy for more info.

Comments are closed.