<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chaitanya Kulkarni on Medium]]></title>
        <description><![CDATA[Stories by Chaitanya Kulkarni on Medium]]></description>
        <link>https://medium.com/@chaitanya-kulkarni-17?source=rss-24917e6d0f85------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*sIxWrrg4ExLo5-Qo</url>
            <title>Stories by Chaitanya Kulkarni on Medium</title>
            <link>https://medium.com/@chaitanya-kulkarni-17?source=rss-24917e6d0f85------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:35:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chaitanya-kulkarni-17/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[NextJS — Catalyst in Drupal 10 Decoupled Architecture]]></title>
            <link>https://medium.com/globant/nextjs-catalyst-in-drupal-10-decoupled-architecture-b40f23ca89d9?source=rss-24917e6d0f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/b40f23ca89d9</guid>
            <category><![CDATA[decoupled-cms]]></category>
            <category><![CDATA[json-api]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[drupal-10]]></category>
            <dc:creator><![CDATA[Chaitanya Kulkarni]]></dc:creator>
            <pubDate>Wed, 12 Apr 2023 13:31:26 GMT</pubDate>
            <atom:updated>2023-04-12T13:31:26.621Z</atom:updated>
            <content:encoded><![CDATA[<h3>NextJS — Catalyst in Drupal 10 Decoupled Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cFwW9ksfh-hysK2M" /><figcaption>Photo by <a href="https://unsplash.com/@alvarordesign?utm_source=medium&amp;utm_medium=referral">Alvaro Reyes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This article targets Drupal developers, demonstrating a decoupled architecture where <a href="https://www.drupal.org/developers">Drupal CMS</a> is used as a back-end content management system. <a href="https://next-drupal.org/">Next.js</a> can serve the front end.</p><p><a href="https://nextjs.org/">Next.js</a> is a flexible <strong>React framework</strong> that gives you building blocks to create fast <strong>web applications</strong>. A headless, or decoupled CMS is an architecture for web development that separates the front end from the back end. Drupal is one of the greatest content platforms and also presents decoupling options with its hub-and-spoke model.</p><h4><strong>High-Level Rendering Mechanism</strong></h4><p>In below image web page consist of two aspects:</p><ul><li><strong>Client </strong>pages were developed using the Next JS component.</li><li><strong>Server</strong> API layer, where business logic is written and exposed using RESTful endpoints.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F9NyiqQh2bgT_g1d" /></figure><p>In this process, a web page creation has basic features that will have business logic developed at the Drupal content provider and rendered through RESTful or GraphQL APIs at the Next JS application. This technique uses</p><ol><li><strong>Routing</strong> <strong>schema</strong>: How to create a page and its access permissions</li><li><strong>Data Fetching: </strong>Integration with Data Providers (e.g., an access layer built on top of a database); Interaction with CMS using RESTful and GraphQL;</li><li><strong>Rendering: </strong>A<strong> </strong>strategy for rendering static or dynamic content</li></ol><p>The compilation of code needs to be transformed into a version that browsers can understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JjU5-QatkeQ3UH7HaN-EEA.png" /></figure><p>For setting up a Drupal instance for developing backend content that the Content Editor manages, we can start with the <a href="https://www.drupal.org/docs/develop/using-composer/manage-dependencies">installation</a> process using the Lando Docker container.</p><pre>lando composer create-project drupal/recommended-project drupal-decoupled</pre><p>To start with a decoupled environment, log in to the Drupal administration panel. Under the <strong>Extend</strong> menu section, you will see the modules shown in the screenshot. We need to enable Drupal-contributed modules, which are new features in the Drupal 10 version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cqi5YGZgbQXV1OctVfLqUA.png" /></figure><h4><strong>DrupalClient — A powerful JSON: API client for Drupal</strong></h4><p>The DrupalClient is a powerful JSON: API client that ships with helpers for working with Drupal data. We can use DrupalClient to fetch JSON API data from Drupal to build static pages. It also comes with full support for JSON: API write operations, which means you can create JSON: API resources from Next.js to Drupal. JSON: API provides methods <em>createResource</em>, <em>updateResource</em>, and <em>deleteResource</em> for performing required actions on nodes or content using the UUID as a unique identifier. <a href="https://next-drupal.org/guides/umami-demo">Guidelines for Next JS with Umami </a>Distribution.</p><pre>// Get content of specific Article using UUID<br>const article = await drupal.getResource(<br>  &quot;node--article&quot;,<br>  &quot;dad82fe9-f2b7-463e-8c5f-02f73018d6cb&quot;<br>)<br><br><br>// Similarly, to create new Arctile <br>const article = await drupal.createResource(&quot;node--article&quot;, {<br>  data: {<br>    attributes: {<br>      title: &quot;Title of Article&quot;,<br>      body: {<br>        value: &quot;&lt;p&gt;Content of body field&lt;/p&gt;&quot;,<br>        format: &quot;full_html&quot;,<br>      },<br>    },<br>  },<br>})<br><br><br>// Updating specific Article we need to pass additional UUID <br>// as unique Identifier<br>const article = await drupal.updateResource(<br>  &quot;node--article&quot;,<br>  &quot;a937dd34-5407-4fff-8594-fccaaa5bb72a&quot;, // &lt;-- Article ID<br>  {<br>    data: {<br>      attributes: {<br>        title: &quot;Title of Article&quot;,<br>      },<br>    },<br>  }<br>)<br><br>// Delete Article using UUID<br>const deleted = await drupal.deleteResource(<br>  &quot;node--article&quot;,<br>  &quot;a937dd34-5407-4fff-8594-fccaaa5bb72a&quot; // &lt;-- Article ID<br>)</pre><h4>Authentication Layer for securing APIs exposed from Drupal to NextJS</h4><p>The Drupal REST &amp; JSON: API Authentication module restricts and secures unauthorized access to your Drupal site APIs using different authentication methods, including bearer tokens,<strong> </strong>basic authentication, external/third-party provider authentication, etc.</p><ul><li><strong>Bearer Token</strong>: Bearer Authentication (also called token authentication) is an HTTP authentication scheme created as part of OAuth 2.0 but now used on its own. DrupalClient manages the expiration of Barear tokens and renews them on expiration.</li></ul><pre>// Bearer Token Method<br>const article = drupal.getResource(<br>  &quot;node--article&quot;,<br>  &quot;293202c9-f603-444e-a426-a5637e2ade2e&quot;,<br>  {<br>    withAuth: {<br>      clientId: process.env.DRUPAL_CLIENT_ID,<br>      clientSecret: process.env.DRUPAL_CLIENT_SECRET,<br>    },<br>  }<br>)</pre><ul><li><strong>Basic Authentication</strong>: Basic Authentication is a method for an HTTP user agent (e.g., a web browser) to provide a username and password when making a request.</li></ul><pre>// DrupalClient for authenticating API.<br>export const drupal = new DrupalClient(<br>  process.env.NEXT_PUBLIC_DRUPAL_BASE_URL,<br>  {<br>    auth: {<br>      username: process.env.DRUPAL_USERNAME,<br>      password: process.env.DRUPAL_PASSWORD,<br>    },<br>  }<br>)<br><br>// Considering example for accessing Articles with authentication<br>const articles = await drupal.getResourceCollection(&quot;node--article&quot;, {<br>  withAuth: {<br>    username: process.env.DRUPAL_USERNAME,<br>    password: process.env.DRUPAL_PASSWORD,<br>  },<br>})</pre><h3>Key Takeaways</h3><p>We have learned how to develop a decoupled architecture using a JSON:API where content is delivered from Drupal 10 CMS and rendered in the NextJS application using a RESTful endpoint. We have also seen how to implement user authentication methods for accessing web services. I have conducted a Drupal tech talk covering a live demo of a decoupled environment. You can go through it in detail <a href="https://www.linkedin.com/events/nextjs-acatalystindrupaldecoupl7039219477632200704">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b40f23ca89d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globant/nextjs-catalyst-in-drupal-10-decoupled-architecture-b40f23ca89d9">NextJS — Catalyst in Drupal 10 Decoupled Architecture</a> was originally published in <a href="https://medium.com/globant">Globant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architecture Skills Framework]]></title>
            <link>https://medium.com/globant/architecture-skills-framework-5ee667482c20?source=rss-24917e6d0f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ee667482c20</guid>
            <dc:creator><![CDATA[Chaitanya Kulkarni]]></dc:creator>
            <pubDate>Tue, 23 Aug 2022 09:47:54 GMT</pubDate>
            <atom:updated>2022-08-23T15:00:30.077Z</atom:updated>
            <content:encoded><![CDATA[<p>Skills frameworks provide a view of the competency levels required for specific roles. They define:<br>■ The roles within a work area<br>■ The skills required by each role<br>■ The depth of knowledge required to fulfill the role successfully</p><p>They are relatively common for defining the skills required for a consultancy and/or project management assignment, to deliver a specific project or work package.</p><p><strong>Need for an Enterprise Architecture Skills Framework<br></strong>“Enterprise Architecture” and “Enterprise Architect” are widely used but poorly defined terms in the industry today. They are used to denote a variety of practices and skills applied in a wide variety of architecture domains. There is a need for better classification to enable a more implicit understanding of what type of architecture/architect is being described.</p><p>This lack of uniformity leads to difficulties for organizations seeking to recruit or assign/promote staff to fill positions in the architecture field. Because of the different usage of terms, there is often misunderstanding and miscommunication between those seeking to recruit, and those seeking to fill, the various roles of the architect.</p><p><strong>Benefits of the use of the TOGAF Architecture Skills Framework include:</strong></p><ul><li>Reduced time, cost, and risk in training hiring, and managing architecture professionals, both internal and external.</li><li>Reduced time and cost to set up an internal architecture practice.</li><li>Reduced time and cost to implement an architecture practice help reduce the time, cost, and risk of overall solution development.</li></ul><p><strong>Categories of Skills<br></strong>The skillset will need to include the following main categories of skills:</p><p>■ <strong>Generic Skills</strong>: — typically comprising leadership, teamworking, interpersonal skills, etc.<br>■ <strong>Business Skills &amp; Methods</strong>: — typically comprising business cases, business processes, strategic planning, etc.<br>■ <strong>Enterprise Architecture Skills</strong>: — typically comprising modeling, building block design, applications, and role design, systems integration, etc.<br>■ <strong>Program or Project Management Skills</strong>: — typically comprising managing business change, project management methods, tools, etc.<br>■ <strong>IT General Knowledge Skills</strong>: — typically comprising brokering applications, asset management, migration planning, SLAs, etc.<br>■ <strong>Technical IT Skills</strong>: — typically comprising software engineering, security, data interchange, data management, etc.<br>■ <strong>Legal Environment</strong>: — typically comprising data protection laws, contract law, procurement law, fraud, etc.</p><p><strong>Proficiency Levels</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*acROp-TtAQfpxnsRFcOliQ.png" /></figure><p><strong>Generic Skills</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b91UUzuosxeaPbaP-uzhyw.png" /></figure><p><strong>Legal Skills</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XaGsz_P5422-2CM3sODPuw.png" /></figure><p><strong>Technical Skills</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HHWl6Q7kgc0DNrg5cBWJgg.png" /></figure><p><strong>Project management skills</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwOIEXAoUXeq6K8QZVqTyA.png" /></figure><p>The role of the architect can be summarized as to:</p><p>■ <strong>Understand and interpret requirements</strong>: probe for information, listen to information, influence people, facilitate consensus building, synthesize and translate ideas into actionable requirements, articulate those ideas to others, and identify use or purpose, constraints, risks, etc.<br>The architect participates in the discovery and documentation of the customer’s business scenarios that are driving the solution. The architect is responsible for the requirements understanding and embodying those requirements understanding in the architecture specification.</p><p>■ <strong>Create a useful model</strong>: take the requirements and develop well-formulated models of the components of the solution, augment the models as necessary to fit all of the circumstances, and show multiple views through models to communicate the ideas effectively. The architect is responsible for the overall architectural integrity and maintaining the vision of the offering from an architectural perspective. The architect also ensures leverage opportunities are identified, using building blocks, and is a liaison between the functional groups (especially development and marketing) to ensure that the leverage opportunities are realized. The architect provides and maintains these models as a framework for understanding the domain(s) of development work, guiding what should be done within the organization, or outside the organization. The architect must represent the organization’s view of the architecture by understanding all the necessary business components.</p><p>■ <strong>Validate, refine, and expand the model</strong>: verify assumptions, bring in subject matter experts, etc. in order to improve the model and to further define it, adding as necessary new ideas to make the result more flexible and more tightly linked to current and expected requirements. <br>The architect additionally should assess the value of solution-enhancing developments emanating from fieldwork and incorporate these into the architecture models as appropriate.</p><p>■ <strong>Manage the architecture</strong>: continuously monitor the models and update them as necessary to show changes, additions, and alterations represent architecture and issues during the development and decision points of the program. The architect is an “agent of change”, representing the need for the implementation of the architecture. Through this development cycle, the architect continuously fosters the sharing of the customer, architecture, and technical information between organizations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ee667482c20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/globant/architecture-skills-framework-5ee667482c20">Architecture Skills Framework</a> was originally published in <a href="https://medium.com/globant">Globant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GraphQL with Drupal CMS]]></title>
            <link>https://chaitanya-kulkarni-17.medium.com/graphql-with-drupal-cms-de58d909ff93?source=rss-24917e6d0f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/de58d909ff93</guid>
            <category><![CDATA[drupal-8]]></category>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[decouple]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[cms-development]]></category>
            <dc:creator><![CDATA[Chaitanya Kulkarni]]></dc:creator>
            <pubDate>Fri, 12 Feb 2021 09:08:22 GMT</pubDate>
            <atom:updated>2021-02-12T09:08:22.421Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*072bSvMi7z6zDGbuSm2-CA.png" /></figure><p><strong>REST vs GraphQL</strong></p><p>The same route handler function is called in REST whereas in GraphQL query can be called to form a nested response with multiple resources. GraphQL execution library is used to construct response structures.</p><p><strong>PURPOSE</strong></p><ul><li>Decoupled Drupal applications with a javascript front-end (React, Angular, Ember, etc)</li><li>Providing more flexibility and efficiency as compared to REST endpoint by exposing API endpoints using GraphQL (Query language).</li></ul><p><strong>For Query Structure</strong></p><pre>type Car {<br><br>  id: ID<br><br>  name: String<br><br>  launched: Date<br><br>  price: String<br><br>  brand: Brand<br><br>}<br><br><br>type Brand {<br><br>  id: ID<br><br>  country: String<br><br>  cars: [car]<br><br>}</pre><p><strong>Base Format for GraphQL</strong></p><pre>type Query {<br><br> car(id: CID!): Car<br><br> brand(id: BID!): Brand<br><br>}<br><br>type Mutation {<br><br>  getTestDrive(input: AddRequestInput): TestDrive<br><br>}<br><br>type Car { ... }<br><br>type Brand { ... }<br><br>type TestDrive { ... }<br><br>input AddRequestInput { ... }</pre><p><strong>Request Format</strong></p><pre>GET /graphql?query={ car(id: &quot;1&quot;) { name, brand { country } } }</pre><p><strong>To Integrate GraphQL in Drupal 8</strong></p><ul><li><em>Module</em>: <a href="https://www.drupal.org/docs/8/modules/graphql">graphql</a></li><li><em>Library</em><a href="https://www.drupal.org/docs/8/modules/graphql"><em> </em></a><em>: </em><a href="https://github.com/webonyx/graphql-php">graphql-php</a></li></ul><p>Advantage of GraphQL</p><ul><li>Reduce the number of API calls to the server by the ability to created nested API calls.</li><li>It uses a strong type system to define the capabilities of an API. These types are written in the schema using GraphQL Schema definition (SDL) which is serves as a contract between the Client and Server.</li><li>Once the schema is defined front-end and back-end teams know the structure of the data and can, therefore, work independently.</li><li>No more Over- and Under fetching of attributes that may be one of the concerns in REST</li><li>GraphQL uses the concept of <em>resolver functions</em> to collect the data that’s requested by a client. With the help of resolvers, we can identify issues/errors in the schema definition</li><li>Changes in the Frontend design can be addressed without any extra work on the server. Since Client-side application (React, Angular, etc) can specify their exact data requirements, no backend engineer needs to make adjustments in API.</li></ul><p>Helpful Documentation</p><ul><li><a href="https://www.drupal.org/docs/8/modules/graphql">Drupal + GraphQL</a></li><li><a href="https://drupal-graphql.gitbook.io/graphql/">GraphQL API Documentation</a></li><li><a href="https://www.howtographql.com/basics/1-graphql-is-the-better-rest/">REST vs GraphQL</a></li><li><a href="https://github.com/drupal-graphql/drupal-decoupled-app">DEMO Application for GraphQL + React</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de58d909ff93" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>