When NOT to use Headless CMS

Introduction

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.

Here is the Youtube video for the same

Sitecore Comics

I've been working with Sitecore since 2012.

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.

Have fun!!!

Here is a Youtube video for the same!!!

Sitecore JSS : Convert YML to JSON

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 want to convert it to json file which can be easily accopalieshed by visiting https://onlineyamltools.com/convert-yaml-to-json as

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

Short tip but very useful!!!

The Sitecore Experience Edge Partner Collection

As you know that Sitecore introduce new product Sitecore Hub with Edge.

Sitecore also launched certification course "The Sitecore Experience Edge Partner Collection" on the same at their eLearning portal.

I registered and follow all the training topics and successfully completed my certification on the same.

Certificate : The Sitecore Experience Edge Partner Collection

 

Introduction to the Sitecore ASP.NET Core Rendering SDK

As you know that we can use ASP.NET CORE for developing headless application on Sitecore platform.

Sitecore launched certification course "Introduction to the Sitecore ASP.NET
Core Rendering SDK" on the same at their eLearning portal.

I registered and follow all the training topics and successfully completed my certification on the same.

 

Sitecore ASP.NET
Core Rendering SDK Certification

 

 

 

Boxever Advanced Certification

As you know that Sitecore acquired Boxever Ltd. which is a SaaS-based Customer Data Platform (CDP) providing decisioning and experimentation.

Sitecore also launched certification on "Boxever" as their eLearning site.

I registered and follow all the training topics and successfully completed my certification on the same.

Boxever Advanced Certification

 

 

Sitecore forgot password configuration with Sendgrid

Recently I worked on forgot password functionality from where user can get new password in his inbox through SendGrid in case if he forgot the Sitecore login password.

My Sitecore instance is on Azure. 

Open Kudu

I create a patch file at \site\wwwroot\App_Config\Include\zzz\MyPatchFile.config file and in <settings> section add below SMTP details lines.

<setting name="MailServer" value="smtp.sendgrid.net" />

<setting name="MailServerUserName" value="apikey" />

<setting name="MailServerPassword" value="4565655676hkjsd7868jkhkj" />

<setting name="MailServerPort" value="587" />

Save your changes.

If you are using SSL security, you must also add the following setting to the configuration file \site\wwwroot\Web.config:

  <system.net>

    <mailSettings>

      <smtp from="noreply@example.com">

        <network host="smtp.sendgrid.net" password="4565655676hkjsd7868jkhkj" userName="apikey" port="587" />

      </smtp>

    </mailSettings>

  </system.net>

</configuration>

 
Save your changes.

You need to change the sender of the Forgot your Password email to a valid email address. You can also edit the subject and content of the email. To do this, follow these steps:

• Log in to Sitecore as an administrator.
• In the Launchpad, open the Desktop, and select the Core database.
• In the Content Editor, navigate to /sitecore/system/Settings/Security/Password recovery/Password Recovery Email.
• Enter a valid email address in the Sender email address field, and change the other fields as you need.

Sitecore Forgot Password configuration

Now if any user forgot his password, 

• Visit to /sitecore/login page. 
• Click on "Forgot your password?"
• Enter Sitecore user name
• Click on Send button
  

You should receive a email with username with newly generated password.