Four layers, four jobs
Features: capability + field semantics + data residency. Columns: species FAQs. FAQ: fast myths. Guides: printable workflows.
Suggested path: features map → species column → FAQ for spats → guides for paragraph templates.
English coverage is partial; missing EN pages defer to Chinese originals—hreflang avoids hollow pairs.
Using templates without cargo culting
Templates are skeletons—you must inject dates, doses, triggers; blank forms index poorly. Copy skeletons privately, then atomize into app fields.
Five-part visit notes mirror clinical flow; map synonyms if your clinician prefers different headings.
Privacy boundaries
Guides assume anonymous readers—strip identifiable details when quoting publicly.
Announcements ship feature changes, not diagnoses—private channels carry individual cases.
Feedback that improves copy
Send summaries plus authoritative links when rules shift—we narrow claims instead of feigning universality.
Template requests with scenario depth (species, post-op day, monitoring tools) beat vague “write more.”
Limits
Web copy isn’t a VCPR substitute or ER tele-triage—call your hospital.
Feature-level detail: `/official/p/features`; data practices: `/official/p/privacy`.