Articles

JAMStack Article

The "Muskavation" of <a href="https://twitter.com/cmscritic" target="_blank">Twitter</a> continues, and the social media giant's newly anointed King is forcing many tech companies to reassess their remote work strategies.
Could this mean the end of <a href="https://zoom.us/" target="_blank">Zoom</a> calls in pajamas and board meetings interrupted by cats?
And who, exactly, is resuming their commute back to the office?
While the remote work phenomenon might be in the rearview for many employees, it seems that developers will continue to drive the trend – and even shape its future. This is according to a recent survey published by <a href="https://www.netlify.com/" target="_blank">Netlify</a>, a buzzworthy platform that's powering modern web development.
The company announced the findings last week from its third annual <a href="https://c212.net/c/link/?t=0&amp;l=en&amp;o=3700082-1&amp;h=3410126094&amp;u=https%3A%2F%2Fjamstack.org%2Fsurvey%2F2022%2F&amp;a=%C2%A0Jamstack+Community+Survey" target="_blank">Jamstack Community Survey</a>, the definitive pulse on global trends across the Jamstack web developer ecosystem. An acronym for Javascript, APIs, and Microservices (the "JAM"), <a href="https://www.cmscritic.com/top-jamstack-static-site-generators-for-2021/">Jamstack</a> is an architectural model that decouples the web experience layer from the data and business logic – improving the flexibility, scalability, performance, and maintainability of modern apps. 
"The Jamstack Community Survey is created by the community, for the community," said <a href="https://www.linkedin.com/in/mathias-biilmann-christensen-a5a3805/" target="_blank">Matt Biilmann</a>, co-founder and CEO of Netlify. "The findings will not only help developers learn from their peers but also help business leaders better understand how developers can be change makers within their organizations. They can learn about what tools and processes they need to be most impactful."
Along with prognosticating the future of remote work, the survey also revealed interesting data from developers about Web3, the growth of serverless and edge computing, and where content management systems fit in the mix.
<h2>For developers, remote work isn't going away </h2>
As Covid-19 lockdowns become a footnote in recent history, the impact of remote work is undeniable. In the last two years, it has cemented itself as "the new normal." 83% of developers claim to be working more than half the time remotely, while 76% say they've maintained or increased their frequency of working remotely in the last year.
What's clear in the survey results is that remote has become the preferred way of working for developers. In fact, 87% say they enjoy remote work – and an astounding 55% said they would quit their jobs if forced to return to an office. Someone should send Musk the memo. 
According to the survey, 33% of respondents have already changed jobs in the last year, increasing the likelihood that developers will not hesitate to "job-hop" if they need to. It's worth noting that remote work flexibility and career growth opportunities were the most frequently cited reasons for leaving a job, followed by compensation.
Clearly, developers value freedom a little more than finances. At least right now. 
<h2>Web3 hope... or hype?</h2>
<a href="https://en.wikipedia.org/wiki/Web3" target="_blank">Web3</a> has captured the tech zeitgeist throughout 2022, with <a href="https://www.bloomberg.com/news/articles/2022-11-18/bitcoin-responds-to-ftx-contagion-by-heading-for-a-weekly-gain" target="_blank">Bitcoin</a> starting the year at around $50,000 to the beleaguered <a href="https://www.cnbc.com/2022/11/15/ftx-says-could-have-over-1-million-creditors-in-new-bankruptcy-filing.html" target="_blank">FTX exchange just declaring bankruptcy</a>. 
While the concept of a new web composed of decentralized blockchains (DeFi) is intriguing, Web3 has also been the target of mistrust and skepticism. According to the survey, 7% to 10% of developers have tried technologies like cryptocurrencies and non-fungible tokens (NFTs), but only 3% report using them regularly.
To help gauge the hope and the hype for the future, Netlify also asked developers to share their general attitudes toward Web3. The findings were mixed: 42% of developers either don't know what Web3 is (or don't care), while 31% had negative feelings about it.
Bottom line: the survey shows that Web3 is still a long way from mass adoption, and developers continue to be slow and cautious about embracing it. 
<h2>Building better web experiences with serverless and edge </h2>
Jamstack is continuing to evolve the modern web by helping developers build more dynamic websites. Developers are relying on cutting-edge cloud technologies to achieve this, including <a href="https://goserverless.solodev.com/" target="_blank">serverless computing</a>.
To that end, Netlify's 2022 Jamstack report found that serverless is now officially mainstream: 70% of developers report using it, up from 46% last year – a jaw-dropping adoption rate. Meanwhile, some 47% of developers are experimenting with edge dynamic sites, a sign of the continued innovation happening at the network edge.
Serverless technology is enabling Jamstack websites to grow their capabilities while maintaining the simplicity of development and deployment that is the hallmark of the platform.
<h2>Web frameworks and programming languages </h2>
To build dynamic web apps, developers require flexibility. They want to choose whichever web framework best suits their needs, and they now have plenty to choose from.
Among the landscape of options, <a href="https://www.cmscritic.com/uxpin-merge-review-sync-react-components-with-prototypes/">React</a> continues to be the overwhelming favorite, with 71% of developers reporting they build with it – 3% more than last year.
Riding React's popularity is <a href="https://www.cmscritic.com/top-jamstack-static-site-generators-for-2021/">Next.js</a>, which uses React and is the overall most popular web framework. In fact, 1 in 2 developers (47%) say they have built sites using Next.js in the last year. However, competition remains strong: newer entrants like Astro (11%) and SolidJS (6%) have had promising starts, and Remix (10%) and Sveltekit (15%) have grown steadily year over year. Vite saw an 18% increase since 2021, with a third (32%) of developers using it.
"We're thrilled that a third of the Jamstack community is embracing Vite as they build for the modern web," said Matias Capeletto (aka Patak), from the Vite Core Team. "Vite's usage more than doubled in a year, thanks to being adopted by many modern app frameworks and web tools. The pace of innovation continues to accelerate. Vite's Rollup-based Plugin API allows the ecosystem to share solutions and collaborate in ways we haven't seen before."
Regarding programming language preferences, the great <a href="https://www.typescriptlang.org/" target="_blank">TypeScript</a> migration continues, with usage growing 110% in the last two years. 21% of developers now call TypeScript their primary programming language, while the number of developers who say the same about JavaScript has dropped from 63% to 53% in the same timeframe. However, JavaScript isn't going anywhere soon: 96% of developers say they use it, even if it isn't their primary choice.
<h2>The CMS of choice is still WordPress, but... </h2>
In the world of Content Management Systems (CMS), things continue to evolve. <a href="https://www.cmscritic.com/wordpress-keeps-classical-editor-alive-acquires-frontity-to-expand-headless-capabilities/">WordPress</a> is still by far the biggest winner, with 37% of devs saying they use it – even though their reported satisfaction with it is lower than many alternatives.
Interestingly, WordPress as a stand-alone CMS is losing share. At the same time, 22% of respondents said that they're using WordPress as a headless API to power a Jamstack website – and that number is growing.
<a href="https://www.cmscritic.com/storybloks-cms-report-shows-enterprises-are-still-scared-of-omnichannel-content-experiences/">Storyblok</a>, a newcomer to the survey, reached 9% usage amongst respondents, a strong showing for the up-and-coming <a href="https://www.cmscritic.com/top-free-headless-cms-platforms/">headless CMS</a>. 
"More and more developers realize the potential of headless architecture in building and deploying better web experiences," said Dominik Angerer, CEO and founder of Storyblok. "At the same time, we believe that the content team utilizing the power of Jamstack with a headless CMS like Storyblok gets the content tools they need and love for creating great experiences on the frontend."
To explore the findings in more detail, you can view the <a href="https://c212.net/c/link/?t=0&amp;l=en&amp;o=3700082-1&amp;h=4098052836&amp;u=https%3A%2F%2Fjamstack.org%2Fsurvey%2F2022%2F&amp;a=full+methodology+of+the+survey" target="_blank">full methodology of the survey</a>.
<h2 class="wcag-arialevel-3">About Netlify</h2>
Netlify is the platform your developers love for building highly-performant and dynamic websites, e-commerce stores and web apps. By uniting an extensive ecosystem of technologies, services and APIs into one workflow, Netlify unlocks new levels of team productivity, while saving time and money. As pioneers of the Jamstack movement, Netlify brings together all modern web frameworks, serverless functions and edge computing into one platform to deliver unmatched user experiences. Millions of developers and businesses build with Netlify, from Fortune 500 companies like Unilever and Verizon to companies changing our digital experiences like Peloton and Twilio. Get started for free at <a href="https://c212.net/c/link/?t=0&amp;l=en&amp;o=3700082-1&amp;h=2291442546&amp;u=https%3A%2F%2Fwww.netlify.com%2F&amp;a=netlify.com" target="_blank">netlify.com</a>.

