Fresh out of the oven

This week we released two new helpers in beta as part of our @prismicio/client package: unstable_htmlAsRichText and unstable_markdownAsRichText. Those new helpers respectively help you convert your existing HTML and Markdown content to Prismic rich text format with flexibility when migrating to Prismic.

Why unstable_?

While carefully tested and capable, the new helpers' APIs, names, and implementations may still change in the future not following SemVer. We will announce in a future update when their APIs become set in stone.

Getting started

You can use those helpers as part of @prismicio/client v7.7 or higher. Learn more about their usage in the updated client technical references.

This week, we've made a small but mighty update to the way you add fields to your slices.

Here's what's new:

• Simplified access: Adding fields is now easier, with a more accessible placement directly within the slice creation process.
• Prioritized fields: The most frequently used fields are now prioritized, allowing you to quickly find what you need.
• Hover previews: Hovering over a field provides a preview of how it will appear in the Page Builder, ensuring your marketing team gets exactly what they need.

These updates are designed to make your workflow more efficient. Check it out 👇

Last quarter, we introduced an improvement to Prismic, allowing you to build slices with multiple repeatable groups of content. Our next step was to develop “advanced groups,” enabling the addition of nested groups within groups.

In the process of designing the solution while talking to developers like you who use Prismic, we realized that groups within groups are complex and do not align with our vision of creating the simplest page builder for marketing websites.

To enhance the editing experience, we decided to focus on the concept of groups and challenge ourselves: can we cover common website elements (80% of use cases) without the complex concept of groups? What if we can bring you specific, out-of-the-box solutions for these common cases instead?

We are starting by focusing on buttons as the first elements. Our aim is to identify improvements that will facilitate easy button creation for both developers and marketers.

After addressing these simple cases, we will revisit the topic to explore solutions for the remaining advanced cases.