I am evaluating Articulate for my employer's website and I find it great. However I will need some custom properties added to the doc types as there is real need of it- one of it being a custom image picker which helps us include image from our stock photography portal. Will it pose problems if we start adding custom properties to the doctypes. Can it create trouble if we are to upgrade Articulate in future?
If you mean adding property types to blog posts, etc... that is totally fine and won't break upgrades.
Since Articulate uses strongly typed models, you will need to access your custom properties the normal IPublishedContent way like GetPropertyValue<string>("myProperty") (the strongly typed models used are instances of IPublishedContent)
I'd recommend just giving it a try, you've got nothing to lose :)
Evaluating Articulate
Hi community,
I am evaluating Articulate for my employer's website and I find it great. However I will need some custom properties added to the doc types as there is real need of it- one of it being a custom image picker which helps us include image from our stock photography portal. Will it pose problems if we start adding custom properties to the doctypes. Can it create trouble if we are to upgrade Articulate in future?
Any help is much appreciated
Poornima
If you mean adding property types to blog posts, etc... that is totally fine and won't break upgrades.
Since Articulate uses strongly typed models, you will need to access your custom properties the normal IPublishedContent way like
GetPropertyValue<string>("myProperty")(the strongly typed models used are instances of IPublishedContent)I'd recommend just giving it a try, you've got nothing to lose :)
I am definitely going to give it a try. I have a prototype set up! Thanks for the very prompt reply Shannon :-), across all the channels.
Poornima
is working on a reply...