Welcome to Sitefinity!
We already have a module for News. If you're looking for increased functionality to the existing News module you can add/remove custom fields by going to Content > News and in the right-hand panel you will see the additional fields option where you can add/remove custom fields such as images. Adding/Removing fields will automatically update the backend inserts so you can use the custom fields. To display the custom fields on the frontend you would just need to modify your template to include them. Most fields can be added with an Eval() statement so something like <%# Eval("CustomFieldName") %> would display it.
As far as pushing to social networks you can do this through our Publishing system. You can see that in Administration > Feeds &Notifications.
I hope this helps.
That dynamic data is controlled by a designer. It seems like you're talking about a banner widget... something that you can add/remove images from dynamically to show on the frontend. If so, definitely possible. There are a couple on the marketplace already from third party developers. We also have a blog post on this.
Essentially when you create your widget you will specify public properties.
You may be using Visual Studio express then? It should work with visual studio 2010 and up if it's not express.
But yes that's entirely possible from a few different approaches. If you just need a list like that then you can create a custom module through Module Builder. This will generate a list view based widget for you based on the fields you selected which you can style using CSS/JS to get the appearance/mobility of your example. You could then use tags/categories as a filter mechanism and the module builder has image fields. Either this way or a widget would work it just depends on how you feel comfortable approaching it.
That would explain the extension problem then. Thunder is definitely a powerful tool while developing for Sitefinity so if you have the ability to upgrade to a higher version of visual studio I would definitely suggest it.
Your approach would work. Especially if you wish to persist a larger amount of data in terms of number of images, fields, etc. When you create a module through module builder it will also give you a code reference for how to access that new data via the API.
It still operates the same way. Meaning if you want to include jquery it's best through resource links like this:
In your masterpage preferably or any one of your widget templates.Regards,