Stuck On Sweet

Overview

Stuck On Sweet was a client WordPress revamp, so the work was very practical. The site already had a lot of recipe content, but it needed clearer structure, better browsing paths, and a more polished brand feel.

I moved the site to Kadence, rebuilt the homepage, cleaned up the recipe categories, redesigned the navigation and sidebar, styled the archive cards, added Flodesk forms, and improved small article details like Jump to Recipe, Table of Contents, affiliate disclaimer, and link styling.

The Problem

The site had a lot of useful recipe content, but it was not as easy to browse as it could be. Categories had grown over time, the mobile path needed work, and the design needed to feel more polished without making the site harder for the client to update.

What I Built

• •Homepage with hero section, featured recipes, dessert blocks, search, author bio, and newsletter signup
• •Recipe category structure for desserts, cookies, cakes, brownies, pies, holidays, and meal content
• •Main navigation with dropdown recipe categories
• •Sidebar with bio, newsletter form, search, and popular recipes
• •Footer layout and post loop cards
• •Styled archive layouts with category badges and clear CTAs
• •Flodesk forms across homepage, sidebar, footer, and post layouts
• •Jump to Recipe, Table of Contents, affiliate disclaimer, and link styling improvements

Technical Approach

Kadence was a good fit because the client needed a flexible WordPress setup that could be maintained after the redesign.

I organised the site around how readers browse recipes: meal type, dessert type, holiday, popular recipes, recent posts, and search. That structure makes the site easier to use without changing the publishing workflow.

Client Delivery

A big part of the project was making the site feel better without making it harder to run. I kept the editing workflow familiar, used clear reusable layout patterns, and made sure forms, cards, and content sections felt consistent across the site.

What I Would Improve Next

I would continue refining archive templates as more content is added, review mobile spacing after the next publishing round, and run a Core Web Vitals review as the recipe library grows.