Friday 17 November 2017

3A Approach with Sitecore Componentization

Before starting development with Sitecore, if we have any prior idea about the components then it will save our times while development and as well as will be full proof.
As per my previous projects experience, always followed the componentization trick and result was great .
Generally in normal project we have around 10+ components.
And believe me once our componentization documentation is ready you feel like everything is done just need to do implementation thing. Because after this we are able to identify which components is getting repeated on which page and after that will have to apply only that rendering on particular pages.
So let's start focusing on creating Componentization Document then next jump to development.
For this Always following the 3A Approach:
1. Authorization
2. Accessibility
3. Action
This 3A magical things helped me a lot. Here I am taking an example of e-commerce site (AMAZON) for reference, please go with attached image first after parallely visit on https://www.amazon.in/ (for reference) can easily see that on the attached image things are in form of component like:
sitecore-components

On Home Page we have:
Header
Logo
Navigation
Search

Body
Carousel
Image Slider
Image Title Description Widget
Image Title Widget
Title Description Widget
Back To Top Widget
Image Links Widget
Teaser(Offer) Widget

Footer
Footer Links
Copyright

here on the homepage components are getting reused just by changing their data source. And if we jump to another page will see their header and Footer components are same just their body part will be little bit changed with some of the new/reused components.

For Proper Documentation, I shared sample Componentization Documentation, Please have a look.

Any feedback/Suggestions/Advice are welcome!!!

Tuesday 7 November 2017

Handling 404 Error Page with Sitecore

Wanna create your own PageNotFound with Sitecore?

Suppose a scenario, where an end user is hitting wrong item and he is getting some technical error (which can not be generally understandable by End User), and you wanted to show him your own page.

Then I would like to say it's cool and quick change with Sitecore, we just need to make an entry into Sitecore Config(<instance name>\Website\App_Config\Sitecore.config) and have to create your own aspx file that's it.


Let's start a quick demo step by step:

1.  First created PageNotFound.aspx file and put it at location [<Instance Name>\Website\PageNotFound.aspx]


2. Second after this made entries to Sitecore.Config [<instance name>\Website\App_Config\Sitecore.config]


404-errorhandling-config

That's It....

custom-404-page-sitecore


@Note: Actually here we are redirecting PageNotFound: 404 Error type with Permanent Redirect: 302 by creating our own user friendly Page.

Please let me know if any feedback or suggestions.