Page consistency
Guide editors through a recurring content structure without asking them to assemble every page by hand.
Product design · Content operations · Internal tool
House of
Verdure CMS
A publishing workspace that turns detailed botanical content into repeatable plant pages, while giving the team control over what appears across the site.
Make a rich plant archive manageable day to day.
Each plant page combines taxonomy, imagery, origins, history, facts, a dossier, and search metadata. Editors also need to choose which stories and sections appear across the site. The interface brings those decisions into two clear workspaces.
Editorial control
Keep global defaults, page-level overrides, and featured stories understandable as the archive grows.
Publishing paths
Support drafting, previewing, downloading HTML, and publishing from the same workspace.
Two connected views for creation and curation.
The create view organizes a long botanical story into named sections. The site admin view handles shared defaults, per-plant exceptions, homepage visibility, and carousel order.
Interface shown in the supplied product screenshots. Open either image to inspect its full length.
A clear path from entry to publication.
- 01
Prefill before editing
Editors can load an existing plant from the database, then change only what that page needs. Import controls provide additional ways to start from prepared content.
- 02
Group content by editorial purpose
Identity, imagery, botanical information, origins, history, illustration, facts, dossier, and SEO each have their own section, with labels and field guidance near the work.
- 03
Separate defaults from exceptions
Site admin exposes global section settings first, then per-plant overrides. This keeps routine decisions centralized while allowing individual stories to differ.
- 04
Make featured content adjustable
Editors can show or hide plant stories in the carousel and reorder them, giving editorial placement a direct control.
- 05
Keep review close to publishing
Preview, download HTML, publish to site, and save to server appear in the persistent action area at the bottom of the interface.
A repeatable editorial workflow for an expanding archive.
StructureOne guided plant-page format
ControlGlobal and page-level settings
CurationFeatured story visibility and order
ReviewPreview and publishing actions together
Next: validate the editorial workflow.
The screenshots demonstrate the interface and available controls. Usage results have not been supplied, so the next step is to measure how editors use it.
Questions to track
- Time to draft and publish a plant page
- Fields that require frequent correction or clarification
- How often editors use a prefilled page or a per-plant override
- Preview-to-publish completion and failed publish attempts
House of Verdure brand↗