Recommend this pageIf this page was useful to you, please recommend it to fellow websurfers:
Home > Scripts > Content Management (CMS) > Radio / Podcast
You may rate this script by simply clicking on the appropriate star (5 stars is the best rating).
To run your audioblog/podcast with Loudblog, you need the following things:
For an advanced Loudblog experience it is nice to have
LoudBlog is a sleek and easy-to-use Content Management System (CMS) for publishing media content on the web. It automatically generates a skinnable website and an RSS-Feed for Podcasting. Just upload your audio/video files, add some notes and links, and you’re done!
The future development of LoudBlog will be done by ONLINETRUST new media. You should have a look at Netz-Kultur.com Blog to get informed about the latest status.
LoudBlog is not a fully featured weblog system like Textpattern or Movable Type, although it does offer the basic weblog functionality. Use LoudBlog if you’re publishing media data on a regular base and do not need sophisticated features other systems may provide much better.
LoudBlog makes Mediablogging and Podcasting easy. There are a variety of ways to put your media content into the system. You can upload it via your browser, use a free FTP client like filezilla or â€“ get the files from the web! (Before you do that you have to ensure you have permission to publish them in your site!)
After that you can add lots of meta information e.g. a title, a short message, or a list of hyperlinks related to your media posting. You can even control the publishing time and put your postings into multiple categories. But you donâ€™t have to!
LoudBlog concentrates on what is really useful. With LoudBlog you can use Textile or Markdown and create beautiful XHTML-code in no time at all. WYSIWYG-Editors are crap! Did you ever understand Trackback/Pingback? It’s complicated stuff and doesn’t fit into the LoudBlog concept.
Are you a famous webdesigner? Youâ€™re not? No problem, simply select one of the amazing LoudBlog-templates. Oh, you ARE a famous webdesigner? Cool, you can create your very own template using the XHTML-conform LoudBlog-tags. Web developers can write new plugins in PHP and generate thrilling SQL-queries. LoudBlog is fully customizable, so you are free to modify it as you like. Even hacks are welcome. At your own risk, of course!
LoudBlog automatically creates a valid Podcasting-feed. Visitors can listen/watch your mediablog posts using a podcast client or ‘podcatcher’ e.g. iPodder. To do this they simply click on the ‘podcast- feed’ hyperlink and copy and paste the page url into their chosen podcatcher. The podcatcher then opens itunes, or another media player selected as the default player, and automatically plays the programme! As the ‘podcatcher’ regularly checks for new content visitors are effectively subscribed to your podcast channel! Wow …
Visitors can also use the podcast feed in an ordinary RSS-Reader minus the media content of the podcast of course.
The fabulous Ektoras created a tool called Loudbot to combine the general power of some well-known content management systems with the ease of use on handling media files that LoudBlog is providing to its users. If you are working with Mambo, Joomla, Drupal, Serendipity, Geeklog or WordPress, you can install LoudBlog additionally to your existing setup — it will help you with uploading, organizing and tagging your media files, and after that Loudbot transfers those files to your main CMS. It’s that easy!
This label indicates that I could install the script without major problems and I could run the script without the need for major modifications to the original code (except for the usual configuration, of course). The label does, on the other hand, not indicate that scripts without this label would not work properly. The missing of the „tested & working“-label just indicates that I did not yet test these scripts.
This label indicates that the owner of this website uses this script / application for his own projects with success and satisfaction. This does, however, not indicate that these projects could not have been realized using other scripts / applications as well or that other scripts would not fit the demands of other projects as well or even better.