Methodology
The directory is meant to be useful before it is impressive. These are the signals and standards used to keep the catalog understandable, honest, and worth returning to.
Each project starts with a concrete job: calculate something, compare options, prepare notes, format text, plan a task, answer a quiz, or explain a narrow topic.
Ideas are favored when they are evergreen, specific, and useful without requiring an account or a long setup flow.
Useful pages should explain the task in plain language, give enough context to avoid misuse, and make the main control easy to find on mobile and desktop.
Pages that attract visits or ratings are candidates for deeper examples, clearer assumptions, better edge-case handling, and extra supporting notes.
Public visit counts come from a lightweight script that runs after a project page loads in a browser. They are not copied from raw server logs.
The counter uses hashed browser cookie and IP signals to count no more than one visit per project per day for the same visitor signal.
Ratings are meant to answer one question: was this project useful for the task you opened it for?
Each rating is stored with hashed browser cookie and IP signals so repeat ratings are limited without storing raw IP addresses in the public rating store.
The public changelog records directory-level changes, measurement changes, and quality improvements. It is there so the site does not feel frozen or anonymous.
Individual projects can be revised when feedback shows confusing copy, missing assumptions, weak examples, or poor fit for a real use case.
hub2.day projects are lightweight helpers, not professional advice. Health, legal, finance, safety, and similar pages should be treated as organizing aids or starting points.
Corrections and quality concerns can be sent to hello@hub2.day.