Netlify Publishes Jamstack Community Survey, Shows Developers are Driving the Future of Remote Work

cms-critic-staff

Image of the Netlify logo with the icon and text against a dark blue background.

Strapi, an open source headless CMS, just the release of <a href="https://strapi.io/" target="_blank">Strapi v4</a>. The platform's latest version offers a reworked core, allowing users to expand Strapi with plugins and boost API performance with greater ease. It also sports a slick UI and a new design system that's worth diving into.
The latest version of Strapi follows several critical upgrades with key features. Last year, Strapi introduced a stable Strapi v3 with <a href="http://strapi.io/features/custom-roles-and-permissions" target="_blank">role-based access control</a>,<a href="https://strapi.io/blog/announcing-a-new-draft-and-publish-feature" target="_blank"> draft and publish features</a>, and <a href="https://strapi.io/blog/v3-5-sentry-plugin-sso-authentication" target="_blank">SSO authentication</a>. Shortly thereafter, the company launched its v3.6, which introduced free content <a href="https://www.cmscritic.com/strapi-headless-cms-announces-v3-6-with-free-content-internationalization/" target="_blank">internationalization</a>. 
According to Strapi, its <a href="https://www.cmscritic.com/top-free-headless-cms-platforms/" target="_blank">headless CMS</a> is designed to power experiences across websites, mobile applications, and IoT devices, and is an ideal fit for the <a href="https://www.cmscritic.com/top-jamstack-static-site-generators-for-2021/" target="_blank">JAMstack</a> (JavaScript, API, and Markup). Strapi's headless posture also enables it to power front-end frameworks such as React, Gatsby, Vue.js, Next.js, and other static site generators. It also supports multiple databases as well as both REST and GraphQL APIs. 
With more than <a href="https://github.com/strapi/strapi/" target="_blank">40 000+</a> Github stars, 600 contributors, and 3.5 million+ downloads, Strapi is the fastest-growing <a href="https://nodejs.org/en/" target="_blank">Node.js</a> CMS. They held their first online global user conference, <a href="https://conf.strapi.io/" target="_blank">StrapiConf</a>, in April of 2021, with more than 2,500 live attendees. The company's <a href="https://strapi.io/blog/save-the-date-strapi-conf-2022" target="_blank">2022 conference</a> will be held March 16-17.
<h2>What’s new in Strapi 4?</h2>
New Design System 
Strapi got a complete makeover, primarily around its visual aesthetics and navigation. This includes a refreshed admin UI, which improves accessibility to the admin panel and makes the entire flow more efficient.
<img src="https://cmscritic.com/ms-content/uploads/2021/12/strapi_v4_screenshot_5cb222faff-e1639090146670.png" alt="New Admin Panel" />
Along with the updated admin panel interface, Strapi released the first version of its new <a href="https://design-system.strapi.io/" target="_blank">Strapi Design System</a> with the goal of enabling everyone to extend and customize their Strapi applications with plugins. To ensure design consistency and provide the best experience to users, Strapi created a component library for plugin developers. 
<img src="https://cmscritic.com/ms-content/uploads/2021/12/components_a32c1d133a-e1639090227330.png" alt="New User Interface" />
In the new design, Strapi focused on making all the pieces of the interface consistent. They also increased the contrast ratio and created elements with adaptive sizes to render the UI more accessible. 
New API to create plugins without pain
Strapi aims to scale its ecosystem and let users choose among a wide variety of high-quality plugins. Conversely, the company also wants to give plugin creators a bigger stage to showcase their work. Overall, Strapi seems focused on giving users more control to customize and integrate with other tools.
Strapi's plugin capabilities have evolved from complex to simplified. For example, in Strapi v3, plugins were loaded based on a file structure, requiring users to configure multiple files. In v4, Strapi took a more programmatic approach, allowing plugins to have their own file structure. Instead of configuring multiple files, plugin developers only need to configure two files at the root of the package:
<pre>strapi-server.js for the Server.
strapi-admin.js for the Admin panel.</pre>
While v3 plugins won’t be compatible with v4 and will require migration, this is a big leap in overall functionality. 
More powerful REST and GraphQL API
Strapi added new features to its content API such as pagination, a better filtering format, and the ability to choose what relations to load. Structurally, the Content API and the Admin API are now split, providing greater control over each channel. Overall, Strapi seems more invested in enhancing the value of their REST and GraphQL APIs, both of which deliver on its promise as a headless CMS platform. 
<h2>Try Strapi 4 </h2>
There are a number of other noteworthy changes in Strapi v4. To see the complete list, head over to their v4 announcement page. 
Strapi says they will continue supporting v3 and fixing critical bugs for at least the next six months. However, they will stop delivering new features for v3, and they encourage users to upgrade to v4 for all new projects. 
One thing we'll say is that Strapi makes it very easy to get started on its platform. Once <a href="https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/cli.html#preparing-the-installation" target="_blank">Node.js and npm are properly installed</a> on your machine, simply copy and paste the following command line in your terminal to create your first Strapi v4 project:
<pre>npx create-strapi-app

