Powershell script can be used in a data source to solve complex problems in Sitecore.
· For this you can create script which is used to provide a list of child items of a parent item within a data source. For example, the script returns all the child items of the event folder that were created from the event detail template.
· The script tag and full path of the script must be specified in the data source.
· The script can be used in a template data source, a data source location, or a rendering data source.
· The script must return either one item or a list of items for Sitecore to display to the end user.
Here is my YouTube video for the same
Stay tuned for more such articles, tips and tricks.
Today, we are going to discuss how to embed a Sitecore 10.3 form on an external website. Sitecore 10.3 is available in the market and offers many new features, including headless SXA and web hooks. The new Sitecore forms use an Embeddable Form Framework, which means that you can create the forms within Sitecore and use them on any type of website, regardless of the technology used.
The benefit of this is that you can collect data from non-Sitecore-based websites and import it into the Sitecore website. This feature is similar to the old FXM feature.
Here are the steps to implement it
· Install Sitecore 10.3
· Rebuild the master and web index
· Install Sitecore Headless Service 21.0.0
· Create and publish an API key
· Create and publish a new form in Sitecore
· Download the Sitecore Embeddable Forms
· Copy the CSS folder and Javascript file to your website's root folder
· Specify the form ID in your HTML or PHP website
· Include the script in your HTML or PHP page
· Pass the API key to the script
· Specify any necessary CSS elements on your HTML or PHP page
Here is my Youtube video for the same
Stay tuned for more such articles, tips and tricks.
Sitecore is a complex platform with many products, features and functionalities, and it can be challenging to keep track of all the details.
A mind map can serve as a single source for quick and easy access to information about a Sitecore products and its different features. It can also be used as a reference guide to quickly find specific information or to communicate the products to the clients, team members and stakeholders.
So I created Sitecore mindmap for reference
I am open to any suggestions or feedback on what else could be included in this mind map that may have been missed!!!!
Here is my YouTube video for the same
Stay tuned for more such articles, tips and tricks.
Today we are going to see new features of Sitecore called Web Hooks. Before understanding web hooks, let's try to understand the concept of hooks in general life. Just like we have hooks in our home to hang clothes or fishing hooks, these hooks can hold two different things and join them. Similarly, in programming, web hooks can allow interaction between different applications.
When two different web applications are present, they can be interacted through a callback function. One application can receive real-time notifications through an event. For instance, if something is happening in application one, it will trigger a notification for the other application, which will receive it in code terms. Web hooks can be used in two places: events and workflows. Whenever an item is created, deleted, copied, published or a workflow is submitted, these actions are considered events.
Web hooks can be used to track these events. Sitecore will send information about the event in terms of a JSON request payload to the other application. The Sitecore HTTP post request will be sent to the other application with the payload in JSON or XML format. The other application will receive the request and further process it. There are three types of web hooks that can be created: web hook event handler, workflow, and validation actions.
Here are the steps to implement
· In Sitecore, web hooks can be created through the System section and Web Hooks option.
· To create a web event handler, select a specific event (item added, copied, deleted, etc.).
· Specify the URL for the other application and enable the event.
· A demo was shown with a method created in the Target application to receive input from Sitecore and save it to a file.
· When an item was added in Sitecore, the event was triggered and a file was created on the local machine with the input received from Sitecore.
Here is my YouTube video for the same
Stay tuned for more such articles, tips and tricks.
Today, we're going to explore another hidden feature of the Sitecore.
By default, all items created within the Sitecore are sorted alphabetically. However, if the position of the items has been changed by the content author, the list may not be sorted. In this case, sorting the items manually by clicking on the "up" or "down" option for each item would take a lot of time, especially if there are hundreds of items under a single parent item.
To solve this problem, the easiest way is to select the folder and click on the " sorting" option. This will open a "sort order" window where you can sort the items by different options such as "created date" or "reverse". To reset the order, simply click on "reset", and the items will be sorted accordingly.
This feature is hidden and simple to use, so I hope you will take advantage of it in your project.
Here is my YouTube video for the same
Stay tuned for more such articles, tips and tricks.
Today, we are going to take a look at something really cool - Chat GPT. In recent weeks, this technology has been a hot topic of discussion. Chat GPT is a dialog-based artificial intelligence chatbot that can answer your questions in a conversational manner. It's developed by OpenAI, a well-known research lab. The best thing about Chat GPT is that it is stateful, meaning it can remember previous questions and respond accordingly within the same context. You can find more information about Chat GPT on the OpenAI website.
As a developer, one use case for Chat GPT is to migrate CSV or Excel data to Sitecore. For example, if a client asks for assistance in migrating data, a developer can use Chat GPT to determine the best approach for accomplishing this task. The first step is to find out the different ways to migrate data and choose the best option. Once the data is migrated, the developer can assign icons, create packages in Sitecore, and publish the items.
The Chat GPT home page provides lots of information about the technology and can be used to help with a developer task such as migrating Excel file data to Sitecore. By asking Chat GPT for help, the chatbot can provide information on different methods, such as using a custom script or a C# code. Chat GPT can even provide the necessary code to complete the task, such as a C# script or a PowerShell script. The developer can then copy and paste the code into their application and test it.
Here is my YouTube video for the same
Stay tuned for more such articles, tips and tricks.
On May 20, 2023, I presented webinar on "15 Ways of Content Migration to Sitecore", offering valuable insights and practical strategies for successfully transitioning content to the Sitecore platform.
Understanding the Complexity of Content Migration:
Content migration is a critical phase in any Sitecore implementation project, requiring meticulous planning, strategic decision-making, and a thorough understanding of both the source and target systems. The webinar emphasized the importance of recognizing the complexity involved in content migration and provided attendees with a different way to achieve it.
The core focus of the webinar was to equip participants with a diverse set of strategies and techniques to tackle content migration effectively. I navigated through 15 different approaches, each tailored to address specific scenarios and requirements. From manual content transfer to automated migration tools, attendees gained insights into a wide range of methodologies to streamline the migration process.
Empowering Sitecore Professionals:
The "15 Ways of Content Migration to Sitecore" webinar left attendees feeling empowered and equipped with a wealth of knowledge to tackle content migration projects with confidence.
Sitecore is a leading digital experience platform that empowers organizations to deliver personalized and engaging digital experiences to their customers. As with any technology, there are constantly new tools and trends emerging in the Sitecore ecosystem that can impact an organization's digital strategy. A Sitecore technology radar can help organizations stay informed about these changes and make informed decisions about which technologies to adopt, trial, assess, or hold.
Sitecore technology radar typically consists of four rings, each representing a different level of adoption and maturity for a particular technology: Adopt, Trial, Assess, and Hold. Let's explore each of these rings in more detail.
Adopt
In the Adopt ring, technologies are widely adopted and proven to be effective in the Sitecore ecosystem. These technologies are generally stable and reliable, and organizations can confidently use them to support their business needs. Some examples of technologies in the Adopt ring for Sitecore include:
Sitecore Experience Platform (XP)
Content Hub DAM
Sitecore JSS (JavaScript Services)
Trial
In the Trial ring, technologies are emerging and have shown potential, but are not yet widely adopted. Organizations may experiment with these technologies to gain experience and assess their potential value. Some examples of technologies in the Trial ring for Sitecore include:
Sitecore XM Cloud
Sitecore SXA (Sitecore Experience Accelerator)
Sitecore CDP
Assess
In the Assess ring, technologies are on the horizon and are being evaluated for their potential value. These technologies are not yet fully understood, and organizations need to carefully evaluate their potential benefits and risks before making any decisions. Some examples of technologies in the Assess ring for Sitecore include:
OrderCloud
Sitecore Search
Hold
In the Hold ring, technologies are no longer recommended for use. These are technologies that have become outdated, are no longer supported, or have been replaced by newer technologies. Some examples of technologies in the Hold ring for Sitecore include:
Sitecore Commerce
Web Forms for Marketers (WFFM)
Sitecore Experience Database (xDB)
By regularly reviewing and updating their Sitecore technology radar, organizations can stay ahead of emerging trends and make informed decisions about which technologies to adopt, trial, assess, or hold. This can help organizations to optimize their Sitecore digital experience and stay competitive in the rapidly evolving digital landscape.
As businesses continue to evolve and innovate, their digital strategies and web development needs must also adapt. In recent years, we have seen a shift towards using cloud-based platforms for web development and deployment, and the adoption of JavaScript-based frameworks for front-end development. Sitecore, a leading digital experience platform, has embraced this trend with the introduction of Sitecore XM Cloud and Next.js.
If you currently have a Sitecore XP MVC-based website, you may be wondering why you should consider moving to Sitecore XM Cloud and Next.js. Today, we will explore some of the key benefits of making the move, and why it could be the right choice for your business.
Here are some of the key reasons why businesses may want to consider moving from Sitecore XP to Sitecore XM Cloud:
.NET Framework
Scalability
Improved Performance
Reduced Costs
Flexibility
Security
Faster time to market
Global reach
Ease of use
Improved collaboration
Continuous innovation
Better customer experiences
Reduced complexity
Lower total cost of ownership
.NET Framework
Since the .NET framework is on its way out, it would be wise to steer clear of it and redirect attention towards Javascript frameworks. As cloud is the future, it's a favorable time to start investing and focusing on cloud-based technologies.
Scalability
One of the main benefits of Sitecore XM Cloud is its scalability. Sitecore XM Cloud is a cloud-based platform that is designed to handle large amounts of traffic and data, making it ideal for businesses that need to scale quickly to meet demand. With Sitecore XM Cloud, businesses can easily scale up or down as needed, without having to worry about infrastructure management or capacity planning.
Improved Performance
Sitecore XM Cloud also offers improved performance compared to Sitecore XP. Sitecore XM Cloud is designed for high availability and reliability, ensuring that your website or application is always up and running. Additionally, Sitecore XM Cloud includes a range of performance optimization tools, such as Content Delivery Networks (CDNs) and caching, which can improve page load times and reduce server response times.
Reduced Costs
Another benefit of Sitecore XM Cloud is that it can help businesses reduce costs. Sitecore XM Cloud is a fully managed service, which means that businesses don't need to worry about infrastructure management or maintenance. This can significantly reduce the costs associated with managing and maintaining an on-premises infrastructure.
Flexibility
Sitecore XM Cloud also offers greater flexibility than Sitecore XP. Sitecore XM Cloud is a headless platform, which means that it can be integrated with a wide range of front-end frameworks, allowing developers to use the tools and frameworks that they are most comfortable with. This can help businesses build highly customized, tailored solutions for their clients.
Security
Sitecore XM Cloud provides enhanced security features, such as automatic updates and patches, proactive monitoring, and 24/7 security operations support. This can help businesses ensure that their websites and applications are protected against cyber threats.
Faster time to market
Sitecore XM Cloud includes a range of pre-built templates and components, which can help businesses get their websites and applications up and running quickly. This can significantly reduce the time to market for new digital experiences.
Global reach
Sitecore XM Cloud is designed to support businesses with a global presence. It includes a range of features, such as geo-targeting, multi-language support, and local hosting options, which can help businesses deliver personalized, localized experiences to users around the world.
Ease of use
Sitecore XM Cloud includes a user-friendly interface that makes it easy for businesses to manage their digital experiences. It also includes a range of tools for content management, analytics, and personalization, which can help businesses improve the efficiency and effectiveness of their digital operations.
Improved collaboration
Sitecore XM Cloud includes collaboration tools that can help teams work together more effectively.
Continuous innovation
Sitecore XM Cloud is a cloud-based platform that is continually updated with new features and capabilities. This means that businesses can benefit from the latest innovations and best practices without having to worry about upgrading their infrastructure or software.
Better customer experiences
Sitecore XM Cloud is designed to help businesses deliver exceptional customer experiences across all channels and touchpoints. By leveraging the power of Sitecore XM Cloud, businesses can create personalized, targeted experiences that engage and delight their users, driving loyalty and advocacy.
Reduced complexity
Sitecore XM Cloud is designed to simplify the digital experience management process, making it easier for businesses to manage and optimize their websites and applications. By reducing complexity, businesses can free up resources to focus on other areas of their business, such as innovation, product development, and customer engagement.
Lower total cost of ownership
Sitecore XM Cloud can help businesses reduce their total cost of ownership by eliminating the need for on-premises infrastructure and reducing maintenance and management costs. Additionally, Sitecore XM Cloud includes flexible pricing options, which can help businesses tailor their costs to their specific needs and usage patterns.
Conclusion
There are many reasons why businesses may want to consider moving from Sitecore XP to Sitecore XM Cloud. By leveraging the scalability, performance, security, flexibility, collaboration, insights, innovation, customer experience, and simplicity of Sitecore XM Cloud, businesses can achieve their digital transformation goals and drive growth and success in the digital age.
The utilization of the find and replace technique is immensely valuable for both editors and developers who seek to modify individual or multiple pieces of content within a Sitecore instance.
To facilitate this process, here is my recorded Youtube video that shows 8 potential approaches to conducting find and replace operations in Sitecore.
If you're a C# developer, you'll want to check out this exciting new tool: C# REPL! This cross-platform command line tool is designed for rapid experimentation and exploration of C# code. With C# REPL, you can easily test out snippets of code, try out different syntaxes, and even experiment with new packages.
One of the great things about C# REPL is that it supports intellisense, making it easy to quickly find the methods and properties you need. You can also install NuGet packages directly from the command line, so you can easily add new functionality to your code without having to switch to a different tool.
C# REPL is a .NET 7 global tool, which means it can be easily installed on any machine running Windows 10, Mac OS, or Linux. And because it's a command line tool, it's lightweight and easy to use - perfect for developers who want to streamline their workflow and focus on writing great code.
With its support for referencing local .NET projects and assemblies, C# REPL can be a valuable tool for exploring and experimenting with Sitecore-specific code and functionality.
Here I am showing a demo on how you can use it Sitecore libraries to test it.
Check out this video for the same
Whether you're a seasoned C# developer or just starting out, C# REPL is a must-have tool for your toolkit. Give it a try today and see how it can help you work more efficiently and experiment more quickly!
Albert Einstein once said that "If you can't explain it simply, you don't understand it well enough.". And I believe that Comics are simple and a great way of communicating ideas and emotions that can't be conveyed through words alone.
Sitecore has come a long way since its inception in 2001, evolving from a simple content management system (CMS) to a comprehensive digital experience platform (DXP). Over the past 20 years, Sitecore has released a number of versions, each with its own set of features and enhancements. Here's a poster of all the major versions launched by Sitecore over the last two decades.
So I designed this jumbo poster for showing the 20 years of Sitecore journey.
This poster reflects that Sitecore's evolution over the past 20 years has been marked by a commitment to innovation and a relentless focus on customer needs. With each new version, Sitecore has introduced new features and enhancements that have helped businesses deliver more engaging and personalized digital experiences to their customers.
We're excited to announce that our TDS team took part in the Sitecore Hackathon 2023 on March 4th.
We kicked off the day at 6 AM and wrapped up at around 10:30 PM. Among the three categories available, we chose "Best enhancement to SXA Headless" as our problem statement.
Our team successfully created a "Sitecore SXA module - SmartFill" for the Sitecore Content and Experience Editor, which functions seamlessly.
A content management system (CMS) is a critical component of any website, allowing businesses to manage their online presence with ease. However, there are times when a primary CMS may not be the best fit for an organization. In these cases, a secondary CMS can provide a more tailored solution. In this article, we'll discuss when to consider using a secondary CMS.
Topics for discussion
· Introduction to Secondary CMS
· Scenarios where a Secondary CMS may be a good fit
· Benefits of using a Secondary CMS
· How to choose the right Secondary CMS
· Implementation of a Secondary CMS and best practices.
Introduction to Secondary CMS
Before we dive into the reasons to consider a secondary CMS, it's important to understand what a secondary CMS is.
Essentially, a secondary CMS is an additional system that works in conjunction with your existing primary CMS to help manage specific areas of your website. This can be a useful solution in situations where your primary CMS is unable to handle certain tasks.
Scenarios where a Secondary CMS may be a good fit
There are several scenarios where using a secondary CMS may be a good fit for your organization. These include:
Managing localized content: If your business has a global presence and needs to create content for different regions, a secondary CMS can help manage localized content. This can include different languages, cultural nuances, and other region-specific content.
Digital asset management: If your business has a lot of digital assets that need to be managed, a secondary CMS can help keep them organized and easy to access.
Marketing automation: If you need to manage and distribute marketing campaigns across multiple channels, a secondary CMS can provide additional functionality that your primary CMS may not offer.
Mobile application content management: If you have a mobile app, a secondary CMS can be used to manage the content that appears within the app.
eCommerce management: If your business operates an eCommerce store, a secondary CMS can provide additional functionality to manage your products, orders, and customer data.
Benefits of using a Secondary CMS
The benefits of using a secondary CMS include:
More tailored solutions for specific needs: A secondary CMS can provide a more tailored solution for specific tasks that your primary CMS may not be able to handle.
Improved efficiency: By using a secondary CMS, you can increase your efficiency and save time by automating certain tasks.
Improved user experience: A secondary CMS can improve the user experience of your website by making it easier to manage specific content.
How to choose the right Secondary CMS
When choosing a secondary CMS, it's important to consider the following:
Compatibility with your primary CMS: Make sure the secondary CMS is compatible with your primary CMS.
Functionality: Consider the features and functionality of the secondary CMS to make sure it meets your needs.
Ease of use: Choose a secondary CMS that is user-friendly and easy to use.
Integration: Consider how the secondary CMS will integrate with your existing technology stack.
Implementation of a Secondary CMS and best practices
When implementing a secondary CMS, it's important to follow best practices, including:
Proper training: Ensure that your team is properly trained to use the secondary CMS.
Data migration: Make sure to migrate all relevant data to the secondary CMS.
Ongoing maintenance: Maintain the secondary CMS and keep it up-to-date with the latest updates and security patches.
In conclusion, a secondary CMS can provide a tailored solution for specific needs that your primary CMS may not be able to handle. By carefully choosing the right secondary CMS, you can improve your efficiency and provide a better user experience for your website visitors.
Sitecore offers SaaS based CMS Content Hub One which is a good fit for secondary CMS.
For example, your client uses Sitecore as their primary CMS with extensive integration and customization, and may even run it as an on-premises solution. Now, they are interested in using a lightweight, SaaS-based CMS for mobile apps and marketing activities, instead of going through the time-consuming, resource-intensive, and costly process of upgrading Sitecore, it would be wise to consider secondary CMS options such as Content Hub One. Generally try to choose a single-family product CMS for your technology stack, as this usually results in better compatibility and ease of use.
Today, we will be discussing a hidden feature of the Sitecore that some of you may already know about but never use. We are all familiar with the "Publish" option in site work, which is used to make changes to the content live on a particular environment.
There are three types of publishing you can do - Incremental, SMART, and Republish.
Let's consider a scenario where you are working on a global website with content authors from all around the world. If one content author starts a publish in one country and another author submits a publish request from another country, the requests will be added to a queue. The second author's changes will only be published once the first author's changes have been completed.
However, if your client asks you to publish a specific item right away, it can become a tricky situation because the item will be added to the queue. In such a scenario, you can use the hidden feature of the Sitecore called "Transfer".
To demonstrate this feature, we will publish an entire website, open it in another window, and publish it again. The request will be added to the queue. In a third window, we will make changes to a item, say "Thank You".
To use the transfer feature, we will go to the "Publish" site and select "Republish". In the next step, we will make changes to the "Thank You" item and save it. Normally, when we publish the changes, they would be added to the queue. But with the transfer feature, we can copy the "Thank You" item and select "Transfer".
We will then move the item to the "Article” Folder, and the changes will be updated on the web database without going into the queue. The full publishing that we did earlier will still be in process, but our changes are already visible on the website.
This is a useful trick to know, although it's rarely used.
Here is my YouTube video for the same
Stay tuned for more such articles, tips and tricks.
Today, we will be exploring one of the coolest features on the Sitecore: OData Services.
This feature allows you to expose your item data in JSON format in read-only mode. It is incredibly easy to use and configure. To do so, you need to create an OData item API at the settings, services API key section. After you have created it, you can specify its fields, for example, core, allowed control. You can also specify the database to which you want to get the item details. In a production environment, it is mostly on the web.
Once you have configured it, you can access your items by using the Sitecore domain name followed by the OData services API and the item ID or item path. You also need to pass the OData services API key. For example, if you want to access the details of a home item with ID and three fields (title, text, and address), you can use this URL and pass the API key. You will get the item properties such as the item name, path, language, template, creation date, and ID.
Headless CMS is a popular technology that is used to manage and publish content across multiple platforms. However, it's not always the best choice for every website or application. In this blog post, I will explain when not to use a headless CMS and why.
Simple Websites with Minimal Content: If your website is small and doesn't require dynamic content, a headless CMS may be unnecessary. For instance, if your website has only a few pages, it's better to use a traditional CMS or a static site generator. You don't need the added complexity of a headless CMS for a simple website.
Small Development Teams with Limited Resources: While headless CMS platforms can offer many benefits, they can also be more complex to set up and maintain than traditional CMS. If your development team is small or lacks experience with headless CMS, it may be better to stick with a more familiar technology. Using a headless CMS can add unnecessary complexity to the development process.
Content-Heavy Websites with Complex Data Structures: Headless CMS platforms are designed to handle complex content models and data structures. However, if your website has relatively simple content needs, you may not need the added complexity of a headless CMS. In this case, a traditional CMS may be a better option. If your website doesn't require a complex content structure, there's no need to use a headless CMS.
Websites with Tight Deadlines: If you're working on a tight deadline, you may not have the time to learn and implement a headless CMS. Traditional CMS platforms are generally quicker to set up and easier to use, making them a better choice for fast turnarounds. If you're under time pressure, it's better to use a traditional CMS platform.
Websites with Tight Budgets: While headless CMS platforms can be a great choice for larger websites and enterprise-level applications, they can be more expensive to implement than traditional CMS. If you're working with a tight budget, it may be more cost-effective to stick with a more traditional approach. Using a traditional CMS can help you save money and still achieve your website goals.
Multiple Integrations: Traditional CMS may be a better choice if you need to perform multiple integrations in your CMS.
Customization: If you anticipate the need for extensive customization of the CMS for administrators or content authors, a traditional CMS might be more suitable than a headless one.
Conclusion: Headless CMS platforms are powerful tools that can help you manage and publish content across multiple platforms. However, they're not always the best choice for every website or application. By understanding when not to use a headless CMS, you can make a more informed decision and choose the technology that's right for your project.
Recently, I had a funny incident where someone asked me to explain what a content management system is. Even though I've been working with Sitecore for a decade, I struggled to explain the question because it was asked by a school boy. I asked the kid what he liked, and he said comics, so I decided to explain it in a way that would be fun for them.
That's how I came up with the Sitecore comics, which explain Content management systems to kids in an engaging and entertaining way.
Till yesterday, I knew that to provide content in Sitecore JSS I need to create YML file.
But today I learn that one can also create JSON file as well
Lets suppose we have following Graphql en.yml file
fields:
pageTitle: GraphQL | Sitecore JSS
placeholders:
jss-main:
- componentName: ContentBlock
fields:
heading: Using GraphQL with JSS
content: |
<p>This is a live example of using Integrated GraphQL and Connected GraphQL with a JSS app.
For more information on GraphQL use in JSS, please see <a href="https://jss.sitecore.com" target="_blank" rel="noopener noreferrer">the documentation</a>.</p>
- componentName: GraphQL-Layout
placeholders:
jss-graphql-layout:
- componentName: GraphQL-IntegratedDemo
fields:
sample1: Hello integrated GraphQL world!
sample2:
href: https://www.sitecore.com
target: _blank
text: GraphQL lets you get structured field data too
- componentName: GraphQL-ConnectedDemo
fields:
sample1: Hello connected GraphQL world!
sample2:
href: https://www.sitecore.com
target: _blank
text: GraphQL lets you get structured field data too
I kept this json data in “testymltojson.json” file as
He is the complete code
{
"fields": {
"pageTitle": "GraphQL | Sitecore JSS - YML To JSON"
},
"placeholders": {
"jss-main": [
{
"componentName": "ContentBlock",
"fields": {
"heading": "Using GraphQL with JSS - YML To JSON",
"content": "<p>This is a live example of using Integrated GraphQL and Connected GraphQL with a JSS app.\nFor more information on GraphQL use in JSS, please see <a href=\"https://jss.sitecore.com\" target=\"_blank\" rel=\"noopener noreferrer\">the documentation</a>.</p>\n"
}
},
{
"componentName": "GraphQL-Layout",
"placeholders": {
"jss-graphql-layout": [
{
"componentName": "GraphQL-IntegratedDemo",
"fields": {
"sample1": "Hello integrated GraphQL world!",
"sample2": {
"href": "https://www.sitecore.com",
"target": "_blank",
"text": "GraphQL lets you get structured field data too"
}
}
},
{
"componentName": "GraphQL-ConnectedDemo",
"fields": {
"sample1": "Hello connected GraphQL world!",
"sample2": {
"href": "https://www.sitecore.com",
"target": "_blank",
"text": "GraphQL lets you get structured field data too"
}
}
}
]
}
}
]
}
}
So if you deployed it to Sitecore, this json file will create its item as
