Stefano Bartoletti

My new portfolio website is finally live after many weeks of work! It has been built with many great techs: @nuxt_js, @tailwindcss, @daisyui_, @storyblok, @Netlify, GSAP by @greensock, Lenis by @darkroomdevs, @threejs via @tresjs_dev. It is live at stefanobartoletti.it

@mariosmaselli They are probably vibe coding 😶‍🌫️

When I started sharing the journey of building my portfolio, I expected more people new to the industry, or people learning development and trying to understand how to combine design + dev, to follow along. But that doesn’t really seem to be the case… where are you newbies? I’m trying to reach you 😅

@mariosmaselli @threejs super 💚

@ste_bartoletti @threejs See u there mate

See you in Paris 🇫🇷 @threejs

@mariosmaselli Quite similar to my setup, even if my main CMS right now is Storyblok. But the same approach of building pages by assembling section modules is the same (and yes, I have also learned a lot about how to structure data from the old WordPress days)

I used to work with WordPress for around 10 years, and for the past 6 years I’ve been working with Sanity. Because of that, a lot of my approach to backend architecture is influenced by the things I liked about WordPress and what I felt a flexible backend should provide without constantly needing to restructure things. So after that small intro, let me explain the Sanity setup. By default, on all projects I have a few core schemas already set up: Home Pages Blog Legal Contact Forms The Pages schema is used to create new pages so I can generate as many as needed, and the other main part of the system is the page components, which allow me to build each page modularly. This is basically the core foundation of every project. I’ve also added extra functionality like page previews, so I can review the page I’m working on without needing to publish it publicly. I also have the option to assign parent pages, which makes routing and page hierarchy much easier to manage. I guess that’s mostly it when it comes to the backend. I try to keep things simple and avoid relying on too many plugins, mainly because Sanity unfortunately hasn’t always been very good at keeping all plugins updated. I’ll probably go into more detail later about how a component works from backend to frontend, and what the full lifecycle of a component looks like, but as a general introduction to the backend setup, I think this is enough for today :D

@mariosmaselli Interesting to see that everyone is having the same struggles when talking about personal portfolios, esp about what to put inside and how specific to be with each project, being it full client ones or just side projects

Ok now that we have a clear structure for the homepage, let’s talk about the rest of the pages and what I’m planning to do with each one of them. So just to recap, from the main menu we have: About, Work, and Labs. In addition to that, there will also be Work Detail and Work Case Study pages. Most of the projects I’ll showcase will be relatively simple presentations, mostly focused on imagery. However, I do want to have at least one project where I go much deeper into the process and explain each stage of the work, from Art Direction all the way to Launch, including support and post-launch updates. Doing this level of documentation for every project feels like a bit too much, especially because not every project involved me from the initial concept phase through launch. Some projects were more focused on development, others on animation or frontend implementation, so the level of involvement naturally changes from project to project. I’m still figuring out whether Labs should also include detail pages, because honestly this is one of the most exciting parts of the portfolio for me. I want to start sharing more of my process and experiments publicly. A lot of the time, interesting work never gets seen unless there’s a full website attached to it, and not every project is worth showcasing as a complete case study. But sometimes a single interaction, shader experiment, visual exploration, or technical prototype is valuable on its own. I also think Labs could become the right place to share deeper explorations into things like shaders, WebGL experiments, motion systems, typography tests, or smaller technical ideas that may later evolve into full projects. Ok, enough talking — let me put some visuals to all of this. Also, small update on the homepage: I gave the copy another pass with ChatGPT. English isn’t my native language, and while the original text communicated the general idea, it still wasn’t fully expressing the tone and direction I wanted. ChatGPT helped refine the writing, improve the flow, and better organize the overall line of thought.

@__rockbiter The dark lord of @threejs

And then God said GRASS!! 🤣 It looks great, but I'm still trying to improve the quality of the shadow cast by the grass and PERF as well. If anyone knows some trick... please lmk!!!! 🙃 #threejs #grass #glsl #webgl #shader #light #trail #envmap #fresnel

@Oluwaphilemon1 Impressive, it looks very similar to last year's SOTY by @itsoffbrand and @ffmfedd 🤦‍♂️

How I built with Claude 1. Build the site around speed every animation should feel like acceleration 2. Use bold typography that hits like a racing car entering a corner 3. Add WebGL for the 3D immersive hero section 4. Sharp transitions and cinematic scroll create momentum throughout 5. Balance racing heritage with a playful personal energy 6. Save this if you want a personal brand that moves as fast as you do 🏎️

I love how you ask AI to check for typos and readability/legibility of your email draft, and the proposed edits are randomly adding or removing concepts and twisting the intended meaning.

@studiofreight Beautiful 😍

More coming → Soon

@marcba But I see that you still have a Copilot

Another day where nobody talked about AI at 4000ft

@__rockbiter 👀

Sharing some updates on my recent #threejs experiment I'm working on... Added light projection from the ball to the ground. Follow me for future updates. #light #trail #glsl #webgl #projection

@alvarosabu @tresjs_dev MTJSGA

Is @tresjs_dev becoming popular again? 🥹

Just a month left to @digitdesigndays! Looking forward to meeting other people who will also be attending, if you will be there, let's get in touch!

@edankwan It is an amazing work, no surprise for the awards to be honest

You never really know if people will connect with your work. This one felt even more unpredictable because, compared with the commercial projects we usually do, it was basically a joke. So winning with such a high score was a real surprise. It even scored higher than our own Lusion Site of the Year website. To everyone who voted for us, thank you. It means a lot. And to those who did not, I will remember this. :)

@wesbos Looks like I'm cool

Only cool people can reply to this

🗓️New availability opening up mid-April🗓️ I'm a freelance web developer specialized in high-quality frontends with ➡️Vue/Nuxt ➡️GSAP/Lenis animations ➡️Headless CMS (proud @storyblok MVP) Need help with a landing page, portfolio or other creative website? DM me and let's talk!

@lusionltd 🤯🤯🤯

Over the past year, a lot of the conversation has been around how quickly AI is changing the digital world. At the same time, it made us think about how little has changed in the physical one. Most products are still designed the same way, just with more features layered on top. We wanted to explore a different direction at Lusion. Instead of asking how to add intelligence, we asked what happens if you take things away. What remains when you strip a product back to its core purpose, and design it properly from there. Oryzo is our first attempt at that. It is a physical product, built with a very simple idea of how it should exist and behave. No dependency on external systems, no complexity for the sake of it. Just something that feels considered. Curious to hear what people think. Link is in the comment!

@arzafran Skills as a service?

are skills the future of SaaS?

@mariosmaselli Yes, it really depends on the specific clients and projects. I think that the daily rate is more common for ongoing collaborations

@ste_bartoletti Interesting... because even when I was a freelancer my clients (in most cases agencies) will ask for me also a closed price for a project. It was very rare to work on a daily or hourly rate. Anyway, thanks for the feedback :)

We experimented this year with component-based pricing instead of page-based pricing. The goal: better scoping, better transparency, fewer surprises. 25–30 components = X budget. Simple, in theory. In reality, clients still think in “pages,” not systems. And that disconnect matters. Would love to hear how others are pricing modern web projects.

@mariosmaselli I tend to use daily rate or less often full project price, but I guess it is different between freelance and agency. In your example I guess there is an correlation between comps and pages so you can give client per-page converted price even if internally you base it on comps

@ste_bartoletti Do you still budget by pages then?