1. Primary Channels
Use any of the following channels to report issues, request features, or discuss partnerships:
- Email: gavinlamxq@outlook.com (general feedback / partnerships)
- GitHub Issues: github.com/linxqing/tools-navigation/issues (bug reports / feature requests)
- GitHub Discussions: github.com/linxqing/tools-navigation/discussions (community / knowledge sharing)
2. Response Time
Our core maintainers span several time zones. On business days (Mon–Fri) we typically respond to email and GitHub Issues within 24–48 hours. Feature-request discussions may take longer — we'll do our best to give a first response within 7 days.
For urgent security issues, see the Security Disclosure section below.
3. How to File a Good Bug Report
To help us reproduce and fix bugs faster, please include in your GitHub issue:
- Steps to reproduce: the full path from page load to the bug.
- Expected result: what you expected to happen.
- Actual result: what actually happened; screenshots or screen recordings are great.
- Environment: browser version, operating system, device type.
- Sample input: input that triggers the bug — please anonymize any real tokens, keys, or PII.
4. How to File a Good Feature Request
When proposing a feature, please describe:
- What you would like added or improved?
- Which workflow pain-point does it address?
- Are there existing alternatives you already know? Their strengths and weaknesses?
- Would you be willing to contribute code? (We provide PR templates and code review.)
5. Partnerships
We welcome the following types of collaboration:
- Blog link exchanges: with other privacy-first or developer-tools blogs.
- Open-source cataloging: inclusion in awesome-* lists or open-source directories.
- Corporate training: workshops on "Building Client-Side Developer Tools" for engineering teams.
- Sponsorship: cloud credits, ad optimization consulting, or security audits.
Send a short email describing your proposal, including your website or GitHub link, and we'll respond within 3 business days.
6. Security Disclosure
If you discover a potential security vulnerability on the Site (e.g., XSS, dependency confusion, information leakage), please do not disclose it in a public issue. Email security@team-tools.xyz directly (PGP public key available in SECURITY.md). We will acknowledge within 72 hours, and credit you publicly after the fix lands (unless you prefer to stay anonymous).
7. FAQ
Q: Does my data get uploaded?
A: Except for the "IP Lookup" tool, all core computations run locally in your browser. See our Privacy Policy for the full breakdown.
Q: Do the ads interfere with the tools?
A: We intentionally place ads away from the tool body (around the hero, blog list, and footer). The tools themselves remain a clean, dark, professional experience — no pop-ups, no interstitials.
Q: Is there an ad-free option?
A: Not at the moment. If you'd like to support us, you can: link to Team Tools from a blog post, contribute a PR, or just send us a kind email :)
Q: Will there be an API or CLI?
A: We are evaluating a CLI (Node.js 18+) build, with a Beta expected in Q3 2026. If this is important to you, please vote on the related GitHub Issue.