Website & Resources Library Design
Client
Gieni Website & Resources Library Redesign
Year
2025
Gieni's marketing website launched with a single blog page covering all company content. After I completed the initial site design, the product moved fast, new features, integrations, and use cases were shipping every few weeks and the resources section couldn't keep up. I was brought back to rebuild it into a structure the marketing team could run and scale on their own.
Scope of Work
One page, six kinds of content
By the time I returned to this project, Gieni had accumulated blog posts, use cases, PR mentions, instructional videos, user guides, and product updates — all competing for space on one undifferentiated feed. Nothing was tagged, filterable, or built to scale, and every new content type meant another one-off page.
Built to scale without design or dev
Because each content type lives in its own collection, marketing can publish, tag, and reorganize independently — and new content types can be added later without reworking the site's structure.
Not Every Widget Survives
Reaching this layout meant designing and testing far more widgets than made the cut — Profile Strength, Visibility Score, RFQ status cards, and profile-completion nudges were each iterated on individually before approval. The result is a set of modular widgets, not one fixed layout, so performance data, RFQ activity, and completion prompts can coexist without competing for attention.
Structuring a CMS marketing could run alone
I restructured Resources around six independent Framer CMS collections — Blog, Use Cases, PR Mentions, Instructional Videos, User Guides, and Product Updates — each with its own template and taxonomy, unified under one Resources navigation.
Custom Illustrations for Gieni and Microsoft Partnership
Reaching this layout meant designing and testing far more widgets than made the cut — Profile Strength, Visibility Score, RFQ status cards, and profile-completion nudges were each iterated on individually before approval. The result is a set of modular widgets, not one fixed layout, so performance data, RFQ activity, and completion prompts can coexist without competing for attention.
