Recent Posts and Articles
The Orchard Team has been hard at work and has just released 0.8.
This is an exciting milestone because it means that both the extensibility and theming infrastructures are now in place.
That means we can start building on Orchard and expect minimal changes when Orchard goes v1.
I’ve been now developing against Orchard for a while and with latest bits from Orchard dev branch everything is looking very good. My main problem has been with the setup of a development environment so that I can update to latest version of dev branch and still keep my own modules in their own source control repositories. I think I’ve found my ideal setup which I’ve used for couple of projects one of which is Syntax Highlighter for Orchard.
Okay, So i couldn't wait. I haven't downloaded the source code in a while and thought why not take a peek around.
I think the Orchard team has focused mainly on striping out their old theme engine to make place for the new old, and I have to say I am impressed. The new theme engine hangs off the work that the Razor boys have been doing along with support for WebMatrix – which is fantastic to see.
The Orchard Project Beta (www.OrchardProject.net) was announced some time ago and I’ve been working with it since.
One of the special challenges in building a framework that can be used as a “Content Management System” is that WHAT content the end user will manage can’t really be known at development time.
Orchard takes a flexible approach to solving this problem by supporting both user defined content types as well as user defined “field” types”.
These last few weeks I’ve been refraining from starting any deep work on my new Orchard-powered blog because most of what I had in mind involved widgets, which are being built right now. Version 0.8 is just around the corner: the team is just putting the final touches to the new theme engine and to the widget system.
In the meantime, there is still some work I could do that I knew would not be throw-away, and that is CSS.
Microsoft announced last week that it was scrapping its Windows Live Spaces blogging technology, and would make Automattic's WordPress the default blogging platform for Windows Live. Couldn't Microsoft's Orchard, the three-year open-source project to provide a general-purpose website publishing and blogging platform, come up with the goods? Sadly, it is just bad timing: Orchard is only half way through its development, which aims to deliver far more than just a blogging platform. It promises an extensible architecture and a complete set of reusable components from which you could easily assemble a web-based application that is exactly tailored to your needs, the IT equivalent of Lego. At the moment there is nothing quite like it on the market.
Today I make my rounds on the usual sites to catch up with the likes of techie news and the such and I see great news that Microsoft has decided to axe Windows Live Spaces (http://news.cnet.com/8301-13860_3-20017745-56.html?tag=topTechContentWrap;editorPicks) though I think this is a partially good idea, I cant understand there reasoning behind wanting to move to word press.
There are three cornerstones to a content management platform - extensibility, storage, and display. The first milestone of Orchard revolved around the first two and the next push is taking a look at the third.
It takes a large leap of faith to retrofit the rendering system of an application. If the retrofit is based on significantly different concepts you don’t really have a choice but to enter a period of almost total loss of functionality. So here we are - jumping the canyon - looking forward to getting all of the modules back online over a new display system.