Recently we just upgraded from Sitecore version 8 to 8.1.
One major thing to note. It is preferred that all unique configurations be done within the Sitecore patch files, not in the Sitecore config files themselves. Our senior developer mentioned that at anytime you should be able to drop a fresh install's config files (of the same version) in any site and the site should function the same. Your independent, unique configurations should always exist in the patch files.
Here is a link to the Release Notes for 8.1: (Click Here)
Here is a link to the Known Issues thus far: (Click Here)
Initial Release Base Page: (Click Here)
Good luck in your upgrade, be sure to comment on anything that you may discover along your journey.
Enjoy!
Welcome to the kmacnbama blog. I am a .NET developer focusing mainly in the C# and Sitecore realm. I am also an aspiring Sitecore MVP. In my blog I discuss various topics around CMS development, focusing mainly on Sitecore. I have used quite a few CMS (Content Management System) engines to allow users to easily update and organize content.
Showing posts with label MVC. Show all posts
Showing posts with label MVC. Show all posts
Jun 13, 2016
Jun 12, 2016
From Ektron to Sitecore
There was a time in which I was employed by an Ektron Platinum partner. I rose through the ranks in which I ultimately became the senior developer on staff. It was up to me to stay up to date with the latest and greatest trends in web development as well as anything Ektron.
Well like anything else in life and corporations, change happens as well as corporate direction. Off we went to San Francisco to get Sitecore certified. Needless to say the systems are different. And like anyone in any profession learning a new system, one tries to relate the similarities and learn the differences.
One similarity between the two systems lie in several sections. One in particular are Ektron smart forms and the Sitecore templates. Sitecore templates seem to be the foundation of how data is structured for the content contributor. Templates are set up to ensure data entered by the content contributor is structured in a fashion the coders can add logic around to produce the desired output. Ektron smart forms had that same direction. Structured data to be entered by the content contributor for the developer to add logic around. This type of data also includes configuration values to have the site's behavior configurable.
One difference is that Ektron had web form controls to developers could drag on an aspx page and add some configuration items and Ektron data would display. Modern Sitecore doesn't however add this feature because it leverages .NET in a more true fashion to allow the developers to create their own fully customizable renderings/sub layouts.
Between the two systems there are more differences than similarities. Whichever system you decide to work with, I suggest you fully involve yourself in the system to become a true expert. As for me, I am looking deeper into Sitecore and quite frankly I am glad I have. It really gives me the ability to use a true MVC approach and allows unlimited possibilities to which makes our solutions that much more attainable.
Enjoy!
Well like anything else in life and corporations, change happens as well as corporate direction. Off we went to San Francisco to get Sitecore certified. Needless to say the systems are different. And like anyone in any profession learning a new system, one tries to relate the similarities and learn the differences.
One similarity between the two systems lie in several sections. One in particular are Ektron smart forms and the Sitecore templates. Sitecore templates seem to be the foundation of how data is structured for the content contributor. Templates are set up to ensure data entered by the content contributor is structured in a fashion the coders can add logic around to produce the desired output. Ektron smart forms had that same direction. Structured data to be entered by the content contributor for the developer to add logic around. This type of data also includes configuration values to have the site's behavior configurable.
One difference is that Ektron had web form controls to developers could drag on an aspx page and add some configuration items and Ektron data would display. Modern Sitecore doesn't however add this feature because it leverages .NET in a more true fashion to allow the developers to create their own fully customizable renderings/sub layouts.
Between the two systems there are more differences than similarities. Whichever system you decide to work with, I suggest you fully involve yourself in the system to become a true expert. As for me, I am looking deeper into Sitecore and quite frankly I am glad I have. It really gives me the ability to use a true MVC approach and allows unlimited possibilities to which makes our solutions that much more attainable.
Enjoy!
Subscribe to:
Posts (Atom)