You may think that you just need to go to admin/build/block in order to add the nodequeue as a block to your site. That's not the case, first we need to enable the nodequeue in Views, so go to admin/build/views and you will see nodequeue_1 listed (ok, mine says nodequeue_2 well I did a dry run before writing this tutorial) with Title 'Latest Stories', notice how the Status is Disabled.
Click on the Enable link under the Actions column in order to enable it.
Now go back to admin/build/block and you will see the nodequeue listed under the disabled.
Select the region where you want it to be displayed and click Save Blocks button. (Note we can configure the block which will allow us to override the Title, and do all the usual things possible with Blocks permissions etc). You should now see the nodequeue appear as a block in your chosen region.
So now we have a Block on the site which lists the content of our nodequeue, we can manually add and remove Story nodes from the queue. But what happens when we eventually have more than 5 Story nodes on our queue? The oldest story will disappear from the queue and we'll have a more link displayed at the foot of the block.
Also, if you inspect the nodequeue the In queue column will show 5 and the words QUEUE FULL.
Before we use Actions and Workflow modules, a few observations about nodequeue:
Let'smake a view of our nodequeue, so we can make the Latest Stories block list stories by the time the Story node was created.