Scope and audience
We publish material about naming decisions and the tools that help people make them. An article should solve a defined problem within that subject. We do not add unrelated topics simply because they are popular in search. A naming guide should leave the reader with a practical next step.
How an article is produced
Start with a specific brief or question. Separate factual claims from creative judgments. Consult primary references for formal rules and calendar information where available. Write a complete explanation, include trade-offs and label unresolved checks. AI can assist drafting and implementation, but its output is not itself a source. This edition has not received an independent native-speaker or professional editorial review.
Evidence and citation rules
A source should support the claim beside it. A national statistics page can support a statement about its dataset, not a claim about the meaning of a particular name. A literary source needs a real passage and context. Official registers should be preferred for registration questions; even then, current individual eligibility must be confirmed through the relevant process. We do not turn a link into a certification badge.
Examples and first-hand experience
Worked examples are labeled as invented design briefs when that is what they are. A proposed testing protocol is not described as completed research. First-hand claims are limited to actions actually performed, such as entering a documented date in the calendar tool. We do not invent clients, quotations, participant counts, author biographies or success metrics. A future real-user case would require permission and clear disclosure of what was observed.
Traditional and culturally sensitive material
Calendar arithmetic is distinguished from divination. Cultural associations are not presented as universal beliefs held by everyone in a country. Sacred or community-restricted practices are not reduced to an automatic name generator. Where local or community review is needed, we say so. Lack of verification is displayed rather than disguised as certainty.
Dates, translations and corrections
An article’s date reflects its creation or a substantive revision, not a cosmetic refresh. English and Chinese long-form editions are linked as translations. Core tool translations do not imply that all names have passed local cultural review. If an error is reported, retain the exact page, statement, proposed correction and supporting source. A factual correction should change the affected content and record a dated note; no correction history is invented for this initial edition.
Search and trust
We use descriptive titles, actual HTML text, internal links, language annotations and structured data to make content understandable. These are publishing practices, not promises of indexing or rank. E-E-A-T is not a score that this website can award itself. Independent reputation and demonstrated expertise must be earned, not replaced with badges or fabricated author profiles.