Sourcefabric Manuals

 English |  Español |  Français |  Italiano |  Português |  Русский |  Shqip

Newscoop 4.1 Cookbook

Working with featured article lists (aka Playlists)

Newscoop offers a couple of automated ways for ordering content:

  • Order by publishing date (ascending / descending)
  • Order alphabeticallly
  • Order manually (in a section you can move articles around)

...and more. These are described in the chapters about listing articles. 

These automated listings have an advantage: you just write, proof and publish your article and they show up in the list - as for example inside a blog where the newest article is on top.

Newscoop also offers the possibility to make custom lists with articles. The advantage is that the editor has full control over what article is displayed where. And we have come to see that any publication of a certain size tends to use this feature, which is called Featured Article List. The downside is that it involves an extra step for the editors: after completion of the article, it needs to be added to the playlist.

Featured Article List is a custom article list created for use in a specific template, such as the front page of your publication. Playlists allow editors to manually manage their content and pick articles from different sections. To create a new list, click on Featured Article List in the Content menu, then click the blue Add list button.

To display these lists (which we call "playlists" internally, it just happened and stuck...) you need to know the name you gave the list in the admin interface or the dynamically generated ID.

Playlists behave exacly like regular {{list_articles}} block. To display it in your template use this syntax:

{{ list_playlist_articles name="<playlist name>" }} 
// or {{ list_playlist_articles id="<playlist id>" }}

You can also set the length of your list. The below example will display the top four articles in the list.

{{ list_playlist_articles id="2" length="4"}}

There has been error in communication with Booktype server. Not sure right now where is the problem.

You should refresh this page.