voxa

voxa pretends to be a product data companion for growth and ops teams. the fictional product promises a daily signal, a way to ask follow up questions, and a clean path from insight to action in tools like slack.

the marketing site has to sell that idea without turning into dashboard cosplay. so the page leans on narrative sections: a day with voxa sequence, before and after contrast, a noisy feed that settles into clarity, use case worlds, pricing, and a short blog index. each block is a designed scene, not a generic feature grid with icons slapped on.

visually the brand stays tight. dark mark, quiet type, crisp cards, and motion that supports the story instead of decorating it. the hero uses a soft ripple canvas. later sections reveal on scroll. nothing shouts.

i treated it like a real product site even though the product is imaginary. that meant writing actual copy, inventing coherent feature names, and making the fake login feel intentional instead of abandoned.

structure stayed static on purpose. html pages for the marketing surface and account shell. css split by section so each chapter could evolve without turning into one giant stylesheet. small javascript modules for navbar behavior, scroll reveals, the day sequence, and the hero canvas.

working this way kept the feedback loop fast. change a section, refresh, judge the rhythm. no build pipeline arguing with the design. the constraint was the point: if the story only works after three frameworks and a design system, it probably was not clear enough yet.

the hardest part was tone. analytics marketing loves urgency and clutter. i pushed the other direction: fewer claims, stronger hierarchy, and enough empty space that the product idea can breathe.

the day with voxa section is the emotional center. it walks through alert, ask, and share as a sticky narrative so visitors feel a morning with the product instead of reading a feature list. the contrast block makes the same argument in two columns. before is messy. with voxa is focused.

pricing and faq stay honest about the fiction. they are there to complete the site grammar of a product page, not to collect cards. the blog stubs exist so the information architecture feels grown up: a product like this would publish, so the shell is ready even if the company behind it is not real.

voxa is not live software. there is no real data pipeline, no auth provider, no billing, no customers. the login page is a prop. the metrics on screen are invented. if you click around expecting a working product, you will meet a carefully built demo.

think of it as a portfolio piece and a practice ground. a place to test layout judgment, product storytelling, and front end polish without the noise of a real launch. that honesty matters. the craft is real. the company is not.

i ended with a complete static marketing world for a product that only exists on the page. that was the goal. it clarified how much of a product site is writing and pacing, how motion can explain an idea better than another icon row, and how far plain html and css can go when the concept is clear.

voxa stays as a reference: a personal design i made alone, finished enough to show, clear enough to say out loud that it is a mock.