Active
Project:
Syndeploy
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Aug 2011 at 00:05 UTC
Updated:
30 Aug 2011 at 22:10 UTC
It looks like we have four (4) options here:
Which one is the best?
We'd like a solution that's simple, yet extensible. Please post your comments.
Comments
Comment #1
socialnicheguru commentedI like the idea of using views to determine what content will get deployed. Views is flexible and gives you a number of views plugins for the content to sent as: rss, ref, etc.
So to decrease development time, would it be worthwhile to use views. You could include a default syndeploy view that people can clone? People could then use any views plugin like views_data_export, views_datasource, or views_rss to export their view to feeds.
Comment #2
colanThat is exactly what this module will do. Please see the project page for details. This issue deals exclusively with what will produce the feed from the view. Let's keep it to that. Thanks!
Comment #3
colanThe build-in Feed display that comes with Views is not sufficient. The only options available are:
There isn't any granular control for fields. Views RSS looks like it may be easier to set up if all you need is an RSS feed, and you get control over fields. If this is sufficient, we may not need something as generic as Views Datasource. See #584706: Duplicate module for details.
Comment #4
socialnicheguru commentedthese might be worthwhile to take a look at
views_atom - provides field level control
feed_atom - provides a feed reader for views_atom output
Comment #5
colanYes, absolutely. Thanks for providing those - I didn't know about them. Here are the links for quick access:
I'm updating the summary at the top to include Views Atom.
Comment #5.0
colanAdded Views Atom to the list.