The articles on the Hiddlins blog are written to help you make better decisions about your website, whether you are a developer, a designer or a business owner. This editorial policy explains how we research, write, review, update and correct that content, so you know what you can expect from it.
Our purpose#
We write about what we know and work with every day: web performance, accessibility, semantic HTML, JavaScript, PHP, WordPress and WooCommerce, UI/UX design, data visualization, AI and machine learning on the web, and technical SEO. Our goal is practical usefulness. Every article should leave you with something you can understand, apply or decide on.
We aim to be accurate, clear and honest about trade-offs. If an approach has downsides, we say so. If the answer is “it depends”, we explain what it depends on.
How we research#
Articles start from real questions: things clients ask us, problems we solve in projects and topics where we see confusion or outdated advice. Before writing, we:
- Consult primary and authoritative sources such as official documentation and specifications, for example MDN Web Docs, the W3C and its Web Accessibility Initiative, web.dev, php.net, the WordPress and WooCommerce developer documentation, schema.org, Google’s developer documentation and OWASP.
- Check that facts, version numbers, thresholds and browser support reflect the current state of the technology at the time of writing.
- Where possible, test techniques and code ourselves before recommending them.
How we write#
We write in plain English for a broad audience and explain technical terms when we first use them. Our standards include:
- Accuracy first. We do not invent statistics, studies, quotes, testimonials or case-study results. If we cite a number, it comes from a source we can name and link to.
- Clear structure. Descriptive headings, short paragraphs, summaries and code examples where they help.
- Working code. Code samples are written to be correct and readable, with security and accessibility in mind. They are examples, so always adapt and test them for your own context.
- Balanced recommendations. We explain why we prefer an approach and when an alternative might suit you better.
- Accessible content. We use semantic headings, meaningful link text and sufficient contrast, in line with our accessibility statement.
How we review#
Before an article is published, it is reviewed for technical accuracy, clarity and completeness. We check every factual claim against its source, verify that external links point to real, authoritative pages, and test code samples where practical. We also read each piece from the perspective of the intended reader and ask whether it actually answers their question.
Transparency about AI assistance#
We work with AI and machine learning, and we use AI tools in our own workflow where they genuinely help. That can include brainstorming topics, summarising documentation, suggesting outlines, drafting sections, or checking grammar and readability.
However, AI tools can be confidently wrong. That is why:
- No article is published without human review and editing.
- Every factual claim, figure and code example is checked against authoritative sources or tested before publication.
- We take full editorial responsibility for everything we publish, regardless of the tools used to produce it.
Sources and links#
We link to sources so that you can verify what we say and dig deeper. We prefer official documentation, specifications and well-established reference sites over secondary commentary. External links open in a new tab and are chosen because they are useful, not because anyone has paid for them.
Links can break and pages can change over time. If you find a link that no longer works or no longer supports the claim it is attached to, please let us know.
How we keep content up to date#
The web changes quickly. Metrics are replaced, standards are revised and new language versions arrive. We review our articles periodically and update them when the underlying facts change, for example when Google updates its Core Web Vitals, when a new version of WCAG is published or when a new PHP release changes best practice.
When we make a substantive update, we revise the article’s modified date. Minor edits, such as fixing typos or improving wording, may be made without a separate note.
Corrections#
We work hard to get things right, but mistakes can happen. If you spot an error, please contact us with the article link and a short description of the issue. We review every report. When we confirm an error, we correct it promptly, and if the error was significant, such as incorrect technical guidance, we add a short note to the article explaining what was changed.
Independence#
Our content is editorially independent. We do not accept payment for coverage, publish sponsored posts or include paid placements. We do not currently use affiliate links; if that ever changes, we will disclose it clearly on the relevant pages.
We are a web development studio, and our articles sometimes mention our own services where they are genuinely relevant. Those mentions never change our technical recommendations. If a free tool, a plugin or a do-it-yourself approach is the right answer for you, we will say so.
Not a substitute for professional advice#
Our articles provide general information. They are not legal, financial or security advice tailored to your situation. For specific requirements, such as legal accessibility obligations or regulatory compliance, consult a qualified professional. See our disclaimer for more detail.
Questions about this policy#
If you have questions about how we create content, or feedback on an article, we would like to hear it. Get in touch and we aim to reply within one business day.
Frequently asked questions
Do you use AI to write your articles?
We may use AI tools to help with research, outlining, drafting or editing. Every article is reviewed, fact-checked and edited by us before publication, and we take full responsibility for what we publish.
How can I report an error in an article?
Contact us through the contact page and include the article link and a short description of the issue. We review every report and correct confirmed errors promptly.
Are your articles sponsored?
No. We do not accept payment for coverage, and we do not publish sponsored posts. If that ever changes, any sponsored content will be clearly labelled.