This is a very short post to draw your attention to the Agnostic IoC and Lucinq documentation that I have been putting together during recent weeks.
You can access this via the menu’s at the top. If there is anything you need clarifying or would like documentation on, please let me know, your feedback is invaluable.
Here is something that I have found all too often in my career working with a multitude of CMS systems, and it is this :-
Sitecore is not a product that you can build for a customer and then forget about, customers to get the best from their solutions should be hand held, communicated with, and as developers / vendors – this provides long term work opportunity. It is all to often that (especially in the Digital Media Agency environments) I find Developers blindly following a spec (often written by someone who does not know the framework) and not considering the bigger / long term picture. In my experience, this often leads to a lot of work later that would have been next to no work during the original implementation.
In my post on The parallels between single language and multi-language developments I covered just such a question. It eludes to statements you will often here from clients which could include (but far from limited to), things like:
- We will only ever have an English site
- We will only ever run one site on our Sitecore solution
- We will always use workflow
Our journey in development should always be governed by a mix of knowledge gained through a variety of mediums, the fact you are even reading this post suggests you are eager to learn more about the product(s) you work with. This added to your own experience and the shared experience of your wider team should lead to you making ever increasingly better decisions with each solution you build. So my responses (based on my own experience and in my head) to this are usually something along the lines of:
- Really…..? Your ‘massive’ brand that you have sold us on since the pitching process has no plans to EVER consider beyond the English market?
- Ok – so your CEO is going to build your brand and sit on their ass and watch the money fly in without thinking – ‘hey we could make some more by..’
- You really haven’t thought about basics like – every image, every tiny translation change… well just… EVERY CHANGE! It’s great that some clients have vast content entry teams with the resources to achieve this. Many clients though will end up with an army wanting ammo and a single guy with the keys to the ammo store (chips down – that guy is gonna get a beating).
The above are all examples of me using my experience / knowledge to question whether the decisions that have been made (often in the developers absence and often by sales / accounts folk) will actually hold up.
Ok, so I am sitting in the lobby of the Palau de Congressos de Catalunya for Sitecore Symposium, I guess I should be writing about my experience, my views on the fantastic marketing features and technical innovations that have been presented to us during the event. However I find myself equally struck by the ease in which developers, marketers and other staff have communicated at a large European event with so many different cultures and how welcoming it has all been.
It got me thinking about something I have had on the back burner for a while and it’s time I sorted it out. I will start with this statement; ‘It is my belief that in the majority of respects, building a great Sitecore solution is almost completely the same regardless of whether you are building for single language, or building for multiple languages’. There are also of course a few important differences but that will be outside of the scope of this post, let’s focus on the basics.
I have finally got around to release Maps for Glass Mapper as a Nuget package. This module provides a really nice way of mapping your POCO’s through Glass Mapper using mapping generics. I also have an implementation of Glass using Autofac / StructureMap and Unity available on a private feed if anyone would be interested in testing?
> nuget install Cardinal.Glass.Extensions.Mapping