วีดีโอ

If you are making a decision as per the job market then it is headless but that will be the wrong thing to do. Your Sitecore concept will become weak. I think that the best path is Sitecore MVC, SXA, Headless and XM cloud. Thank you

It would be difficult to verify this over a comment. Could you please send a screenshot of the error in the console, log files, and the corresponding Sitecore item via email? Also, please check if you are using the correct placeholder. Thank you

Thank you. Honestly, you hit the nail on the head. I hope Sitecore addresses this soon. At this point, it is very difficult to get a playground for XM Cloud. The only way to access it is if your organization has a license and provides you with access. Currently, gaining hands-on experience with XM Cloud is challenging without your organization's support.

Thanks for responding sir.

There is no need to write a custom submit action for file uploads. Sitecore Forms provides an out-of-the-box file upload control, which automatically saves the uploaded files in the form database.

Yes. There is a Git link i have shared wherever code is used

This video is for pipelines and processor th-cam.com/video/0MVy3KlKdvQ/w-d-xo.html

Sitecore does not have a page life cycle. It works on the concept of pipeline and processor. It resolves page depending on the pipeline. Please check below video for component based development and how page request resolves th-cam.com/video/ElLX6GJXByU/w-d-xo.html

Sitecore requires renderings to display content, whether static or dynamic. You can create custom renderings or use static bindings for specific components, including forms. However, if forms are statically bound, they lose flexibility, as a marketer would not be able to add, remove, or modify forms dynamically without developer intervention. To enable marketer-driven changes, dynamic renderings (like placeholders or data-driven renderings) are necessary.

Thank you so much. There is already an video th-cam.com/video/0MVy3KlKdvQ/w-d-xo.html I know that i have not done a walkthrough. I will add it to my todo list. My pipeline has many other priority topics in queue 🙂 so it may take time. Thank you once again🙏

Traditionally, Sitecore MVC websites are relatively slow (though many may disagree, this is often the case in practice). One of the key reasons to transition to Sitecore's headless architecture is the ability to leverage features that can improve website speed, such as using Experience Edge as a CDN. There is no one-size-fits-all cache setting; it must be tailored to your specific architecture and infrastructure. This will always be an ongoing process. Thank you

Traditionally, Sitecore MVC websites are relatively slow (though many may disagree, this is often the case in practice). One of the key reasons to transition to Sitecore's headless architecture is the ability to leverage features that can improve website speed, such as using Experience Edge as a CDN. There is no one-size-fits-all cache setting; it must be tailored to your specific architecture and infrastructure. This will always be an ongoing process. Thank you

Thank you

Thank you. I will try as much as possible to cover topics related to forms in upcoming videos🙏

@@MySitecoreDiaries Thanks! You are an awesome teacher.

and Thanks To you mister

and keep going

That is in the pipeline. It may take time after we complete our react series

@@MySitecoreDiaries thank you mister very much

Converting a traditional MVC website to a headless architecture is definitely possible, though it may take some time. In older versions, the Item API was commonly used to fetch data. To the best of my knowledge, it has not been deprecated, so you could consider leveraging it. Alternatively, you could develop a straightforward API layer as another option.

Thank you for providing a different topic. I will definitely consider this.

Layout service is out of box in Sitecore. Nothing you have to do to generate it.

Sure. Added in my to do list

@@MySitecoreDiaries where it is ?

What I mean is I will do that in future videos of Sitecore Interview questions video series. Few questions are already there and slowly I will add few more. Check below playlist th-cam.com/play/PLt519PJr4jF9dUAgkMKtt1y5IP9t6C5bK.html

Sure. Will add it in my to-do list 👌

@@MySitecoreDiaries Thank you sir.

Sorry but i did not get your question. While creating a partial design we need to add renderings in presentation details or in experience editor. It is exactly same how we design any page in Sitecore

Yes.. In simple words you can say that but generally in layout you would have components like design elements example columns, rows section etc. But partial design can have components like header, footer, menu etc. In next month i will create a short video related to this.

Sitecore installation is the traditional way however there are some additional packages that are needed like headless service and SXA. As you will move ahead with this series it is covered however if you want to jump in directly You can follow the playlist in which we are creating headless pages from scratch Set Up Headless Website in Sitecore JSS | Sitecore JSS Headless Tutorial for beginners: th-cam.com/play/PLt519PJr4jF95vq5CvsZ82CxlRSce-xSm.html

@ thanks 😊

