More in this section
Forums / Suggestions / Widget vs Module

Widget vs Module

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
3 posts, 1 answered
  1. Marc
    Marc avatar
    24 posts
    Registered:
    09 Jun 2011
    27 Jun 2011
    Link to this post
    Still real green when it comes to Sitefinity and I am having to make the decision between building some custom functionality as a module or a widget.  I know the basics of widgets and modules and have built a couple of each, but I am curious what thoughts go into deciding between a widget or a module when functionality of the new feature could be accomplished in either.  I figured it mostly related to permissions, localization, ect. but couldn't find a post or documentation with a breakdown relating the two and when to go with one or the other when building out a custom solution.  Thanks in advance.

    Marc
  2. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    28 Jun 2011
    Link to this post
    The way I look at is is if I need to have separate db tables to store data, or the same data needs to exist on multiple pages...then I go module, and then widgets are your front end view to that shared data. If I just need something simple data specific to a page, then go widget
    Answered
  3. Marc
    Marc avatar
    24 posts
    Registered:
    09 Jun 2011
    28 Jun 2011
    Link to this post
    Thanks Steve, so the main focus when choosing a path should come down to if you need to encapsulate data in a repository which needs to be used on multiple pages you should go with a module.  But if your solution does not require multiple pages to show your data creating more of a  one-to-one relationship (one piece of content to one page) then a widget may be a better plan as the data can exist within the page without the need to persist it to a seperate table structure. Am I understanding this correctly?  Also, can categorization, tagging and annotation of content still be utilized if using a widget?
3 posts, 1 answered