Our Peak3 website build covered 17 page templates and six CMS collections. At that scale, the questions about publishing deserve as much attention as the finished pages. A blog post, a whitepaper and a careers entry need different information. Making them editable is only part of the design problem. The person adding the next entry also needs to understand what is missing and what happens when they publish it. Here’s a hypothetical review I’d run before a CMS handoff: create a whitepaper entry, add the title and cover, then leave out the download file. Does the editor flag the missing file? Can someone preview what the visitor will see? If the entry can still be published, does it create a download button that leads nowhere? I’d use that test to decide which fields must be required and which incomplete states need an explanation.

Beautifully executed work

Returning to foundational assets is always a valuable exercise in brand scalability. Currently, I am preparing and structuring the master delivery files for a new sub-brand—built upon a visual identity system I originally designed a couple of years ago. Designing adaptable brand frameworks from day one is what allows a business to expand seamlessly over time while maintaining complete visual coherence. Looking forward to sharing the final execution soon.