Add a citations column (JSON array of source references such as Shang Han Lun chapter numbers or modern textbook pages) and use a list mapping to render them as a references block at the bottom. The same array can feed a JSON-LD ScholarlyArticle citations field if you want machine-readable provenance.

Yes. Keep parallel columns for english_name, pinyin, and characters. Tag mappings target three separate headings on the template, and a meta mapping populates the page title and OG image with whichever locale you set as primary. Hreflang can be added per locale if you publish multiple language versions.

Add a related_patterns column holding the slugs of constituent syndromes as a JSON array. A list mapping renders a See also block linking back to each component. The combined pattern keeps its own page; the cluster forms automatically through the related arrays without manual link maintenance.

Nothing about SleekRank prevents that, but the corrective workflow is far cheaper. Update the JSON array in the row and the page reflects the change on next cache invalidation. A clinical lead can audit and update 300 patterns in a single sheet review session instead of 300 article revisions across a CMS.

Yes. Add a practitioner_notes column and gate its rendering with a Twig conditional inside the base page template that checks user role. The same row drives both the public and the practitioner view; only the rendered HTML differs based on who is logged in at request time.

Run a second SleekRank page group for herbs, keyed on /tcm/herbs/{slug}/. Cross-link the two via slug arrays: each pattern page lists its core herb formulas, each herb page lists patterns it addresses. Two sheets, two URL families, fully interconnected through shared slug columns.

No. SleekRank lives under a different URL prefix you choose, so the existing blog at /blog/ keeps publishing under its own template. Reference pages at /tcm/food-therapy/{slug}/ become the canonical structured corpus while the blog handles long-form articles and case studies as before.

Yes. Build a print stylesheet into the base page once and every generated pattern inherits a clean print view. Alternatively, expose a /tcm/food-therapy/{slug}/handout/ subpath via a second template that renders the same row in a single-page handout layout suitable for clinic printers.