Not sure if this is the right way of doing things but it works.
Consider this scenario – you have a Drupal multisite and would like a central location to write and publish news.
Ok, doing this is pretty simple, just go to your Drupal root and find .htaccess file.
Open it and somewhere at the top add this code: Note changing 'timonweb' to your own Feedburner ID. People there gave good solutions for managing multiple feeds.
Drupal 8 includes new features and improvements for both users and developers, including: a revamped user interface; WYSIWYG and in-place editing; improved mobile support; added and improved key contributed modules including Views, Date, and Entity Reference; introduced a new object-oriented backend leveraging Symfony components; revamped configuration management; and improved multilingual support.From now on, everyone who uses your main Drupal RSS feed which looks like: be redirected to Feedburner processed RSS feed. No more code changes, no more jumping through the hoop. The problem I have is that feed 2 always creates a new set of nodes rather than updating the existing nodes (that were created using feed 1).The traditional advice about updates is to subscribe to the updates mailing list: that works well for most projects.For broad software projects like Drupal, however, that advice is increasingly unmanageable.