Editorial and testing policy
How a tool earns a published page
77 Toolkit publishes working utilities together with original explanations. This policy describes what is checked before a page is included in navigation and the sitemap.
Function first
A page must perform the task it promises with reviewable input, output, errors, and browser behavior.
Specific guidance
Examples, limitations, alternatives, privacy notes, and checklists are written for that tool rather than copied across the catalog.
Traceable sources
Long-form Guides link to primary specifications, standards bodies, or official project documentation whenever those sources exist.
Choosing new topics
A new tool should solve a bounded task that can be completed safely in a browser and explained without pretending to replace professional validation. The collection avoids fake generators, unavailable features, pages created only for keywords, and dozens of near-identical variations of the same conversion.
Functional review
Before publication, the maintainer checks representative successful input, empty input, malformed input, boundary values, copying or downloading, keyboard operation, responsive layout, and the claim that data remains local. Security-sensitive tools must state what they do not verify. Image transformations preserve an original preview and warn about re-encoding effects.
Editorial review
Every tool page includes a task-specific introduction, steps, realistic example, method, limitations, FAQs, scenarios, result checklist, privacy context, and a better alternative where appropriate. Guides are organized around a real decision or debugging workflow rather than a search phrase. Automation may assist code and drafting, but published behavior is tested and factual claims are checked against the linked primary references.
Language policy
Indexed publisher content is written in English as the site's primary language. Optional Chinese controls in selected applications are clearly user-initiated. The project does not create automatic translated copies merely to multiply page count; a future language edition should receive human review, its own navigation, and correct hreflang relationships.
Corrections and updates
Each Guide displays publication and update dates. Corrections can be reported through the Contact page or public issue tracker. Material changes to tool behavior, standards, browser support, or safety guidance should update both the page and its reviewed date. The public Git history preserves what changed.
Advertising separation
Publisher content and application controls are designed before advertising. Ads must not imitate tool cards, navigation, results, copy buttons, or downloads, and no wording encourages clicks. The noindex 404 page does not load AdSense.