About Harbour Atelier

One developer, many years with WordPress and a preference for small tools

Harbour Atelier is the name I use for focused WordPress plugins that solve a specific maintenance problem without becoming another platform, account or permanent obligation.

Harbour Atelier sailing bird mark

The person behind it

I have spent much of my working life building and maintaining websites

I worked across front-end and back-end development, with a large part of that time spent on WordPress - commercially, for charities and on my own sites. The same small but awkward maintenance problems kept returning.

I no longer work professionally because of my health. When I have the energy, I am returning to old plugins and ideas that never had time to become finished products. Harbour Atelier is where I release them properly.

That background shapes the work: practical scope, few dependencies, useful documentation and no pretending that an independently maintained plugin comes with a support department.

Why the plugins stay narrow

I would rather solve one problem properly than sell you another dashboard

WordPress already gives site owners enough moving parts. A plugin for one maintenance job should not quietly add a hosted service, a collection of unrelated features and a settings area that becomes work of its own.

  1. Start with a real problem

    Each plugin begins with a task somebody responsible for a WordPress site may genuinely need to perform or remember.

  2. Stay close to WordPress

    Use WordPress itself and keep operational data with the site wherever that is practical.

  3. Avoid unnecessary services

    I do not want a remote account or external API in the middle unless the feature genuinely cannot work without one.

  4. Make FREE worth installing

    The free plugin should solve the core problem without an expiry date or an artificial monitor limit designed only to frustrate you.

  5. Charge for saved work

    PRO should earn its price through automation, history, stronger checks or bulk tools - not by unlocking the basic job.

  6. Write down the boundaries

    You should know what a check proves, what it does not prove and where your hosting or WordPress configuration still matters.

No magic claims

A check is useful only when you know what it actually checked

Years around WordPress taught me not to confuse one successful layer with the whole system working. A database value can be correct while the public page is broken. WordPress can accept an email for sending without the message ever reaching the inbox.

Page Content Guard checks supported content stored in WordPress. It does not render the frontend. PRO uses the site's WordPress Cron and mail environment rather than pretending to be an external monitoring or delivery service.

I would rather state those limits before you install the plugin than explain them after you relied on the wrong assumption.

Checks run in WordPress Monitoring is performed inside the WordPress installation.
Operational data stays with the site Monitor settings and results are stored in the site's database.
Stored content, not the rendered page The plugin inspects supported WordPress records and values, not the final frontend output.
Your site still supplies mail and cron PRO depends on the WordPress scheduling and email environment already available to the site.

How the project is run

Independent means fewer promises, not vague ones

Support is best effort

There is no support team and no guaranteed response time. Documentation is intended to answer the common questions, and any direct help depends on the time and energy I have available.

Serious failures come before new features

Security, data integrity and major compatibility problems take priority over making the feature list longer.

I test failure paths, not only the happy path

Page Content Guard has deterministic tests for FREE and PRO behaviour, malformed input, failures, concurrency, migrations, rollback and larger installations.

That work reduces avoidable mistakes. It still does not turn software, WordPress or a hosting environment into a guarantee.

Support the project

If the free work proves useful, you can help me continue it

The plugins are not built around donations, and FREE does not become less useful without one. Ko-fi is there for people who saved time or avoided a problem and would like to support the testing, fixes and documentation behind the project.

Continue

Start with the problem, then decide whether FREE or PRO fits