What Gillish Core is, and what it does today.

What Core is#

Every Gillish tool, Cairnstone, Node, Feed, Mesh, is its own plugin, installable and useful entirely on its own. Once a site runs more than one of them, there is a second job to do: give the site one place to see the whole toolset and move between the parts. That is Core.

Core is a single common admin surface. It is the home the Gillish menu in WordPress points at, and the page this documentation network is organised around. It does not replace any tool's own dashboard; it sits above them and ties them together.

Its role in the ecosystem#

• It is the hub, not a product. Core is only meaningful on a site that runs two or more Gillish tools. A site with one Gillish plugin has nothing for Core to tie together, so Core stays out of the way. It is never sold or used on its own.
• Menus stay separate by design, Core is the only future exception. Every Gillish tool ships its own top-level admin menu deliberately (Node as Gillish, Cairnstone as Cairnstone, and so on); that separation is intended, not a defect to be unified away. The only thing tools would ever share menu-side is whatever Core provides, and Core is planned but not yet scheduled. Today Core ships nothing here.
• It detects, it does not depend. Core looks at which Gillish tools are present and surfaces each one, but no tool requires Core to function, and Core never hard-wires itself into a tool's internals. A missing sibling is simply shown as not installed. Tools work with Core absent; Core works with any tool absent.
• It links straight through. From the one Core surface you go directly into each installed tool's own dashboard and its documentation here on this site.

What Core does today#

The honest current state, on the v0.1.x line:

• The ecosystem grid. Core boots and renders one card per Gillish tool. Each card shows whether that tool is installed and active, probed live, with a link into it. This is the part that works. Core does not own a shared admin menu, every tool keeps its own top-level menu by design.
• Dynamic Tags. Core's first real feature of its own: a set of short text tags you type into any page or post, swapped for live text when the page is shown. They started inside Gillish Node and moved into Core, so they now work anywhere on your site, not just on Node's own links. There are tags for the date and time ([y] for the current year, [today], [time]), for the current post ([views], [readtime], [published]), for copyright lines ([cyr] becomes "© 2026"), for the site and visitor ([sitename], [user]), and two you set yourself, your brand name ([brand]) and support email ([contact]). The whole feature is off until you turn it on, and every tag has its own on/off switch. If a tag name is already taken by your theme or another plugin, Core leaves it alone rather than fighting over it.
• A settings page with tabs. Core now has its own settings, split into a General tab and a Dynamic Tags tab. The Dynamic Tags tab is where you turn the feature on, switch individual tags on or off, see which ones are active, and set your brand name and support email.
• A neutral bot-detection signal. Since v0.1.26, Core owns the gillish_is_bot hook: one ecosystem-wide signal that any Gillish tool can read to know whether the current visitor is a bot. Node populates it; Cairnstone reads it; any future tool can do the same without wiring directly to Node.
• Light and dark. The Core surface follows the same paired light/dark theming as the rest of the ecosystem admin.
• It stays light. Core still creates no database tables and runs no scheduled jobs. It remembers only a few small settings, your light/dark preference, whether Dynamic Tags is on and which tags you enabled, and your brand name and contact email, and it cleans those up on uninstall.

That is deliberately a small surface. Core is built thin and predictable first; ecosystem-level features are layered on top of it as the toolset matures, never bolted on in a hurry.

Better together#

The principle Core exists to serve: every Gillish tool must be excellent on its own and worth more when its siblings are also installed. Cairnstone already reads visitor country through Node; Feed is scoped as the content finder that feeds Node; every Gillish tool follows one shared design language while keeping its own separate top-level admin menu by design (menus stay separate deliberately; the only future shared-menu surface is Core, which is planned but not yet scheduled). Core makes "what does this become when the other tools are here too?" the default question rather than an afterthought, and gives that compounding a single front door.

"Better together" is never "depends on." The value compounds when tools are combined, but each tool degrades gracefully and stays whole when run alone. Core is the clearest expression of that rule: it is the thing that only appears, and only matters, once there is more than one tool to tie together.

What comes next#

Core is named and reserved as the place ecosystem-level surfaces will live, a shared overview across tools, cross-tool preferences, and whatever else only makes sense above the level of a single plugin. None of that is built yet, and this page will not claim it before it ships. It is updated as Core grows past the dashboard, the same way every other status surface on this site moves only when real work lands.

The ecosystem-wide picture, what the whole toolset is, the better-together principle, the commercial and distribution model, and the honest pre-launch state, is set out in the Gillish ecosystem product brief.

The standing security, privacy and compliance posture, and the Core-owned EU Cyber Resilience Act program for the whole ecosystem, is at Core security & compliance. It is an honest working status, not a certification.

For what each tool does, see the rest of the ecosystem: Cairnstone, Node, Feed, Mesh, or the toolset overview.