HealthySkinfluence
- Public product
- Content
- Search
- Laravel
Consumer content and structured skincare knowledge
Turning skincare research and product data into a calm public experience.
↗VisitHealthySkinfluence
HealthySkinfluence as it is publicly accessible — captured from the live landing page.
- Contribution
- Product-minded full-stack engineering
- Role
- Co-founder & CTO
- Type
- Consumer product · Publishing platform
At a glance
A public-facing publishing product backed by structured articles, products and ingredients, editorial administration, search infrastructure and production workflows.
The linked landing page is public and the image below is an authentic capture. I do not present routes that are not currently available as live proof.
Product idea
Make a complicated subject feel approachable
Skincare knowledge is spread across editorial articles, product catalogues and ingredient terminology. The product challenge was to give that information one coherent structure without turning the public experience into a database interface.
The result connects roughly two thousand products and six thousand ingredients with about thirty in-depth editorial articles: a restrained editorial surface backed by a much denser application — related content, structured product knowledge, publishing workflows and search-ready records.
What I worked across
The public experience and the system that feeds it
- Structured relationships between articles, products and ingredients.
- Editorial workflows and administration built for regular publishing work.
- Search indexing and relevance work across different content types.
- Background processing for work that should not slow down an editor’s save.
- Public-page structure, accessibility, performance and search visibility.
Public boundary
Only claim what a visitor can verify
The live domain currently provides the landing page shown here. Other application capabilities are described from the source I built, but unavailable public routes are not represented as live screens or recreated for effect.
Product through-line
Research becomes structured, reviewable publishing
The useful engineering sits in connecting editorial work to a public experience without losing the relationships in between.
- 01Structure
Model the knowledge
Articles, products and ingredients become related records rather than isolated pages.
Out of sight
- Relational modelling
- Content relationships
- 02Edit
Give the team ownership
Editorial work happens through a dedicated administration surface instead of code changes.
Out of sight
- Publishing workflow
- Permissions
- 03Find
Make different content discoverable
Search infrastructure works across the shapes people actually look for.
Out of sight
- Search indexing
- Relevance tuning
- 04Publish
Serve a calm public surface
The complexity stays behind an experience designed for readers.
Out of sight
- Public rendering
- SEO and performance
Highlights
- One connected knowledge model
- Editorial content, products and ingredients are related instead of maintained as disconnected catalogues.
- Editors own the catalogue
- The administration surface turns product knowledge into an ongoing publishing workflow.
- Public proof stays public
- The case study uses the real live page and clearly separates it from capabilities that are not currently exposed there.
Technology
What it is built with
- LaravelDomain modelling, publishing workflows and background work.
- VueA responsive public and editorial experience.
- InertiaA cohesive bridge between server-side product logic and Vue.
- FilamentPurpose-built administration for regular editorial work.
- RedisFast application services and work that runs out of sight.
- Tailwind CSSA restrained, consistent interface system.
Next step
Have a workflow that does not fit off-the-shelf software?
Tell me what needs to change. I’ll tell you honestly whether I’m the right fit, then we can agree on scope, timing and the right working model.
Discuss your project →
