I'm Bluffing

How to keep track of what Sitecore items have been published I recently got this question from a colleague who was looking into a customer reported issue. He was wondering if he could see if this specific page/item has already been published. The default answer here would be to check the "Web" db or any other publishing target. However, this is a tedious task when checking multiple pages as well as when these pages are nested deeply within your root structure. So I decided to see what the web had to offer with regards to this. I first found a Sitecore answer that gave a list of the Items that were in the publish queue. This provides insight into what has NOT been published yet. But does not show what HAS been published: http://sdn.sitecore.net/Forum/ShowPost.aspx?postid=26498 This was however not what I needed, an I continued on... The solution come from Stack Exchange: http://stackoverflow.com/questions/15172346/sitecore-flag-new-items-as-unpubli...

Multi-Site setup with Sitecore Sitecore is in my opinion one of the easiest CMS's out there to facilitate a multi-site setup. It offers a number of approaches to doing so. You can either create entirely different structures and implement it as such so that through security and configuration entire different structures can be disclosed while at the same time specific content can still be shared in one location. But you can just as easily decide that a specific node within your website should function as a seperate site with its own visualisation and behavior. For example, you might want the following structure within Sitecore : " Corporate Home > Tertiary pages > B2B > Support " to be disclosed under the following url: http://www.corporate.com/support/ In order to do so I tend to revert to the Virutal Site setup that is available within Sitecore How-To Siteore configures its mapping of the various path, hostnames, databases and so on thr...

Case A web editor has created a large amount of content that is ready to be published. However, in order to get the final 'OK' on this newly created content, he needs to get the buy-in of specific persons in the company. The default answer here would be to use the Sitecore preview mode or use well devised workflows within sitecore that are automatically notifying the correct group of persons by sending mails or updating their RSS coupling (in outlook for example). These notifications would in turn push the stakeholder into taking the right actions needed to ensure the content gets published in the correct form. However,  what is the best possible approach if your target audience has no knowlegde whatsoever of Sitecore? Users that don't have an account and can not (or should not) be motivated into adopting your well designed Sitecore content approval approach ? At that point the Sitecore Live Mode can come into play and offer a relatively elegant solution. ...

DateRange utility class Throughout development there are a number of typical things that tend to recur. One of these is implementing a means to display start and end dates for News, Events, Symposiums, Lives etc etc Writing a little class that manages printing these dates seemed like a necessary task that just had to be done in order to make this tedious task be a thing of the past. Therefore I created my "DateRange" class (what's in a name) that should handle this entirely for you. The Idea The intriquities of displaying a datetime range should be an abstraction. You should only need to worry about passing the correct dates (start and end - if applicable) to the Utility class combined with an optional formatting. The class can be entirely configured through use of Enumerations for all the separate settings such as DayFormat etc. An additional class was used to implement this utility, the StringValue attribute class. You can easily use thie class to a...

Even though I know that the HTML 5 standards and features are slowly becoming old news, there are still a number of features that we haven't incorporated into a lot of projects until now. So after doing some research on the topic of Offline applications and how to use the local storage I set out to build a simple proof of concept. Using the information I found on the following sites : http://www.code-magazine.com/Article.aspx?quickid=1112051 http://www.w3.org/TR/offline-webapps/#offline http://html5demos.com/html5demo.appcache http://www.html5rocks.com/en/tutorials/webdatabase/todo/ I was quickly able to create a simple project that allows for users to register themselves. Registration is then handled by a manager class that does nothing more than append to a file. If you are in offline mode however, the system still allows for the pages to load and to register. Once the internet connection is recovered, the page will synchronize the registrations to the manager...

Since I've been wanting to look into creating an application that is capable to work in offline modus asswell i've decided to create a blog so I can report on my progress and other nice to know implementation tricks or technologies.