Who produces this content
userTourKit is a solo-maintained project. All documentation, guides, comparisons, and blog posts are written and reviewed by Dominique Degottex (domidex01), a software engineer with working experience in React, TypeScript, and developer tooling. The about page lists verifiable external profiles (GitHub, LinkedIn, X) so readers can assess expertise independently.
How content is reviewed
Every content change — docs, comparisons, blog posts, landing copy — is submitted as a pull request to the public repository at github.com/domidex01/tour-kit. The full edit history is public and auditable. Each PR is type-checked, tested, and built before merge; technical claims that depend on code behavior are verified against the referenced code paths.
Because the project is solo-maintained, there is no separate editorial board. Readers and contributors are encouraged to open an issue when a page is factually wrong, out of date, or unclear. See Corrections below.
Sources and citations
- Primary sources first. When discussing a library, framework, or browser API, we link to its official documentation or specification — not second-hand summaries.
- Code claims are linked to code. Statements like "Tour Kit ships a X KB bundle" or "API Y returns Z" must link to the commit, npm package page, or source file that proves them.
- Competitor claims require their docs or repo as the citation. Comparisons against Joyride, Shepherd, Driver, Intro, Appcues, Pendo, WalkMe, or Userpilot cite the competitor's own documentation or pricing page.
- No fabricated benchmarks. Performance and bundle-size figures are either measured from the current release or omitted. When a number is known to be stale, we label it as such.
Corrections policy
If you find an error — a broken API signature, an outdated comparison claim, a miscredited source — please open an issue at github.com/domidex01/tour-kit/issues with the page URL and the specific claim. We aim to acknowledge corrections within 7 days and fix or retract substantive errors within 30 days. Significant corrections are logged in the commit history on the affected file, which also drives the visible "last updated" date on every docs page.
Ethics and disclosures
- No paid placement. We do not accept money, gifts, or sponsorships in exchange for coverage in comparisons, tutorials, or blog posts. Tools are recommended on technical merit only.
- No affiliate links. We do not use affiliate tracking on outbound links to third-party tools or stores.
- Commercial relationship: ourselves. userTourKit sells a commercial Pro license. When a comparison mentions our own Pro packages (adoption, analytics, checklists, etc.), we label them as such so readers can weigh the bias.
- No anonymous sources. Every claim is attributed to a public artifact — docs, repo, npm, issue thread — that readers can verify themselves.
AI-assistance disclosure
Some editorial content (primarily long-form tutorials, comparison articles, and glossary entries) is drafted with the help of large language models — currently Anthropic's Claude family — and then reviewed, edited, fact-checked, and code-tested by a human before publication. No AI-generated content ships unreviewed. Technical claims generated by AI are verified against primary sources (official docs, source code, npm) before merge.
Update cadence
- API reference is regenerated on every release so it cannot drift from shipped code.
- Comparison articles are reviewed each time a competitor ships a major version, and at least every 6 months.
- Tutorials and guides are reviewed when a referenced dependency (React, Next.js, Fumadocs, etc.) ships a breaking version, or every 12 months.
- The "Last updated" stamp on each docs page is derived from git history and updates automatically when the file changes.
How we test
For the methodology behind benchmarks, bundle-size claims, accessibility scores, and performance measurements, see How We Test.