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 via the matching data source type.

Store the cultivar name in a dedicated column and append it to the URL slug. The template renders cultivar names in single quotes per botanical convention, and a parent_species field links the cultivar to its species page.

Yes. A 'group' column with values like tropical, succulent, fern, or carnivorous can drive different URL patterns from the same sheet, so the entire houseplant catalog lives in one source.

Add a toxicity column with values like safe, mildly toxic to pets, or highly toxic. A meta mapping drives a warning badge at the top of pages where toxicity is non-safe, so visitors with pets get the warning before scrolling.

Store photo paths in the source and drop the images into a structured assets folder named by slug. The template references the photo by slug, so adding a new species means adding a row and an image, nothing more.

Add columns for growth rate, mature height, and mature spread. A small Twig macro renders these into a stat row on every page when present, so the corpus surfaces sizing consistently.

Store a winter_care field per row. The template renders a 'Winter care' callout when the field is non-empty, so species that need a dormancy period get the warning without restructuring the layout.

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