Bankole Emmanuel · Software & blockchain developer

I build software.
And make room
for better ideas.

Hey, I’m Bankole — you can call me Mrbarnk. I’ve been developing software since 2016. Here, I explore practical AI workflows for people who run WordPress blogs.

Bankole Emmanuel, software developer also known as Mrbarnk
THE HUMAN BEHIND THE CODE
BUILDING SINCE 2016CODE × WORDPRESS × AIA LITTLE BLENDER, FOR FUN
01 / The focus

Less repetitive work.
More thoughtful publishing.

A focused space for independent WordPress publishers: turn source material into useful drafts, keep a human in the loop, and understand what happens when an automation breaks.

01 — CONTENT WORKFLOWS

From idea to a draft worth editing.

Research briefs, source checking, clear outlines, and a review step before anything goes live.

Read the draft-first guide ↗
02 — WORDPRESS AUTOMATION

Connect the moving parts.

APIs, publishing queues, post status, images, and the small details that keep a blog running.

Use the publishing checklist ↗
03 — DEVELOPER NOTES

Look under the hood.

Backend decisions, databases, and practical engineering context behind the workflows.

Read the database guide ↗
02 / A little about me

A developer.
A curious person.
Still learning.

I’m Bankole Emmanuel, a software developer since 2016. I’m also a blockchain developer. My background spans WordPress, backend applications, APIs, blockchain systems, and the infrastructure that keeps software running.

I also learned Blender for fun. Building something visual exercises a different part of the same curiosity.

JavaScript / TypeScriptPythonWordPressBackend systemsBlockchainBlender
How I got here

I started developing software in 2016. Along the way, I’ve worked with web applications, microservices, fintech and blockchain projects. My earlier portfolio covered a broad range of tools; this site brings that experience into a more focused conversation about useful software and publishing workflows.

What I like working on

Connecting systems, making repetitive tasks easier, and understanding why something fails. My technical background includes Django, Flask, Express, SQL databases, MongoDB, Redis, Docker, Nginx, and cloud hosting.

Why AI and WordPress?

WordPress gives a publisher a place to own their work. AI can help with the preparation around that work. I’m interested in where those two meet: useful assistance, clear review steps, and systems a person can understand.

Outside the code editor

I explore 3D with Blender for fun. You can also find me on Instagram, X, and LinkedIn — the links below lead to my own profiles.

03 / Selected projects

Some of the work
behind the words.

A few projects I’ve worked on across messaging, commerce, fintech, and connected digital services.

waabot.01
MESSAGING & AUTOMATION

Waabot

A messaging automation platform with WhatsApp APIs and tools for connecting business conversations across channels.

Explore Waabot ↗
waabot.shop02
COMMERCE & STOREFRONTS

Waabot Shop

An online store builder for small businesses, bringing product catalogues, online payments, and order management together.

Explore Waabot Shop ↗
NYXEX03
FINTECH & BLOCKCHAIN

NYXEX

A technology business focused on financial applications, blockchain development, and AI-enabled services.

Explore NYXEX ↗
Morizon Hub04
CONNECTED DIGITAL SERVICES

Morizon Hub

A digital hub connecting an ecosystem of payments, property, entertainment, and community services.

Explore Morizon Hub ↗
04 / Start here

A good AI workflow still has a human in it.

Use this simple outline to think through an AI-assisted WordPress publishing process. Open each step to see where the checks belong.

A workflow outline, not a claim of measured results or a deployed automation.

01 · Start with a real question

Choose one question your reader needs answered. Gather original notes, examples, and trustworthy references before asking AI to help organise the material.

02 · Prepare a draft

Use the brief to shape an outline and draft. Keep source links beside factual claims and mark anything that still needs verification. Save the result as a draft in WordPress.

03 · Review like an editor

Check facts, run the example, inspect links, and add your own explanation. A fluent answer can still be wrong. Only publish once a person has checked the final page.

04 · Keep the workflow accountable

Record what was created, the WordPress post ID, and what failed. Review an existing draft before retrying a failed run so you do not accidentally create duplicates.

05 / Keep in touch

Have something interesting to build?

Tell me about the problem, the people it serves, and what you want to make easier.

Connect on LinkedIn ↗