It has been few weeks since we have released the all new and shiny developer manual. As promised we’ve been updating it since then (though the Monday thing failed miserably, we’ve managed to update manual once per week – so that’s how it’s going to be from now on – once per week :).
So here is a little overview of major updates:
In the coming weeks, you can expect additional topics in Adding new Generic Content based module section, ContentViewDesigners overview with samples for modifying or extending them - and finally security samples across all types of custom modules (Intra Site, Pluggable and Generic Content based).
Also, we are working on Templates Map section which will provide quick and simple lookup for all control templates in Sitefinity, what they do, how they look like and how can they be safely modified without losing your changes on the next upgrade.
If there is anything else you think is a top priority for Dev Manual, leave a comment and it’ll make its way into the manual.
Greetings from our small, but brave (!), dev docs team.
So here is a little overview of major updates:
- Events API overview
http://www.sitefinity.com/help/developer-manual/events-api-overview.html - Bare-bones Pluggable module Visual Studio template
http://www.sitefinity.com/help/developer-manual/adding-new-modules-pluggable-bare-bones.html - Images and Documents API overview
http://www.sitefinity.com/help/developer-manual/libraries-api-overview.html - Adding new Generic Content based module
http://www.sitefinity.com/help/developer-manual/overview.html
In the coming weeks, you can expect additional topics in Adding new Generic Content based module section, ContentViewDesigners overview with samples for modifying or extending them - and finally security samples across all types of custom modules (Intra Site, Pluggable and Generic Content based).
Also, we are working on Templates Map section which will provide quick and simple lookup for all control templates in Sitefinity, what they do, how they look like and how can they be safely modified without losing your changes on the next upgrade.
If there is anything else you think is a top priority for Dev Manual, leave a comment and it’ll make its way into the manual.
Greetings from our small, but brave (!), dev docs team.