[Zope-CMF] Customizing content types

[Reverend Matt]

Determining whether to extend or create new depends on the complexity
of the desired result.  The basic types that are included are just
that, basic.  They will work fine for the majority of cases, but when
they don't you have to determine if it makes more sense to extend or
build your own new one.  

I opted to create a new one with PABlog, and it was a learning
experience (and continues to be).  

I recommend checking out:
http://cmf.zope.org/doc/FAQ/development/faq_4_8

http://www.zope.org/Members/digitalis/basic_cmf_product/how_to

http://plone.org/documentation/howto/HowToWriteYourOwnContentType




--- In zopeCMF at yahoogroups.com, David Chandek-Stark <dc at d...> wrote:
> I am engaged in a pilot project migrating a web site into Zope/CMF.
This 
> may involve customizing some of the CMF content types (adding 
> properties) and/or creating new content types. I'm beyond the newbie 
> stage with Zope and the CMF, but can't see far enough down the road for 
> potential pitfalls. I'm concerned about upgrade problems with
customized 
> CMF content and, in general, the sustainability of such a project. 
> Obviously it's a lot easier to simply make do with the CMF types, 
> perhaps bending the meaning of Dublin Core to accommodate the metadata 
> we want, but we'd prefer not to do that.
> 
> I've read the CMF Dogbowl how-to on Scriptable Type Information objects 
> and the ZopeLABS article on adding custom properties to CMF default 
> content. How does one determine whether to add a custom property to a 
> CMF type or to create a new scriptable type altogether?
> 
> Thanks for any help, advice, thoughts.
> David
> 
> -- 
> David Chandek-Stark
> dc at d...
> 
> 
> 
> _______________________________________________
> Zope-CMF maillist  -  Zope-CMF at z...
> http://mail.zope.org/mailman/listinfo/zope-cmf
> 
> See http://collector.zope.org/CMF for bug reports and feature requests