my-project --quickstart</pre>
<h2>About Strapi</h2>
<a href="http://strapi.io" target="_blank">Strapi</a> is a leading open-source headless CMS, giving developers the freedom to use their favorite tools and frameworks while helping editors easily manage their content and distribute it to any device or channel. The remote-first company has offices in Paris and San Francisco, and is scaling its team globally. Strapi, Inc. is venture-backed by Index Ventures, Accel, and Stride VC, as well as notable angel investors and open-source experts.

Strapi Releases v4 of Headless CMS, Enhances Plugins and API Performance

paris-tuzun

When it comes to content management systems, there's one platform that makes headless "like butter."
Of course, we're talking about <a href="https://www.cmscritic.com/dynamic-landing-pages-with-components-and-buttercms/" target="_blank">ButterCMS</a>, an aptly-named brand that's been making solid gains over the years, particularly around the rise in popularity of <a href="https://www.cmscritic.com/top-jamstack-static-site-generators-for-2021/" target="_blank">JAMstack</a> and MACH-related microservices. The platform powers static site generators like <a href="https://www.cmscritic.com/gatsby-unveils-v3-0-cloud-hosting-and-more-at-gatsbyconf-2021/" target="_blank">Gatsby</a>, for example – and makes it incredibly easy to connect their CMS to a fast, secure, high-performing frontend site.
Recently, the company announced some slick new additions to its <a href="https://buttercms.com/features/#fastcontentupdate-localization" target="_blank">content localization capabilities</a> that aim to simplify the workflow, allowing users to translate content to any language right within the Butter UI.
Not to spread it on too thickly (pun intended), but this is exactly the kind of feature that CMS platforms need to serve global initiatives. The new functionality empowers international teams collaborating on projects to access information and quickly translate it for their specific region – all with just a few clicks. It also prevents any duplication of effort, allowing projects to be completed faster and more efficiently.
We've got more details below, but we'll butter you up with a little something extra: a brief Q&amp;A with <a href="https://www.linkedin.com/in/lumetta/" target="_blank">Butter's CEO, Jake Lumetta</a>. Read what the company's founder had to say about their new localization capabilities, composable CMS, <a href="https://www.cmscritic.com/top-jamstack-static-site-generators-for-2021/" target="_blank">JAMstack</a>, and the <a href="https://www.cmscritic.com/top-free-headless-cms-platforms/" target="_blank">headless</a> frontier. So grab your toast and dig in.
<h2>A new tool for clients with international teams and topics</h2>
There's no question that the Covid-19 pandemic has exacerbated the <a href="https://www.forbes.com/sites/carolinecastrillon/2021/12/27/this-is-the-future-of-remote-work-in-2021/?sh=6f9e6f441e1d" target="_blank">growth of remote work</a> – and consequently, the rise of remote teams. This has been felt on a local level, but international teams have been working from a distance for quite some time.
According to Butter, companies with growing international interests need products that make working with their remote teams easy and effective. As such, their new localization enhancements are targeted at taking the work out of managing distributed teams, specifically marketers and translators across the globe.
The expanded set of features is a big leap forward in both speed and convenience for ButterCMS customers, giving them the option to import content in English – or any other language – as a base template to work from for any project. Once this base version is created, individual users can then copy that content and translate it for any region using simple features in the navigation menu.
<h2>Butter CMS localization: process and options</h2>
On a more granular level, the process of importing and translating content in ButterCMS is designed to be very intuitive. For example, when modifying content for a specific region, a user can select “Copy From” in the menu, and import existing content from any other locale. There's also a scrollable drop-down menu that includes all the languages that have been configured in a user's account, making it easy to select options on the fly.
After the base content has been imported, the content can be translated manually by local experts, via API by Google, or through another third-party service of your choice. Another point of convenience: regions that have already been translated are highlighted for quick recognition.
<img style="max-width:706px" src="https://cmscritic.com/ms-content/uploads/2021/09/image001.jpg" alt="localization settings - languages dropdown" />
There's no limit to the number of languages you can support. That means your team members from any corner of the world can translate content to accommodate local languages and meet cultural-specific content requirements.
From a permissions perspective, another new feature is the ability to <a href="https://buttercms.com/kb/enabling-localization-and-creating-localized-content" target="_blank">control editing privileges</a> for various regions at the user level, allowing teams on the ButterCMS Enterprise plan to ensure that only approved members in a designated region can make changes to their specified content. This feature streamlines the interface for international teams, minimizes confusion, and prevents unauthorized changes.
<img style="max-width:502px" src="https://cmscritic.com/ms-content/uploads/2021/09/image003.gif" alt="locale access checkboxes" />
<h2>Additional CMS features and updates</h2>
For Butter, "convenience" has always been a key attribute. Their interface is familiar and intuitive, making it easy to learn and use. Along these lines, they've made several recent updates that improve the content production process – making it more flexible and less time-consuming.
For example, there’s a new <a href="https://buttercms.com/features/#fastcontentupdate-preview-changes" target="_blank">resizable preview panel</a> that lets users preview live content inside the same window where they are currently editing. You can also use the same click-and-drag functionality to control the size of the API explorer window. This prevents the hassle of toggling back and forth between windows while working.
<img style="max-width:600px" src="https://cmscritic.com/ms-content/uploads/2021/09/image004.gif" alt="Resizable review panel" />
<a href="https://buttercms.com/features/#flexiblecontentmodeling-components" target="_blank">Reusable components</a> help keep the development process as simple as possible with a unique component picker tool, allowing marketers to build dynamic landing pages using pre-defined, pre-styled components. It’s a powerful feature for building dynamic landing pages without relying on a developer.
Another is Butter’s pre-configured <a href="https://buttercms.com/features/#flexiblecontentmodeling-blog-engine" target="_blank">blog engine</a>, which makes it really easy to add an SEO-friendly blog to an existing website or app. It supports all of the popular frontend frameworks, with drop-in SDKs for any language.
Users can also take advantage of Butter's native <a href="https://buttercms.com/features/#medialibrary" target="_blank">Media Library</a> to host all the files necessary for a blog, app, or website. The Media Library can hold images, videos, audio files, PDFs, and more – and all files are distributed securely via <a href="https://aws.amazon.com/cloudfront/" target="_blank">Amazon CloudFront’s CDN</a>.
<h2>Summary and pricing</h2>
ButterCMS has just upped its game with some great content localization enhancements. Whether you’re managing content for a mobile app, a hybrid web app, a static site, or just a blog, the platform provides an array of tools and features to improve your development and marketing efforts.
When it comes to pricing, there are several <a href="https://buttercms.com/pricing/" target="_blank">plans</a> available that meet the needs of everyone – from freelancers and startups to enterprises and agencies – and can be scaled as your organization grows.
<h2>Q&amp;A with Jake Lumetta, CEO and founder of ButterCMS</h2>
CMS Critic had a chance to connect with Butter's CEO and founder, Jake Lumetta. We asked about their growth opportunities, composable and reusable CMS trends, and what makes their headless CMS stand out in the crowd.
<hr />
CMS Critic (CC): With localization being such a key focus in your recent update, it seems fair to say that ButterCMS is growing globally. What are your core markets? Where are you seeing the most growth internationally?
Jake Lumetta (JL): Butter has customers around the globe and in every vertical you can imagine.  If you need to manage content for a modern, highly performant application, then Butter is a great fit for your team. We've seen amazing growth in e-commerce, marketplaces, SaaS, e-learning, and financial services.
CC: Composable and reusable components are becoming essential to a CMS. Can you tell us more about your component strategy? What aspects are low code/no code? And how customizable is the framework?
JL: We heard early on from our customers that they wanted to build with components in Butter.  We built a field type called Components which enables our users to group related fields together in an intuitive way. A simple example might be an SEO component that contains all SEO meta information you might want to control for a page.  Butter Components work nicely alongside the concept of reusable components for your Front-end.  Design and marketing can work hand in hand to determine and build out beautiful and customizable experiences using Butter Components. We've made using Components really intuitive for non-developer users with another concept called a Component Picker as well. This allows any marketers to build out a custom, unique page or section of a website or mobile app using any components that they need.
CC: Headless is fast becoming the focus of the CMS market. What would you say is Butter’s most unique advantage when considered against the landscape of options – particularly those that are growing rapidly in the JAMstack?
JL: One of Butter's unique advantages is our laser focus on superior customer support and experience. Our customers want to get their hands on the product and quickly get a proof of concept running with their preferred tech, and we allow every person to easily do that. Our Customer Success team aims to promptly support all folks at any stage of using Butter. We provide resources for learning, using, and scaling the use of Butter so that people can answer their own questions quickly. Our product is also simply more intuitive than most on the market – for both developers with our straightforward API and for marketers with our intuitive and clean interface.
<h2>About ButterCMS</h2>
ButterCMS offers a modern content management solution that helps companies across several markets tackle projects and manage content with ease. Their API-driven headless CMS has enjoyed strong success in several verticals, including e-commerce, agencies, SaaS, and marketplaces. Butter offers extensive documentation and a convenient API explorer interface for quick and painless integration with any application or website. If you need additional help, they offer live, personalized support for all clients.

