A real tool before a real listing
An inventory record is a research starting point, not a published recommendation. Before an introduction is published, the original URL and tool identity should be checked, the visible functions reviewed and the primary category chosen from the actual task.
A tool can have one primary subject category and several relevant function types or tags. Classification should describe the tool's behavior, rather than merely echo its brand name.
Explain the task and the boundaries
An introduction should include a short description, main features, intended users, practical use cases, limitations and data-processing notes. The detailed article belongs in the main body, where the reasoning and examples can be read together.
Features should be distinguished from possibilities that have not been tested. A worked calculation needs assumptions and units. A visual planning aid should not be called a physically calibrated simulator without evidence.
Treat images as evidence
A tool image should help readers understand the real interface. Prefer a genuine screenshot or a clearly identified illustration over unrelated stock photography. A screenshot records a moment; it does not prove every feature or demonstrate an independent security review.
Do not use fabricated results, fictional popularity badges or invented testimonials to make an entry look complete.
Separate statements from verification
If the original site says that files are processed locally, report it as the site's statement unless the behavior has been independently checked. Be explicit about the scope of a review. Checking a visible setting is different from auditing the network or the source code.
Links to relevant primary documentation can help readers go deeper. Verification dates should reflect the actual review rather than update automatically just because a page was saved.
Review each language
English and Korean pages are edited separately and linked as translations. Tool identity and the original URL come from the shared record. The explanatory text, examples and SEO metadata belong to the individual language page.
A translation should preserve the meaning and limitations of the original review while reading naturally. Missing translations should not produce misleading language links.
Publish deliberately, correct specifically
Internal research and review stages are separate from WordPress publication. Marking an entry Ready to Publish does not publish it. Incomplete inventory, draft entries and empty tests should remain outside public listings.
When a tool changes or a report identifies a problem, recheck the relevant claim and update the explanation. The verification date and the actual evidence should tell the same story. Contact reports are welcome, but submitting one does not guarantee a particular update time.