Story Vs. World Almanac
 

I dont see the point of having the two different. whould someone explain the point?

I could be wrong, but I always thought this was way to de-clutter the interface.

You would have all the pertinent information about your adventure in the story almanac and the wider/more general information about your campaign world in the world almanac. If my party is adventuring in New York, I don't really need all the information for LA at my fingertips (necessarily) but it is still there in the world almanac if required.

Another cool thing is that if the PCs clear portions of your adventure, you can transfer the cleared content to the world almanac as a de-facto way of managing where you are up to in the adventure/campaign.

I look on the World Almanac as the Library, and the Story Almanac as the book I am going to focus on at the moment. As I require additional information, I can access the library and obtain other relevant books/documents for my reading table. I only need to have immediate access to that which is relevant to the current story/area of research. The rest of the library will come in handy when I need to look elsewhere.

They've got the right idea for how the Story Almanac seems to have been intended. I'm not using RW at the table so I'm only using the World Almanac for now. I find the artificial division annoying while doing world building. The last thing I want is to have to do two searches every time I need to find something.

Unfortunately, this means that if I were to start using both it'd take a lot of work to move the right parts over to the Story Almanac. :(

Some of us would like to see Custom Almanacs so we can organize things in more ways. I personally would like one of them to contain everything.

If you're using the Container Hierarchy, when you move a container from World to Story or Story to World, it asks if you want to include all the child topics. That takes almost all the work out of moving multiple entries from one to the other, for me, as I usually do want the child topics to go with the container.

While building, keep all in one. I built the Second Darkness AP all in the Story almanac for ease, then moved the key container topics to World for some things. The reverse, building all in World and moving a few to Story as needed, would work just as well.

I also agree that moving topics between them is very simple. And I don't know what you mean, Parody, when you say having to do two searches? The linking mechanism, for example, searches both Almanacs (and even the Mechanics section, too.) So generally there's not much searching you'd have to do. Especially when using the Story Almanac as just a short repository for the stuff you expect to be using at the table. That gives you a relatively short list of things you're already expecting to have to glance/search through. Then if you really need something out of the World Almanac you already know what sections you don't have in Story so it's easy enough to switch over.

For initial building I also agree it's best to just put everything in World, then when you are ready to start a game just pull over those things you need at that time.

I think what Parody means is if it is necessary to update a topic, finding one among many can be a chore.

I seldom do searches, honestly. I click on a topic I can readily find that I think should have a link to the one I want, then click through the link.

Searching between Almanacs is what I've asked for here: http://forums.wolflair.com/showthread.php?t=48861

Sure would make my life easier, and it sounds like I'm not the only one. Give it a +1 if you think it's a good idea.

This might not be as intended but works fantastically for me in my games.

Story Almanac is for things that occur in the campaign that are player related, and I use World Almanac for all the setting things that I might use between games, especially when we are able to transfer content between realms.

It makes it easy to tell what is official and what is campaign specific :)

And I use the articles for rules based content including generic monster statblocks.