New Content Localization Capabilities from ButterCMS: Q&A with CEO Jake Lumetta

More WordPress in the press – and the operative word is headless. 
We're covering a couple of big announcements today that are certain to have lasting impacts on the WordPress community. What's clear is that <a href="https://automattic.com/" target="_blank">Automattic</a>, the company that owns WordPress, seems to be listening intently to its users – and gearing up to challenge the <a href="https://www.cmscritic.com/top-free-headless-cms-platforms/" target="_blank">headless CMS marketplace</a>.
Without further ado, (don't) stop the presses...
<h2>The Classical Editor isn't being laid to rest – yet</h2>
It's not hyperbole to say that the introduction of <a href="https://www.cmscritic.com/gutenberg-2-years-later-is-wordpress-better-off/" target="_blank">Gutenberg</a> in 2017 caused widespread uproar across the WordPress community. And why not? The Classic Editor allowed you to create and manage your content in an ultra-simple way, almost like a word processor. This simplicity is also what powered WordPress to market dominance. 
In a race for parity with other page editors such as <a href="https://www.wpbeaverbuilder.com/" target="_blank">Beaver Builder</a>, <a href="https://www.elegantthemes.com/gallery/divi/" target="_blank">Divi,</a> and <a href="https://elementor.com/" target="_blank">Elementor</a>, WordPress <a href="https://www.cmscritic.com/gutenberg-2-years-later-is-wordpress-better-off/" target="_blank">released Gutenberg</a> – their answer to a block-based editing experience. Unfortunately, the Classical Editor was destined for demise, and WordPress scheduled an official sunset on December 31, 2021.
The Gutenberg release has been a bumpy road for users as they struggled to adapt. That said, things are improving: over the last few years, WordPress has worked steadily on Gutenberg, releasing updates every two weeks with <a href="https://www.cmscritic.com/cms-monthly-recap-salesforce-completes-acquisition-of-slack-contentsquare-accelerates-ml-capabilities-and-more/" target="_blank">cool new features</a>. 
While many WordPress users appreciate the evolution of Gutenberg, the Classical Editor retains a fierce and loyal following. Now, it seems that the voice of the community is driving change. In a bold move, WordPress has agreed to <a href="https://wordpress.org/news/2021/08/an-update-on-the-classic-editor-plugin/" target="_blank">continue supporting the Classical Editor for another year</a>. They said it was" the right call for the project as well as the community." 
Personally, we think it's the right call as well. Change can be challenging, and users have the most valuable voice in defining a product's horizon. Perhaps WordPress could have metered their timetable based on community input, allowing them to better read the tea leaves. That said, if there's one constant to change, it's that people will always resist it on some level. 
We'll be monitoring the community feedback as things unfold.
<h2>Frontity joins WordPress, goes headless</h2>
<a href="https://frontity.org/" target="_blank">Frontity</a>, the open-source <a href="https://reactjs.org/" target="_blank">React</a> framework for WordPress, has been acquired by Automattic, the parent company of WordPress. Their team will contribute to the WordPress open-course project and focus on the Gutenberg editor – improving the blocks and themes in addition to making the WordPress sites more performant.
In 2019, Frontity launched their open-sourced Frontity Framework as a way to ease the integration between WordPress and React for building websites. This doesn't mean they will push React to WordPress; rather, the unification will help improve the <a href="https://www.cmscritic.com/updates-on-wordcamp-2021-wordpress-5-8-beta-details-and-gutenberg-enhancements/" target="_blank">full-site editing</a> developer experience and contribute to WordPress' front-end tooling, performance, and UX. 
There's no question that <a href="https://www.cmscritic.com/tag/headless/" target="_blank">headless CMS</a> has exploded in popularity. With traditional (or coupled) CMS platforms, the content management back-end is completely tied to a website's front-end. This effectively limits content creators and developers just to the website pages and templates that are managed and rendered in the system itself. 
With a headless CMS, you are truly "channel agnostic." That means you can manage content via the <a href="https://www.cmscritic.com/top-jamstack-static-site-generators-for-2021/" target="_blank">JAMstack</a> (JavaScript, API, and Markup) with different front-end static site generators using <a href="https://reactjs.org/" target="_blank">React</a> or <a href="https://vuejs.org/" target="_blank">Vue</a>. But the omnichannel only begins at the website layer: with a headless CMS, you can manage content on a wide range of endpoints, from <a href="https://www.storyblok.com/mp/headless-as-digital-signage-software" target="_blank">digital signs</a> to <a href="https://www.luminary.com/blog/serving-content-to-iot-devices-with-a-headless-cms" target="_blank">wearable tech to IoT devices</a>. The possibilities are endless. 
When we think of a traditional CMS, the first thing that comes to mind is WordPress. While it powers more than 40% of all websites on the internet, it's still considered a traditional CMS as its architecture links the front-end (HTML templates, Javascript) to the back-end via a database (MySQL). However, in recent months, WordPress has signaled a deepening investment in headless delivery, particularly with their Gutenberg initiatives. The Frontity acquisition codifies this mission by introducing a static site generator with serverless pre-rendering to the WordPress ecosystem.
"I believe there's still a lot that we can learn from decoupled systems, and we can incorporate those learnings into WordPress itself as we emphasize performance, flexibility, and ease of development," <a href="https://ma.tt/2021/08/frontity-to-join-automattic/" target="_blank">said Matt Mullenweg,</a> founder of WordPress. "I look forward to Frontity joining WordPress and channeling their efforts into the WordPress APIs, documentation, and Gutenberg's full-site editing tools." 
<a href="https://frontity.org/blog/announcing-frontitys-e1m-funding-round-with-automattic-and-k-fund/" target="_blank">Automattic's 2020 investment in Frontity</a> opened the door for this opportunity, helping both organizations to realize the alignment around their vision. The unification will shift things towards decoupled architectures in the coming years, and React will play a key role in WordPress to build modern digital experiences.

WordPress Keeps Classical Editor Alive, Acquires Frontity to Expand Headless Capabilities

WordPress, Frontity, and React logo icons

<h4>In our exclusive Q&amp;A with Sanity founder and CEO Magnus Hillstead, we discuss the current state of the CMS market, the advantages of headless, and what's ahead for the structured content platform. </h4>
<hr />
After a year of hyper-accelerated digital transformation, the content world might feel a little, well… unruly.
Throughout the Covid-19 pandemic, companies feverishly raced to adapt in a contactless, eCommerce-driven economy, experiencing a decade of acceleration in a matter of months – an effect <a href="https://www.mckinsey.com/business-functions/strategy-and-corporate-finance/our-insights/five-fifty-the-quickening">McKinsey</a> christened as "The Quickening."
At the same time, the reliance on content has exploded. Now, with billions of websites and apps floating in the ether, the task of managing dynamic content and digital experiences across a growing multitude of screens and endpoints has become nearly insurmountable.
But the aptly-named <a href="https://www.sanity.io/">Sanity</a> – a San Francisco/Oslo-based SaaS startup – is betting that their innovative platform for structured content will help bring calm to the chaos.
Today, the company announced that it has raised $39 million in Series B funding, becoming the latest venture in the <a href="https://www.cmscritic.com/tag/headless-cms/">headless CMS</a> and DXP ecosystem to acquire significant investment in recent months. In fact, they just completed their Series A in October of 2020 <a href="https://techcrunch.com/2020/10/14/sanity-a-platform-to-build-and-manage-content-flows-on-sites-raises-9-3m-from-ev-williams-threshold-and-more/">for $9.3 million</a>, codifying the confidence around their growth potential.
Over the past year, Sanity has tripled its customer base and doubled its revenues while broadening a portfolio of notable brands, including Unilever, National Geographic, Figma, and others. The company has also doubled the size of its team in the same timeframe.
<h2>A compelling stable of investors</h2>
Founded in 2018, Sanity has experienced a meteoric rise with some impressive investment. This latest round, led by <a href="https://iconiqgrowth.com/">ICONIQ Growth</a> – with additional venture capital from <a href="https://leadedge.com/">Lead Edge Capital</a>, <a href="https://threshold.vc/">Threshold Ventures</a>, <a href="https://www.heavybit.com/">Heavybit</a>, and <a href="https://allianceventure.com/">Alliance Venture</a> – brings Sanity’s total funding to a tidy $51.8 million.
It’s worth noting that ICONIQ Growth General Partner <a href="http://www.pepperspectives.com/p/about-doug-pepper.html">Doug Pepper</a> has joined the board, codifying the overall confidence in their growth potential. Pepper was the first investor in <a href="https://business.adobe.com/products/marketo/adobe-marketo.html">Marketo</a> before its acquisition by <a href="https://www.adobe.com/">Adobe</a> for $4.75 billion in 2018 and has a track record of early bets on strong B2B software players like <a href="https://www.cmscritic.com/canva-button-gives-cms-users-integrated-graphic-design-tools-for-visual-content/">Canva</a>, <a href="https://www.braze.com/">Braze</a>, <a href="https://www.datadoghq.com/">Datadog</a> and <a href="https://airtable.com/">Airtable</a>.
“Sanity has created the hero product for building innovative product experiences, with an impressive developer-oriented approach to content delivery and a personalized product experience that breaks down silos for content creators, marketing, and developer teams," said Pepper. "We're excited to support the Sanity team as they enter this next phase of growth.”
<h2>Rethinking CMS in a world of siloed data</h2>
One of the biggest challenges facing brands in the digital age is the gap between customer expectations and reality. According to <a href="https://www2.deloitte.com/si/en/pages/strategy-operations/articles/changing-consumer-digital-marketing-impact-Covid-19.html">Deloitte</a>, brands face a challenging disconnect as users access multiple touchpoints throughout the purchase experience. While 75% of customers expect consistent experiences, 58% feel like they’re communicating with a number of different divisions – and not one company.
This lack of cohesion is forcing brands to rethink the role of CMS and embrace a new philosophy around content as data. Sanity’s vision to provide structured content comes as businesses look to redefine their digital customer interactions and break the silos that exist across channels.
Sanity positions itself as a “fast-growing alternative to the traditional CMS,” uniquely treating content as data. By storing resources in their <a href="https://www.sanity.io/docs/datastore">Sanity Content Lake</a>, organizations can effectively de-silo their content – making it available for both collaboration and global distribution. By leveraging APIs, users can manage their text, images, and other media in a unified platform and build engaging digital experiences in real-time.
Sanity also enables teams to collaborate on content, design, and code in parallel, allowing them to achieve velocity and ship better products faster. Editors are also able to work more efficiently in customized editing environments built on Sanity’s open source <a href="https://www.sanity.io/docs/sanity-studio">Content Studio</a>, which developers can customize and extend with their own React components.
<h2>Q&amp;A with Magnus Hillstead</h2>
CMS Critic had an opportunity to connect with <a href="https://www.linkedin.com/in/magnushillestad/">Magnus Hillstead</a>, the founder and CEO of Sanity. He shares some of his views on the CMS market, the value of being headless, and what his company is excited about.
<hr />
CMS Critic (CC): How would you describe the overall CMS market in 2021? Where are the gaps from your perspective, and how does Sanity address them?
Magnus Hillstead (MH): In 2021, content is moving beyond websites and mobile applications. Content is reshaping into a web of information that is structured, contextual, and reusable. The CMS industry comes from a web perspective and has partly broadened out to support mobile applications. The rise of JavaScript and new web frameworks has driven a trend of improved customer experience for both marketing and eCommerce. However, as customers are increasingly getting their product experience from digital content, the requirements and opportunities for making amazing customer experiences are growing.
This creates a shift in how organizations work with content. As digital channels become integrated parts of the product experience, the CMS needs to transform to be a part of the product stack and support organizations in extending their product experiences.
We believe that the market has just seen the first increments of a much larger motion. Having content available on an API is table stakes in 2021. Mature digital organizations should require more from their content solutions. Content should no longer be stuck in HTML silos at the edge of organizations, but rather structured, shared and reused across the organization. Organizations should be able to integrate product, customer, and transaction data together with content in order to create better product experiences.
This is the gap Sanity closes. By treating content as data, we fully decouple it from design considerations. Content can be used as a single source of truth for driving product and marketing operations. Rich data models allow faithful integrations of content systems and other data sources, allowing the enrichment and decoration of the content for better customer experiences.
This is what Sanity is all about – high-fidelity data models, real-time event-driven system synchronization, and custom user interfaces for optimal content operations for modern content teams.
<hr />
CC: You mention that Sanity is an alternative to CMS. As an API-driven ecosystem, how would you say Sanity differs from headless CMS platforms?
MH: Sanity treats content as data. Content is structured and programmatically approachable for both reading and writing through real-time APIs. This enables content to be seamlessly interoperated with other sources of truth and used to better express content in context for the various applications and situations organizations communicate to their customers.
Our user interface is open source and meant to be customized and extended by the end-users. Developers can thus create the optimal content model and user interface that the organization needs, fast and with great tools for further development and iteration as their business needs develop.
In a decoupled world, all systems need to be headless, i.e. separate the presentation layer from the content platform. But being headless is not enough. Most headless CMSes are semi-monoliths with code extensions that still treat content as a situation-specific asset, integrating content and design. But they fail to treat content as data and provide a platform that centers around structured content and enables organizations to leverage a programmatic approach to content.
Sanity, therefore, stretches far beyond web content management. We provide a platform for structured content, that enables organizations to treat content as a single source of truth in any application, device, or channel.
By properly separating content from design, you avoid the typical CMS migration every time you want to iterate on your digital surface. Our content platform is meant to be iterated on as your content workflows and digital applications change, without having to rework or migrate the content itself.
<hr />
CC: Would you say Sanity is focused more on the developer as opposed to ContentOps roles, such as marketing?
MH: No, not at all. In fact, Sanity enables developers to create a content platform that bends around the organization, instead of a CMS that the organization has to bend around. This provides much better tools for working with content for the various content creators and organizers.
At Sanity, we believe in finding the general high-level description of what content management systems need to do in organizations. We then carefully express this as high-level APIs that developers can use to build optimal collaborative editing experiences.
Our solution has state-of-the-art multiplayer collaboration, social presence, and per-field rollback where you can see that someone on your team mistakenly changed the hotspot of an image last Wednesday and amend it. All made to enable content creators to collaborate seamlessly as they iterate on content and presentations.
<hr />
CC: As a content platform, how does personalization play into your strategy?
MH: Many of our customers use Sanity to personalize content for their various audiences, and most of the others have plans to do so in the near future.
The rich data models offered by the Sanity Content Lake let content strategists add personalization at exactly the level it is needed. Variants are expressed where you need them, from a single field, to sets of fields to entire documents. As such: personalization is just a special case of content variants like localization or A/B testing.
When it comes to delivering personalization to web users we see a variety of solutions that integrate well with Sanity, from Uniform to Optimizely. Sanity delivers the content and the metadata and seamlessly integrates with such solutions.
<hr />
CC: How are you leveraging AI and automation across your horizon? For example, your asset pipeline and editorial workflows appear to provide some dynamic features. Is AI playing a role here (or elsewhere)?
MH: Sanity is an ideal use case enabled by various forms of AI. As all data is structured and programmatically available, Sanity can handle content and contextual metadata that is key for enabling machine learning.
We do not develop machine learning models for our users out-of-the-box. There is a range of third-party solutions that our users can integrate into their Sanity platform and enable machine learning algorithms on text and images stored in Sanity.
We think that we are only seeing the start of these kinds of solutions and that our key value proposition is to seamlessly integrate with your solution of choice, creating a state-of-the-art platform that enables the best AI for your content.
<hr />
CC: Any innovation on the horizon that you can hint at? What are you most excited about?
MH: We’re excited about a lot of things. We’re excited about how our customers are picking up the idea of content as data and using it to break out of the CMS mode, remove internal silos, and create wider, more holistic digital experiences for their customers. They’re extending their products with digital experiences that drive customer adoption and engagement.
We believe that the world will significantly change its view on what content is and how it should be used in the organization going forward. Content should increasingly be served from a single source of truth and reused across the organization.
We also believe that the future content platform not only powers classic digital presentation layers like web and mobile, but that we will see an increasing use of our content platform as a backend to any application that needs a dynamic, versatile and scalable solution instead of having to build their own in-house.
<h2>About Sanity</h2>
Sanity treats content as data so teams can create transformative digital experiences. Developers use Sanity’s APIs to build optimal editing workflows and share content between systems to increase digital velocity. Our mission is to be the platform for all content - a single place to interconnect, store, author, collaborate, and distribute. Dual-headquartered in San Francisco and Oslo, Norway, Sanity is used by thousands of companies including Unilever, Puma, National Geographic, and Condé Nast. Sanity is backed by ICONIQ Growth, Threshold Ventures, Lead Edge Capital, Heavybit, Alliance Venture, Monochrome Capital, and prominent angel investors like Twitter and Medium co-founder Ev Williams, Netlify co-founder Matthias Biilmann, ex-CEO of Heroku Adam Gross and Vercel founder Guillermo Rauch. Learn more at <a href="http://www.sanity.io">www.sanity.io</a>.

Sanity Raises $39 Million, Focuses Growth on Content as Data for Transformative Digital Experiences

Sanity logo with image of CEO Magnus Hillstead

Top JAMstack Static Site Generators for 2021

Explore a wide range of informative articles on JAMStack, insights, and industry updates. Stay informed and ahead of the curve with our diverse collection of news and posts covering the latest trends and developments in the industry