About template.tips

What you'll find here

Every article answers a specific question a developer might search for, with real code you can copy, the browser-support caveats that matter, and an honest note on when a technique is the wrong tool for the job. We cover three areas:

• CSS — layout, selectors, animation, and modern features as they ship.
• HTML — semantic markup, native elements, forms, and accessibility.
• Quick tips — small, focused techniques you can apply in minutes.

How we keep it accurate

Web platform features move quickly, so accuracy is the thing we care about most. Our editorial approach:

• Primary sources. Claims link to authoritative references — MDN, web.dev, the W3C/WHATWG specs, and caniuse — not second-hand blog posts.
• AI-drafted, human-reviewed. Articles are AI-drafted, then reviewed by Paul Radford for technical accuracy and tested against current browser behaviour before they're published.
• Corrections. If something is wrong or has gone out of date, tell us and we'll fix it. Email hello@template.tips and we'll update the article.

Who's behind it

Articles on template.tips are AI-drafted, then reviewed and edited by Paul Radford, a full-stack developer, before they go live. He started the site to collect the CSS and HTML techniques he reaches for most and make sure each is explained the way he'd actually want it explained: with working code, the caveats that only show up in production, and a straight answer on when a technique is the wrong tool for the job.

Every article is reviewed for technical accuracy before it goes live. If something here is wrong or has gone out of date, Paul would rather hear about it than not, email hello@template.tips and it gets fixed.

template.tips has a sister site, aitool.tips, covering AI coding tools, prompt engineering, and developer productivity.

Get in touch

Questions, corrections, or feedback are always welcome. Reach us at hello@template.tips or head to the contact page.