[ckan-discuss] CKAN custom development

[Dominik Moritz]

Hey,

Great, feel free to ask questions on the dev mailing list. Also, even though sean is still working on them, there are experimental docs for writing extensions at [1] which might be helpful. I think they are already great, but keep in mind that these docs are not released yet.

Best,
Dominik


[1] https://github.com/okfn/ckan/pull/943 There is a link to the built version of the new docs

On 1 Jul 2013, at 23:04, Pabitra Dash <pkdash_reena at hotmail.com> wrote:

> Hi Dominik,
> 
> Appreciate making this clear to me.  Now I think I can focus on how to create a new CKAN extension. I need to create a 'Hello World" type extension first in order to grasp the concept as well as the process of creating an extension. I am using the information at http://docs.ckan.org/en/ckan-2.0/extensions.html to create my "Hello World" extension. Hope it won't be too difficult of a journey.
> 
> Thanks, 
> Pabitra
> 
> Pabitra Dash
> 
> Utah State University
> Logan, UT
> pkdash_reena at hotmail.com
> 
> 
>> Subject: Re: [ckan-discuss] CKAN custom development
>> From: dominik.moritz at okfn.org
>> Date: Mon, 1 Jul 2013 21:48:52 +0200
>> CC: ckan-discuss at lists.okfn.org
>> To: pkdash_reena at hotmail.com
>> 
>> Hey Pabitra,
>> 
>> We suggest that you use extensions for all customizations. This will make sure that you don't break any core functionalities and keep CKAN upgradable. Also, it's a lot easier to get started with a new extension than to change the CKAN core. If you need to change existing functionalities, you can do that in an extension. Basically all core functionalities can be overridden in an extension. Furthermore, the templates can be overridden and you can make CKAN look totally different if you want to do that. You can find example CKAN instances at ckan.org/instances which were customized using extensions. 
>> 
>> My suggestion is to always make customizations in a extension. If something is not possible in an extension, we should try to add an extension point to CKAN so that you can make your customizations in an extension. 
>> 
>> I hope that this answers your question and I'm happy to help if you have any further questions. 
>> 
>> Best wishes,
>> Dominik
>> 
>> On 1 Jul 2013, at 20:35, Pabitra Dash <pkdash_reena at hotmail.com> wrote:
>> 
>>> I am new to CKAN and I am not sure if all custom code development to add new features have to be implemented as CKAN extensions. What about changing any of the existing functionalities?
>>> 
>>> Thanks
>>> Pabitra
>>> 
>>> Pabitra Dash
>>> 
>>> 
>>> pkdash_reena at hotmail.com
>>> 
>>> 		 	   		  _______________________________________________
>>> ckan-discuss mailing list
>>> ckan-discuss at lists.okfn.org
>>> http://lists.okfn.org/mailman/listinfo/ckan-discuss
>>> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-discuss
>> 
>> Dominik Moritz
>> CKAN developer  |  skype: d.moritz  |  @doobly_doo
>> The Open Knowledge Foundation
>> Empowering through Open Knowledge
>> http://okfn.org/  |  @okfn  |  http://ckan.org  |  @CKANproject
>> 
> 		 	   		  

Dominik Moritz
CKAN developer  |  skype: d.moritz  |  @doobly_doo
The Open Knowledge Foundation
Empowering through Open Knowledge
http://okfn.org/  |  @okfn  |  http://ckan.org  |  @CKANproject