We have mentioned Figma since the beginning of Friction Log as the tool that we used to create assets for the webpage, interestingly enough I haven't used Figma before and decided to try it out.
This post has a smattering of random tools that I didn’t think was appropriate for a full friction log (at least not yet). This is more of a “first-time” impressions post.
I don't recall how I came upon this app but it seemed really compelling. I decided to try it on a trip recently. It's a fun app with some promise but a lot of friction.
Github Codespaces (i.e. VSCode inside Github) is promising. It's remarkable just how portable they've made VSCode. This is a light, quick friction log on a first-time experience setting up Codespaces. More logs will surely come :-)
Friction logs are also great for analyzing end-user platforms. In this log, Rick and Cesar have a fun conversation around Hey.com and it's usefulness.
It's time to update our website that leverages NextJS to the latest release. In this feature experience, I embark on the quick journey of implementing the incremental static regeneration.
With the popularity of the JAM Stack, platforms like Vercel and Netlify have become the go-to way to deploy websites. My first experience had to be to deploy FrictionLog's website in Vercel.
I’ve tried a lot of CMS’s over the years but I specifically wanted to try out using GraphCMS as Friction Log’s headless CMS and I wasn’t disappointed.
I was able to easily spin up a sample project, with a DynamoDB and GraphQL backend, play around with it, make changes, with very little friction. If I would’ve stopped at the introductory tutorial, I think my review would be a little different.
The conventions and philosophy of Tailwind make quick work of converting a design to HTML/CSS.
I’ve always wanted to build something on NextJS. Building out the Friction Log website was the perfect opportunity to do so.