Anywhere structured. Google Sheets and Notion work well for editorial teams, a flat JSON or CSV works for solo curators who prefer git, and a custom WordPress post type works for teams that already live inside WP. SleekRank reads any of them.

Store lookalikes as an array of objects with name, key distinguishing feature, and severity. The template renders the block in a fixed warning style on every page that has entries, so readers always see the warning the same way.

Yes. A kingdom or group column with values like plant or fungus drives different URL patterns from the same sheet, so a single curatorial source can cover both forager domains.

A region_notes column lets curators flag plants that are edible in some regions and avoided in others. The template renders the regional note in a callout when present, so the reader sees the nuance before assuming universality.

Yes. Add a legal_status field with values like protected, restricted, or open. The template renders the status as a badge near the top of the page, so readers see permit or protection requirements before reading further.

Store preparation per edible part. The list mapping renders each part with its preparation note attached, so 'leaves: cook to neutralize formic acid' stays paired with the leaves entry.

Add a community_notes field with moderated entries, or accept submissions into a separate sheet and curate them into the canonical source. The page renders whatever the source carries on the next cache cycle.

Edit the row. The cache expires on the configured cycle and the page reflects the new data on the next request, so a corrected seasonality range propagates across the corpus without per-page edits.