<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Decoupled on Merkle Drupal &amp; Acquia Blog</title>
    <link>https://drupal.merkle.com/tags/decoupled/</link>
    <description>Recent content in Decoupled on Merkle Drupal &amp; Acquia Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>drupal@merkle.com (Merkle Drupal Team)</managingEditor>
    <webMaster>drupal@merkle.com (Merkle Drupal Team)</webMaster>
    <lastBuildDate>Fri, 23 Aug 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://drupal.merkle.com/tags/decoupled/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Decoupled Drupal and Next.js</title>
      <link>https://drupal.merkle.com/post/2024/08/decoupled-drupal-and-next-js/</link>
      <pubDate>Fri, 23 Aug 2024 00:00:00 +0000</pubDate><author>drupal@merkle.com (Merkle Drupal Team)</author>
      <guid>https://drupal.merkle.com/post/2024/08/decoupled-drupal-and-next-js/</guid>
      <description>Drupal &amp;amp; Next.js&#xA;In today’s digital world, choosing the right technologies is essential for success. This is specifically important for enterprise level applications, where wrong decisions can increase cost in further maintenance and decrease gains provided by the solution.&#xA;As user engagement is a key focus for web applications, we need to ensure that chosen technologies will be beneficial for providing best user experience.&#xA;By combining Drupal with Next.js, we are taking the next step, where we split business logic from presentation layer, ensuring flexibility, scalability, and performance.</description>
    </item>
  </channel>
</rss>
