Friday, July 7th I began my new series “A Different Approach” with the post about injecting resources into the experience editor. After I made my that post live, I continued my research and I became increasingly unhappy with my solution described. There is a better solution that solves my issue and that solution is somewhere in this post! 😮 Continue reading “The Better Solution: Injecting Resources into the Experience Editor”
Welcome to the first post in a new series called “A Different Approach”. Often when I search for a solution to an issue, I find multiple posts that solve the issue in a similar fashion. Since I have a strong need to be unique, I try and come up with a different approach. In this new series, I’ll share the most common solution found, cite the source(s) and explain my unique alternate approach. In the event my approach is not all that unique and is similar to another, please inform me and comment below. I will happily update my post giving credit to the developer and providing a link to their post.
Last week in my “Mister Rogers” themed post, I presented an issue a client had with the Experience Editor and then showed you my solution to that issue. My code contained some HTML markup with custom CSS classes. In order to complete the video demo by the end of last week, I took a shortcut and hardcoded the style definitions above the markup in processor. This is unacceptable for numerous and obvious reasons.
♬ It’s a beautiful day in the Experience Editor, A beautiful experience for an author, since we’re together, we might as well say, won’t you be my Content Author? ♬
Hi, Sitecore Neighbor, I’m glad we’re together again… discussing new cool ways we can help provide the friendliest authoring experience an author can have while using Sitecore’s Experience Editor! Continue reading ““All it takes to turn a grouchy Experience Editor Friendly is a little TLC.” – Mr. Rogers”
Remember that time when developing for the Page Editor (now known as the Experience Editor or “EE” for short) was an afterthought or often just outright ignored? If you are like me, you’ve buried those memories hoping to forget those days even existed. Today, having a friendly Experience Editor… experience is one of the more important aspects of a successful Sitecore implementation. Whether the client has plans on using personalization, xMarketing, etc. or not, neglecting the EE is a huge mistake that’s still commonly made.
For a long time, I ignored the Page Editor. I admit it, albeit shamefully. My attention was elsewhere and some (unintentional) bad habits developed circa 2006 lasted longer than others. It wasn’t until I began my career at Paragon Consulting, Inc. in 2014 that I corrected those bad habits. I became fully aware of my sins against Sitecore’s standards and best practices and in the years since I’ve made the EE one of my main areas of focus. Continue reading “Understanding Glass: The issue with the Editable Method and Paragraph Tag”
These videos should be beneficial to those developers who want to make custom Sitecore fields that can be rendered and edited with Glass. I am still in the process of cleanup and code refactoring. I also am going to attempt to improve the documentation of the code. As I have mentioned before, I am a perfectionist and this “Proof of Concept” is not up to my standards… yet. I got into a little fight with a few small bugs last night and that battle’s remnants are still scattered throughout the solution. However, the code will still be available in its non-pristine condition.
I mentioned in the first video I would be uploading 2 Demos, however, to keep the videos shorter, I broke them up into 4 videos. As usual, I didn’t stop Vlogging/Blogging for unimportant tasks, like sleeping, eating, moving… I was exhausted and in my opinion, you can hear the grogginess in my voice set in on the Demo 3 video. Continue reading “LivePhotosKit API, Sitecore & Glass Integration: Demoing the Functionality and Code”
It’s been a LONG two days, but I am finally finishing the last post in the 4-part series. My idea took weeks longer to implement than I originally planned. I procrastinated by mistake. I don’t know why, but I was under the impression ‘procrastinate’ was a synonym for being ‘proactive’; turns out, I was incorrect. I guess I am still capable of learning new definitions at my old age.
If you read the first three chapter in this series, you should be somewhat familiar with the important aspects of integrating LivePhoto, Sitecore and Glass. If the concepts are a lil hazy, Click here for a recap of the most important pieces that you should know more about. Continue reading “Apple’s LivePhotosKit, Sitecore & Glass: Chapter 4 – Rendering & Editing the Live Photo in the Experience Editor”
It’s 4:59PM Friday afternoon and your long work week is almost over; one minute away from 48 hours of non-stop, fun-filled, Mountain Dew fueled LARPing. Just as you stand up to leave, your work phone rings and it’s your favorite client. Going against your better judgement you decide to be nice and answer.
“Help Hasagn Sailorslayer! Thoust Dragon Smaug breathed fire on our site and tis no more!”… the client says while speaking with a horrible British accent. “I swear, all I did was a publish and now the entire site is erroring!”.
The client provides you with all the vague, helpless information you’ve come to expect and now your weekend of throwing lightning bolts may be delayed.
After a half hour and a couple hundred “WTFs” you remember Sitecore troubleshooting basics. You check the logs and find an object reference error on the “Main Navigation”; somehow the client deleted the Main Navigation’s datasource item while ignoring common sense and Sitecore’s warnings. You restore the deleted item and the crisis has been adverted, the client is happy and you begin to rethink the client’s request of needing full admin privileges.
There are a lot of ways we could prevent this error from happening. Continue reading “Don’t Let a Datasource Error Delay Your Weekend of LARPing”
Let’s pretend I inherited a very old Sitecore implementation that was developed in the dark ages back in 2010 using Sitecore version 6.4. Before version 7 and the renaissance, the history books tell us that this period was very dangerous, the Page Editor was largely ignored, template and field proliferation was widespread and anarchy reigned supreme. Continue reading ““MySpace” the Content Editor – Customizing the Content Editor via the Rules Engine – Part 3: File Mapping”
Yesterday morning, I was asked to implement the Customized Content Editor module on a site Cris (project lead) and I are currently rebuilding. Cris was impressed with the module but had one request; she requested the modified field names appear in the Experience Editor as well. Without thinking through all the aspects of why her request was valid, I quickly responded that since the content author can visually see where the field is located that they are editing, the field name is irrelevant. Cris disagreed and brought up a good point. If the content author was to switch back to the Content Editor, they would be confused as to which field they were previously editing. Since we are on a tight deadline (two weeks), she said if it was too time consuming we would implement it in phase two. I finished the task I working on so I decided to give her request five minutes of research. I quickly discovered Cris’ request would be easy and quick to implement; 30 minutes later it was complete. Continue reading ““MySpace” the Content Editor – Customizing the Content Editor via the Rules Engine – Part 2: The Experience Editor”
Joking! Although it’s totally possible to “MySpace” the Content Editor, there are better ways to customize the Content Editor.
A couple weeks back a colleague asked me what I thought about the possibility of changing the display name of a field on a case by case basis. As we discussed the usefulness of this idea, I had already started researching. With one of my favorite development tools “JetBrain’s DotPeek” open, I searched the Sitecore kernel and discovered that not only is my colleague’s idea possible, but implementing it won’t create future Sitecore upgrade headaches. Continue reading ““MySpace” the Content Editor – Customizing the Content Editor via the Rules Engine – Part 1″