From a collection of images to a creative universe.
I wanted visitors to understand the range of my work—visual design, 3D, and creative systems—without losing the personality behind it.
The problem
My previous portfolio could display the work, but it wasn't telling the whole story.
In the earlier portfolio ↗, a visitor could see images, but I wanted fuller project pages: complete series, motion, process, and the reasoning behind each creative system. Some paths led to a single picture when the work needed a connected story.
I also needed a presentation that made sense of an unusual range. Organizing the top level by software would bury the relationship between the art I create, the 3D work I build, and the systems I invent.
The process
Start with the visitor's story, then make room for experimentation.
- STRUCTURE
Create → Build → Invent
I grouped work by what I do rather than by Photoshop, Blender, or other software. Each project can still name its tools where they matter.
- IDENTITY
Find a visual language with range
I iterated on a near-white concrete surface, midnight blue layers, neon seams, a bold name treatment, and recurring wave transitions. The expressive moments sit on a clear editorial grid.
- CONTENT
Give projects enough space
I built internal pages for image series, 3D motion, typography, and systems. The deeper case studies use a repeatable order: problem, process, solution, outcome, and learning.
- ITERATE
Use AI to shorten the idea-to-test loop
I described the desired behavior, supplied references and project material, reviewed live versions, and corrected what didn't feel right. AI-assisted implementation helped turn those decisions into code and content quickly; direction and judgment stayed with me.
The solution
A portfolio that can evolve as the work grows.
The homepage introduces the three practices, with browseable project cards that lead to internal series and case studies. Motion clips, galleries, readable content panels, and a public profile give different kinds of work the presentation they need.
The site is a static collection of pages and assets. Its source lives in a private GitHub repository. Cloudflare Pages deploys updates from the repository, and the custom domain points to that deployment. The domain was registered through Hostinger; its nameservers now use Cloudflare. This keeps publishing straightforward: revise the work, push the change, and check the deployed page.
AI assists with drafts, code, and iteration. I set the direction, choose the work, review the result, and decide what ships.
The outcome
The site is live and can now show both finished work and how I make it.
Visitors can move from the homepage to full project pages and structured systems case studies on feliciadonnamarie.com ↗. The site has a working GitHub-to-Cloudflare publishing path and a backup branch from before the latest visual changes.
There are no measured visitor or hiring results yet. The visible result is a clearer portfolio architecture and a repeatable way to add the next project without rebuilding the site from scratch.
What I learned
A strong structure lets the personality get louder.
The biggest design decision was to build a system for showing the work before polishing individual effects. Once the categories, page hierarchy, and case-study pattern were clear, it was easier to use neon, motion, and texture with purpose. The same approach made AI useful: shorter cycles for trying ideas, with a consistent standard for deciding what belonged.