Tanit Interiors

TANIT is an architecture and interiors practice focused on creating refined spaces and thoughtful design experiences. The website needed to act as an extension of the studio's work - showcasing projects through strong visual storytelling while remaining easy to manage internally. The result is a premium editorial experience built around imagery, typography, and content flexibility.

Architecture websites often rely heavily on photography, making it easy for the digital experience itself to feel secondary. The challenge was to create a platform that elevated the presentation of projects without competing with the work being showcased. Additionally, the client required a content management workflow that would allow new projects and content to be published without developer involvement.

I approached the project with an editorial mindset, focusing on pacing, whitespace, and typography rather than excessive visual effects. Layouts were designed to give imagery room to breathe while creating a clear narrative structure across projects and pages. Each interaction was intentionally subtle, allowing the content to remain the focus while still creating a premium browsing experience.

The visual system is built around restraint. A neutral palette, strong typographic hierarchy, and carefully controlled spacing create a timeless aesthetic that complements the architecture rather than distracting from it. Every component was designed to support the content-first nature of the website. The system disappears - so the work can appear.

The finished website provides a flexible and future-proof foundation that reflects the quality of the studio's work. By combining editorial design principles with modern frontend development and a robust CMS, the project delivers a browsing experience that feels as considered as the spaces being showcased.

• 01

  Editorial design principles - pacing, whitespace, and typographic rhythm - are as valuable in web design as in print.

• 02

  CMS architecture should be designed alongside the visual system, not bolted on afterwards. Both need to serve the same content logic.

• 03

  Restraint is a design decision. Choosing what not to include is often the most significant creative act.

• 04

  A well-structured content system removes the developer from day-to-day platform management - which is itself a quality outcome.