An April 2022 Recap
Tags: nextjs, css, career, productivity
Published: 2022-05-13 21:59:34

One of the coolest things I’ve observed while working at [Prismic](https://prismic.io?utm_source=dev.to&utm_medium=referral&utm_campaign=devto_monthly&utm_content=article_title) is seeing how our headless website builder frees devs to do more of what they enjoy. When devs master building with Slices (aka website sections), they can ship a custom website builder experience to their content teams, and then spend their time building and optimizing. They’re not constantly bogged down with requests from content teams or, worse still, broken stuff to fix and maintain. 

With that in mind, we’re creating content that helps developers step into and explore something they love to work on: optimization. 

I get to work with awesome developers to pull this content together, and I’m really proud of all they’ve been doing. Our new motto is that the Prismic blog is a place where devs can go to optimize their skills, stacks, and careers. Here’s a quick round-up of what we published in April:

## [6 Thoughts on Building a Career in Web Development](https://prismic.io/blog/6-thoughts-building-a-career-in-web-development?utm_source=dev.to&utm_medium=referral&utm_campaign=devto_monthly&utm_content=article_title)

Okay, this one came out a little before April, but how could I know about a blog with career advice from Cassidy Williams and not share that with you? From community to your personal brand, she shares some awesome insights based on her experience building a career in tech.

## [12 Discovery Questions to Ask Freelance Web Development Clients](https://prismic.io/blog/discovery-questions-freelance-web-development?utm_source=dev.to&utm_medium=referral&utm_campaign=devto_monthly&utm_content=article_title)

Especially at the outset of a freelance career in web development, one of the most challenging things to do is manage clients. Asking the right questions when starting a project can help the whole process run a lot smoother. Thanks to Coner for sharing these great questions!

## [14 Actionable Tips for Developer Productivity](https://prismic.io/blog/14-actionable-tips-for-developer-productivity?utm_source=dev.to&utm_medium=referral&utm_campaign=devto_monthly&utm_content=article_title)

If you haven’t heard of [Alex Trost and Frontend Horse](https://twitter.com/trostcodes), you’re lucky to have stumbled on this post. He’s one of the most productive and hardworking developers I’ve met, and the tips he shared in this post are things you can immediately do to improve your productivity — in a healthy way. 

## [How to Choose the Best CSS Framework: Understanding Metrics and Context](https://prismic.io/blog/how-to-choose-the-best-css-framework?utm_source=dev.to&utm_medium=referral&utm_campaign=devto_monthly&utm_content=article_title)

Have you ever wondered how different parts of development evolved to where they are today? Anthony Campolo gave us a tour of CSS framework history, and it provides an excellent context for understanding which option might work best for you and your project. 

## [How We Helped Bring You the New Nuxt 3 Link Component](https://prismic.io/blog/how-we-helped-bring-new-nuxt-3-link-component?utm_source=dev.to&utm_medium=referral&utm_campaign=devto_monthly&utm_content=article_title)

[Lucie](https://twitter.com/li_hbr) is our resident Nuxt Ambassador and all-around developer extraordinaire. She spent the first part of this year bringing her RFC for `<NuxtLink>` to life and shared a bit about her experience in this post. We’re all really proud of the work she’s doing, and I can’t wait to see what she does next!

## [Part 3: Striving for Accessibility When Building Components for a CMS](https://prismic.io/blog/accessible-components-in-a-cms?utm_source=dev.to&utm_medium=referral&utm_campaign=devto_monthly&utm_content=article_title)

Accessibility is a topic that’s near and dear to me, and when Alexander Dubovoy proposed a series on it, I was thrilled. As developers, we have a unique perspective of the need and requirements for accessibility on the web. This is the third installment in a series on working with accessibility in Next.js, which takes developers through the unique concerns that arise when we hand websites off to a content team at the helm of a CMS.

There are many more exciting things ahead of us, from a [coding challenge newsletter](https://prismic.io/blog/coding-challenges-newsletter?utm_source=dev.to&utm_medium=referral&utm_campaign=devto_monthly&utm_content=article_title) to a bit of a makeover for our blog. I can't wait to share more next month!