# About CYBERMAPS

The WordPress experience and design decisions behind CYBERMAPS, from advanced sitemaps to useful AI publishing.

THE PEOPLE AND THE PURPOSE

Built from years of WordPress work. Made for what comes next.

CYBERMAPS started with a feature I wanted and grew into the publishing and discovery system I wanted to use on my own clients’ websites.

## It started with an upgrade I didn’t want to buy

An XML sitemap plugin had a pro feature I wanted. I didn’t want to pay for it. That was the spark.

But once I started, I had a longer list. I wanted better control over what a website publishes. I wanted agents to retrieve useful content. And I wanted a dashboard I could stand to look at every day.

The SEO plugins I’d used kept filling that dashboard with popups, banners, upgrade prompts, and junk. An affront to my sense of aesthetics. I wanted something **slim, clean, and lean**.

> So I sat down and cooked. CYBERMAPS is what came out.

## Useful AI support, with substance behind it

I wanted real LLM agent support. Too many of the integrations I encountered offered stubs that satisfied a scanner without giving an agent much useful content to retrieve.

My goal was to connect the pieces: eligible content, readable publications, structured business information, and tools that inspect the actual public response. A site should be able to explain what it offers to a visitor arriving through search or an agent working for a human.

The same principle shapes the interface. Clear controls, useful evidence, and room to work. A WordPress dashboard should help you run the site.

## Why WordPress 7.1?

Starting fresh gave me room to build around the platform I want to develop on. **CYBERMAPS requires WordPress 7.1 and PHP 8.2 or later.** I chose those minimums so I could build on the newer platform features.

The plugin uses WordPress 7.1’s public ability metadata filtering to find abilities it can expose to external clients. In the code, that means calling `wp_get_abilities()` with `meta.public`. CYBERMAPS then shares its native Ability kernel across MCP, WebMCP, API Catalog, OpenAPI, and ARD discovery.

The practical benefit is consistency: capability definitions feed several interfaces from one foundation. The plugin also uses WordPress-owned global routing for its well-known discovery endpoints.

I don’t want to carry a growing compatibility layer just to recreate that foundation on older installations. I want to spend that time improving the plugin. If you like building on the leading edge of WordPress, that is the direction of this project.

## Built from years of WordPress work

I’m **Aleksandr Oreshkin**, a web developer representing [CYBER BRAND](https://cyberbrand.net/). I’ve built hundreds of WordPress websites since 2009.

I built CYBERMAPS around what I’ve learned working on those sites. I want it to save you time, help you spot useful improvements, and make your content easier for people and agents to understand.

And this is my cat **Nuski**. He helped a lot. I couldn’t introduce the project without him.

[![Aleksandr Oreshkin outdoors in a snow-covered helmet](/images/blog/aleksandr-thumb.webp)View photo ↗](https://cybermaps.dev/images/blog/aleksandr-oreshkin.jpg)

**Aleksandr Oreshkin**Developer · CYBER BRAND

[![Nuski standing on a branch among spring blossoms](/images/blog/nuski-thumb.webp)View photo ↗](https://cybermaps.dev/images/blog/nuski.jpg)

**Nuski**Cat · Much appreciated help

## Put it to work

The open beta is available now. Explore what is included, try it with your content, and help shape the next release.

[See what you can try in the open beta →](https://cybermaps.dev/blog/open-beta/)