Editorial policy

Authorship

Substantial pages are authored or reviewed by Oliver Burton. The byline is not decorative. Where a page is commercial, the same person is the engineer you would hire.

Review

Published technical content is read by a human who can stand behind the claims. We do not publish unreviewed model output as advice.

AI and tools

Drafting, research scaffolding, or copy-editing may use AI tools. That use is a writing aid. It is not a substitute for implementation judgement. Anything that looks like a command, a checklist, or a security claim is checked against current Laravel/PHP practice before it stays on the site.

Updating

Service and technical pages show a published date and an updated date when the substance changes (for example a new Laravel support window). Cosmetic edits do not always change the date.

Corrections

If something is wrong, email the contact address. Factual errors are corrected visibly; we do not silently rewrite history on security topics.

Sources

Framework behaviour is cited to Laravel’s own documentation where it matters. We do not invent statistics, client counts, or review scores.

What we will not publish

Thin location pages, keyword-swapped twins, or “what is Laravel?” primers that do not help a buyer with a live application.