Aurelia Bloom is a concept luxury skincare e-commerce website designed and built as a complete, end-to-end shopping experience for a premium botanical beauty brand. The project shows how elegant visual design, clear product discovery, and a thoughtful customer journey can come together to create an online store that feels as refined as the products it sells.

The experience opens with a warm ivory and deep plum palette, refined serif typography, and generous white space, giving the brand a calm, high-end editorial look. A slim announcement bar highlights complimentary worldwide delivery, while the clean navigation (Collections, Cellular Elixirs, Philosophy, Pledge and Concierge) keeps every key section one click away. A currency selector, account access, wishlist, and shopping bag complete the header for a true international storefront.

The heart of the project is "The Complete Botanical Master Catalog", a fully filterable product collection page. Customers can browse by category tabs (All, Cellular Elixirs, Alpine Hydration, Balance Oils and Ritual Toolsets), refine results by Cellular Target & Concern and Formulation Texture, adjust a price range slider, sort by "Most Popular" and switch between grid and list views. Each product card includes high-quality imagery, a Bestseller badge, concern and texture labels, star ratings, pricing, and a wishlist heart so that shoppers can compare products quickly and confidently.

Beyond the catalog, the site tells the brand story through dedicated content pages. The Philosophy page explains the science-led approach, including high-altitude extremophile adaptation and a colloidal 24K gold suspension, supported by an elegant pull-quote layout. "The Circular Sustainability Pledge" presents the brand's eco commitments, such as a violet glass and refill pod system and ethical alpine foraging quotas, in clean, easy-to-scan cards that build trust with conscious buyers.

A personal account dashboard completes the journey. It features a member profile, loyalty points balance, order history with status labels (Fulfilled and Delivered), carrier tracking details, saved items, saved sequences, and VIP privileges, all designed to encourage repeat purchases and long-term customer loyalty. A privacy and botanical cookies consent banner shows attention to compliance and user trust.

Key highlights:

Luxury, editorial-style visual identity with a cohesive colour and type system

Advanced product filtering, sorting and category navigation

Responsive product grid with grid and list view options

Brand storytelling pages for Philosophy and Sustainability

Customer account area with orders, loyalty points and wishlist

Smooth micro-interactions and a polished, conversion-focused layout

This project demonstrates my skills in modern web design, UI and UX design, and e-commerce website development for beauty, skincare, and luxury lifestyle brands. If you need a premium online store, a product catalog website, or a conversion-focused brand site that builds trust and drives sales, I would love to help bring your vision to life.

A luxury skincare store lives or dies on how calm and spacious the product pages feel. Did you pick the photography style for Aurelia Bloom yourself, or work around supplied images?

Agents fail tax work by filling the gaps in the file. Surge AI's new benchmark gives agents 50 real tax assignments, about 30 documents each, and the best one passes 10.8%. The failures in their write-up aren't misread PDFs. One agent decided a couple wasn't married from their Florida address, while the file showed a Colorado ceremony. Another assignment plants a ledger entry pointing at a receipt that isn't there. That matches what I see on 200-page loan files. Reading the pages is the easy part. The hard part is a value with no page behind it, because the model fills it with something plausible and the output looks finished. The Hacker News thread says better tooling around the model would fix most of this. I think it fixes part of it. The tooling has to make the agent cite a page for every answer and accept "not in the file" as a result. If you think tooling closes most of that 90% gap, what would you add to it first?