You need to write custom code to consume third party services and get content from it and then you can create sitecore items and content using sitecore APIs. For this you can use dotnet code or powershell script. This is a rare case where you will use Sitecore or in that case any CMS. CMS is used to manage the content but that content itself is managed by a third party then it may not make sense to use CMS. A thumb rule - Never use CMS to store transaction data. You can consume third parties and assign that data to your model to display content. Don't store it in CMS.

@@MySitecoreDiaries can you shown any demo like how we consume dynamic data using sxa ?

It is a custom dot net code depends on API. We hardly use it, infact in last 10-11 yrs of Sitecore experience i have never used it. If i encounter something then i will definitely create it. It is simply consuming API as we do in dot net.

You do not have to create it manually. It is an out of the box feature of Sitecore

@@MySitecoreDiaries sir can you share your no. are you given any paid services also.

Yes you can say it is the same but ideally the Content API is a wider concept. You have graph ql or layout service which can be used as a content api in Sitecore. Content API is a headless concept where content can be provided using API approach that can be anything like creating a api layer programmatically or using an outbox feature. Sitecore provides two options Layout Service which provides content in a specific format doesn't matter if you need all the data or not. graph ql which uses a query system to get specific data which you need. Both are outbox content Api mechanisms 👍

Apologies for same. can you tell me which device you have used?

Thank you. Do share video series whoever wants to learn Sitecore headless

Added in the todo list. Thank you for the feedback 🙏

Thank you

It would be difficult for me to provide a solution for your error without seeing it. Please share the error details, such as a screenshot and a description of the error, so I can further investigate and provide you the solution. Even you can email me the same. If you have tried everything and are still encountering an error, we have a strong Sitecore community and support system to help you. You can post your issue on the Sitecore Slack channel or raise a ticket with Sitecore Support. Thank You.

@@MySitecoreDiaries thanks very much to you how can i contact with where the gmail

Thank you for your message. I wanted to let you know that Sitecore Forms is already on my to-do list. Additionally, I’d appreciate your input on the topics you’d like to cover under Globalization. Your suggestions will help ensure we address the most relevant and impactful areas. For your reference, we currently have a video series on Personalization, which you can explore here: th-cam.com/play/PLt519PJr4jF9IBmOsClz2XiaLtAXx3pRW.html It would be great if you could provide a detailed list of topics or areas you'd like us to focus on. This will help in tailoring content that aligns with your expectations. Looking forward to your response!

@@MySitecoreDiaries is there any tutorial for jss with next jss and sxa using graph ql ?

Can you suggest what you want to include?

@@MySitecoreDiaries any complex component with lot of customization which would benefit to get detailed knowledge.

Thank you for the feedback. I will definitely consider your feedback. Thank you

I was thinking about that for a long time but now everyone knows the channel. Almost 2-3 yrs efforts 😀

Below 👇 is the playlist Sitecore tutorial for beginners | Sitecore XP for beginners | Introduction to Sitecore for NET developers: th-cam.com/play/PLt519PJr4jF-BN4MbDovbwNoKs35lr1fF.html Once you complete this series then you can go through our headless and xm cloud series. This will cover everything in Sitecore

Comprehensive Guide to Sitecore Headless Development | Sitecore JSS Tutorials: th-cam.com/play/PLt519PJr4jF9OHxFflJ8OzvWetbGTuHWP.html

Sitecore XM Cloud Certification Prep: Master the Essentials | Introduction to Sitecore XM Cloud: Getting Started: th-cam.com/play/PLt519PJr4jF_WIJ3lTLpS4tQQ_j6oKHdp.html

Thank you so much. Keep supporting by sharing this video with others.

React supports client-side rendering, while Next.js supports server-side and static rendering. In this video, we are using React, so it is focused on client-side rendering. If you want to know more details about it, watch our latest video: th-cam.com/video/8anzpg5O7mM/w-d-xo.html Thank You.

Thank you

The Experience Editor is used for designing pages. Creating or linking a stylesheet is part of the development process. You can add a style list name in your site settings and render it in the layout file. I am not sure about your specific use case. You can provide a list of classes for each component as properties or rendering parameters. Write code in your component to apply those classes. You need to create the stylesheet in the traditional way and link it in the layout file.

We are using the SXA site so it is already defined in the configuration thus we are disabling the site patch. For non sxa sites we need to use sitr patch configuration

Placeholder would be what you have defined in your layout item

It is defined in this Sitecore documentation doc.sitecore.com/xp/en/developers/hd/latest/sitecore-headless-development/layout-service.html#getting-the-output-of-the-whole-layout-for-the-item And also we can take it from our frontend app network calls in connected mode

Thanks for the feedback. I will soon upload code in GitHub.

Please email a screenshot of your api key item and the logs

Please email a screenshot of your api key item and the logs