Digital Transformation using Digital Technology

Sitecore 10.1 Vanilla installation on Developer machine   Step 1. Install Visual studio 2019 Step 2. Install SQL server 2019 (Developer edition) Step 3. Copy all the setup files and tools at shared location with full rights   Step 4. Browse “Sitecore 10.1.1 rev. 005862 (Setup XP0 Developer Workstation rev. 1.2.3-r6)” folder and run setup.exe in admin mode Step 5. You should be able to see SIA installation screen, click on Start button to start installation Step 6. SIA complete the entire process in 3 parts, first part installed all required Sitecore 10.1 prerequisites. Step 7. Once Prerequisites are installed restart the development machine and open setup.exe again in admin mode (refer step #4). Once SIA will be started then don’t click on Install button again for “Prerequisites”, just click on Skip. Step 8. As I said in Step #6 that Sitecore does installation in three parts, so this is second parts where you will have to pass require parameter to setup solr and sql

Custom Caching with Sitecore Caching has been always black box and full of surprise, if we define caching strategy in our application it will do surprise with the performance and if not then will create mess. Let's first understand Caching A cache is a temporary storage area. Caching works best with data that change infrequently. Caching makes a copy of data that can be returned much faster than from the original source. What we have in Sitecore for cacheing Sitecore internally uses various caches to Store data, Render presentation logic In-memory information in order to improve performance and response time.These are caches that inherit from Sitecore.Caching.CustomCache class . Let's talk about how we can implement custom caching in SItecore Custom Caching component provides capability to cache application specific items. e.g., Site configuration, Custom View Model etc. We can have following caching implementations which are injected at runtime based on the config

  Overview This document is intend to provide guideline to understand requirement of the multi locale, multi brand and multi lingual capability. In the other section of the document there is guideline how to design architecture of the website which is having requirement of Multi locale, brand and language. Requirement 1. Multi Locale When delivering contents in multi locale and multi lingual site we have to be aware that, apart from the mere translation, other adjustments, such as date and number formats, currency have to be made. The topics Internationalization and localization are extensive cross-section concerns, where the implementation is definitely not trivial. Locale languages on Sitecore use the format ll_CCc, where ll is a two-letter language code, and CC is a two-letter country code. For instance, en_US represents U.S. English. Sitecore support many ISO languages and country codes Multi-locale should support all data Format 8 byte (UTF-8) encoding. We might need to cha

Objective Whenever we think of CMS systems, the first thing that comes to mind is the content and its availability in different languages. Today's websites are global in nature, so businesses need localized content over their websites. It is possible to have a regional website in addition to a localized website. In Sitecore, content authors can create content in different languages, although this is a manual process that will take a great deal of time and require specialized skills for authoring.  The application takes one version of the content (default) and provides localized versions in various languages. In order to meet this type of business requirement, Globalization Partners International(GPI) is one of the providers available in the market to provide such services. Description The GPI provides translation and localization services for website content. It provides Sitecore connector which allow content author of websites to initiate translation workflows.  There are f

Sitecore is having matured logging mechanism which logged all kind of log from CMS and CD site It's does provide different kind of mechanism to view the logs like: SCLA(Sitecore log Analyzer) Sitecore Admin tool for log  Application insight(PaaS only). SCLA  SCLA is very handy tool to view Sitecore generated logs. It provides different filter to view different kind of log. This tool is still got unofficial support till Sitecore 9.2 (on-premise).We can find very good documentation at Sitecore portal for Sitecore 9.3 onward (Azure based )  : Documentation . I tried to explain on-premise Sitecore instance, the important part which we always look for during debugging. 1. First we need to map the log file path then click on Analyze button. 2. We can apply date filter or by default it's disabled. 3. We have different tab like Messages,Audit,Health Monitor,Raw View and Internal program Log 4. In Message tab you can there are four different check box for Error, Wa

Localization of content of website Objective: To reach globally, every organization planned to localized the website which means that content of the website would be available in the user own language, which will give comfort to end user and it will be easy to communicate. Points need to follow: To localize a website successfully, there should be very clear defined policy from functional and clearly adapted by technical. Since localization mistakes and oversights can be awkward for website users and potentially embarrassing for the company, make sure to get it right — it's absolutely worth the time and effort. We need to pay attention on some couple of points: -              Dates: Need to have clear understanding that which date format is being used at which place and should get displayed in that format. E.g. Month, day, year vs. day, month, year. -              Time: Weather  the time cycle should be 12-hour vs. 24-hour time. -              Color: Avoid loca