Sources
Guides start from primary sources. For browser metrics and APIs, that means web.dev, Chrome for Developers and the relevant specifications. For framework behaviour, it means the framework's own documentation, API reference and release notes. Each guide ends with a list of the sources it relies on, labelled by type:
- Primary source: documentation or announcements from the organization responsible, such as Google for Chrome APIs or the Vue team for Vue.
- Secondary source: reporting or analysis by others, such as law firm commentary on privacy rules.
- Commercial source: a company describing its own offer, such as a published price list.
Where a claim rests on a secondary or commercial source, we try to say so in the sentence as well as in the list.
Numbers and examples
We do not invent statistics, benchmarks, client results or testimonials. A figure in a guide either comes from a cited source or belongs to an example clearly marked as illustrative. Example traces, dashboards and before-and-after panels on this site are labelled "illustrative" or "sample numbers" wherever they appear.
Versions and dates
Framework and browser behaviour changes often. Guides name the versions they describe, and every guide shows the date it was last updated. When a release changes our advice, we update the guide and the date.
Code samples
Code samples are kept short so the idea is clear, follow the documented APIs they illustrate, and are not production-ready libraries. Adapt them to your app, and test them in your own setup.
Commercial interest
Our funding and commercial interest are described in the site footer. Whatever topics we choose, what a source says is reported as it says it. We take no advertising, sponsorship or affiliate commissions, and no vendor pays for mentions or reviews.
Use of AI tools
We may use software tools, including AI writing assistants, for drafting, editing and checking. Every guide is reviewed against its sources before publication, and the byline takes responsibility for the result.
Corrections
If you find an error, email hello@renderloria.online with the page and passage. We check the claim against its sources and correct it if we were wrong. Substantive corrections are noted at the end of the affected guide with the date; small fixes such as typos are made without a note.
Recommendations and relationships
When a guide or review recommends a tool, library or approach, we have no financial relationship with its makers. If that ever changes, the relationship will be disclosed next to the recommendation.