Writing case studies from my work has always been a bit of a struggle for me.
You need to remember what you've done, some insights from previous work, and outcomes. While an outcome could be a link to a live site, the process is interesting as well.
Most of my work now happens inside Claude or ChatGPT, so I made a skill for remembering things: /journal-this.
After each session it writes down insights, decisions, and ideas for case studies and posts.
It saves to one folder outside of any project, one markdown file per day. So I have a single journal of all my work, and I can look up what I did a year ago.
Link in the comment.
@david_visuals_ Eyebrows, serif font with italic in h1, gradient color in titles, numbered sections, ultra detailed graphs and charts - if you don’t have it, you’re good!
@SarpSusuzer Apart from having consistent UX, I think we should dedicate more time to making little quality of life improvements to products. Nothing fancy just some things that speed up your workflow. These are often overlooked
AI can build a Webflow page in minutes.
Keeping it on-brand is the hard part.
Pages drift for multiple reasons:
1. No variables, so the AI guesses colors and sizes
2. Loose class names, so it keeps making new classes
3. No section library, so every page is a new layout
4. No written rules for the AI to follow
If you don't have a solid foundation, whatever you do, you'll end up with a lot of clutter.
Wrote an article about it:
(This article is part of the experiment with PloyAI)
@manali_manek01@_vargaalex Behind the scenes is always interesting for sure! I think not even clients but also designers love to see it. Its like sharing what’s working for us and if you’d like, you can try this workflow too
@k_bachanek Sometimes stakeholder obsession with a speedy delivery of features pressures you into cutting corners. At the same time, you learn how to push yourself and do your best within the limited time you're given
@alidalton If it's also connected to repo with a design system, the prototype can be even closer to the real product. No more guessing which color to use or a button.
Along the way when there is a need it's possible to update the design system with new components.
Webflow horror story.
It was Halloween a couple of days ago, so here's a story about a small UI issue that published a whole new website without any approval.
If you've worked in Webflow, you know you can publish to staging and production. When you work on new pages, you uncheck production in the Designer and expect it to be off everywhere.
In the site settings, that checkbox didn't show the same state as in the Designer.
I was invited to build a few pages for an existing website. After a full day of work, adding new pages and doing mobile breakpoints, I needed to tweak something in the site settings. I did it and wanted to publish right away and send the link to the client. I clicked publish, and then publish again. While it was publishing, I saw the production checkbox was checked.
That was a true Halloween moment. Cold rush down the spine.
I couldn't revert, because that meant redoing everything I'd done that day. The oldest backup was 3 days old.
I reached out to the client immediately. As an apology, I offered a performance optimization: cleaning up old classes and interactions, optimizing custom code, and every other improvement I could make.
Moral of the story: don't rush. Check where you publish.
Never thought I'd enjoy building a website with AI as much as I'm enjoying it now.
While iterating on a page, I could pin comments on elements of the page, like in Figma. Claude goes through all of them one by one. It's like asking another designer to fix things.
One page took about 20 rounds of comments. Some small ones, some big.
The other big win is global changes. Changing the brand color or a heading style is one edit, not 40 class tweaks.
@cedric_design Ai helps to get started. Could be a good start or could steer away from what’s needed and core positioning. So designers will definitely have work in the future :)