If you are reading this, chances are you have noticed that Alagad.com was given a little bit of a makeover. Besides getting a new coat of paint, we also ripped out all the plumbing and replaced it with FarCry. Most people would descibe FarCry as a content management system (CMS), but it is much more than that. FarCry is more of a framework, on which the CMS we all know is built.During development the Alagad team ran into some walls, which stemmed more from unfamiliarity with FarCry than anything else. Over the next few weeks, I plan in putting together a series of entries that will details some of the issues we encocuntered, how we got around them and stuf we leaerned about FarCry as we went along.The purpose of this entry is to offer some high level advice if you decide to head down the FarCry path.
- FarCry is a framework. It will take time to understand the workflow,and inner workings. Give it time. Developing in FarCry gets easier the more you do it.
- Let FarCry do what it was designed to do. FarCry handles things on the backend differently than you probably would. Embrace this, don’t fight it.
- http://groups.google.com/group/farcry-dev?hl=en should become your best friend. The list is fairly active, and frequently the development team for FarCry will respond to your questions.
- http://docs.farcrycms.org:8080/confluence/dashboard.action should become your second best friend. While not perfect, the documentation for the latest versoin of FarCry are better than in any other version.
Here is an incomplete list of items I plan on covering in upcoming entries, if there is something you would like to see, please leave a comment.
- Creating Custom Content Types (objects)
- Creating and Using Display Rules
- Using FormTools
- Overriding Native Methods